Re: "Miscellaneous" bus for the driver model?

From: Jeff Garzik (jgarzik_at_pobox.com)
Date: 01/07/04

  • Next message: Jeff Garzik: "Re: [autofs] [RFC] Towards a Modern Autofs" 
    Date:	Wed, 07 Jan 2004 16:20:43 -0500
To: Russell King <rmk+lkml@arm.linux.org.uk>

    Russell King wrote:
    > On Wed, Jan 07, 2004 at 09:33:45AM -0800, Greg KH wrote:
    >
    >>On Wed, Jan 07, 2004 at 11:00:16AM -0500, Alan Stern wrote:
    >>
    >>>Would it make sense for the driver model core to add a "miscellaneous" or
    >>>"other" bus, intended for devices or drivers that are one-of-a-kind or
    >>>otherwise non-standard? Kind of similar to the platform bus but meant
    >>>for new things, not part of a legacy or other system/architecture-specific
    >>>base?
    >>
    >>That's what the "legacy" bus is for. There's a patch floating around
    >>that renames that bus to "platform" to remove any connotation that
    >>"legacy" might occur.
    >
    >
    > Can we get this patch merged ASAP please? It should really have gone
    > in before 2.6 so we don't have this change during a stable kernel series.

    It's already in :)

            Jeff

    ChangeSet@1.1474.51.99, 2003-12-29 21:54:21-08:00, akpm@osdl.org
       [PATCH] Rename legacy_bus to platform_bus

       From: Jeff Garzik <jgarzik@pobox.com>

       I've seen this patch floating around. Not sure the origin, but it's
       surfaced on lkml and also when I was poking around handhelds.org CVS for
       iPAQ patches: on non-PCs, particularly system-on-chip devices but not
       just there, you have a custom "platform bus" that is the root of pretty
       much all other devices and buses.

       It's something I wanted to make sure people didn't forget; to make sure
       the legacy_bus didn't get "legacied out of existence." ;-)

    -
    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: Jeff Garzik: "Re: [autofs] [RFC] Towards a Modern Autofs"

    Relevant Pages

    • [CODE RFC] redefining sched_setscheduler using LD_PRELOAD
      ... Do also try (don't try this as root unless rt_monitor is running) ... code that checks uid before using the redefined functions won't work ... (I have an modified latencytest) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH]
      ... the polymonials used are not even primitive, the ability for root to wipe-out ... the random pool, the ability for root to access the random seed directly, the ... all of these, uses crypto-api, uses known crypto primitives, is simpler to ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] [3/48] Suspend2 2.1.9.8 for 2.6.12: 301-proc-acpi-sleep-activate-hook.patch
      ... When the user has an initrd or initramfs, ... image, encryption keys and so on have been set up, but the root fs has ... probably will result in hard disk corruption if they echo to do_resume ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: via-rhine apparently broken in 2.4.23-pre4
      ... > VIA Rhine II chip. ... root:~# uname -a ... Now, booting back to 2.6.0-test5;) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: unsafe printk
      ... So one day root is using grep on ... Sanitizing kernel messages would be good start, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)