Just a thought: Kconfig & architecture command

From: Wim Van Sebroeck (wim_at_iguana.be)
Date: 01/03/04

  • Next message: Helge Hafting: "Re: udev and devfs - The final word" 
    Date:	Sat, 3 Jan 2004 15:51:50 +0100
To: linux-kernel@vger.kernel.org

    Hi All,

    while working on some of the watchdog-drivers (that are only valid for certain architectures), I just wondered if we cannot have a simpler indication of the architecture the driver is working on. A possible solution would be to have an extra keyword/command 'architecture' in the Kconfig file. It works like a dependancy, but you have a clear distinction between the real dependancy and the actual hardware/architecture it runs on.

    Lett me give a simple example: the sa1100 watchdog driver only works for the sa1100 architecture. In Kconfig this could then look like:
    -Kconfig------------------------------------------------------------------
    config SA1100_WATCHDOG
            tristate "SA1100 watchdog"
            architecture ARCH_SA1100
            depends on WATCHDOG
            help
              Watchdog timer embedded into SA11x0 chips. This will reboot your
              system when timeout is reached.
              NOTE, that once enabled, this timer cannot be disabled.
                                                                                                     
              To compile this driver as a module, choose M here: the
              module will be called sa1100_wdt.

    --------------------------------------------------------------------------
    Â
    The advantage is that you could source driver directory's more easily in a lott of architectures (without having to copy general pieces in every seperate architecture-dependant Kconfig file, like we do know for sun, sh, ...).

    Greetings,
    Wim.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Helge Hafting: "Re: udev and devfs - The final word"

    Relevant Pages

    • Re: Just a thought: Kconfig & architecture command
      ... > the sa1100 architecture. ... In Kconfig this could then look like: ... The ARCH_ prefix already says that it's an arch symbol and you ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: a 15 GB file on tmpfs
      ... > That should be no problem on a 64 bit architecture. ... Please read the FAQ at http://www.tux.org/lkml/ ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
      (Linux-Kernel)
    • Re: [PATCH] 2.4.22pre10: {,un}likely_p() macros for pointers
      ... >> Well, I'm not sure about the polarity, but that unlikelymacro isn't ... architecture where there's a pointer type larger than long, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] generic irq subsystem: ppc64 port
      ... >> I still like the idea of the patch, so it would be useful if you added ... >> architecture can provide it's own. ... > generic IRQ code and just provide a way to switch between 1:1 mapped and ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: List of oversized inlines
      ... > on sizes on one architecture. ... style inlines. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)