Re: Christmas list for the kernel

From: Vojtech Pavlik (vojtech_at_suse.cz)
Date: 11/23/05

  • Next message: Sid Boyce: "Re: 2.6.15-git latest build broken on UP x86-64" 
    Date:	Wed, 23 Nov 2005 13:17:26 +0100
To: Jon Smirl <jonsmirl@gmail.com>

    On Tue, Nov 22, 2005 at 04:13:01PM -0500, Jon Smirl wrote:

    > On 11/22/05, Greg KH <greg@kroah.com> wrote:
    > > On Tue, Nov 22, 2005 at 01:31:16PM -0500, Jon Smirl wrote:
    > > >
    > > > 4) Merge klibc and fix up the driver system so that everything is
    > > > hotplugable. This means no more need to configure drivers in the
    > > > kernel, the right drivers will just load automatically.
    > >
    > > What driver subsystem is not hotplugable and does not have automatically
    > > loaded modules today?
    >
    > All of the legacy stuff - VGA, Vesafb, PS2, serial, parallel,
    > joystick, floppy, gameport, etc.

    You can remove these from the list:

    ps/2 and serial (for input devices) use the 'serio' layer, which does
    have automatic loading.

    gameport is missing, but planned. Unfortunately you can't probe for
    joysticks before you load the specific modules, so it simply will have
    to load all available drivers. On the other hand, gameports are a dying
    breed, replaced by USB, which is good.

    And the others:

    VGA drivers are autoloaded by the PCI subsystem.

    VESAfb can't ever be autoloaded.

    serial, parallel, gameport, etc are using the PnP subsystem and will be
    autoloaded if ACPIPnP reports these devices.

    And floppy, well, I think it isn't using ACPIPnP but possibly could ...

    > Those drivers could be in initramfs
    > and only load if the hardware is found. Most of these legacy devices
    > have poor sysfs support too. Also, it's not just x86 legacy device all
    > of the platforms have them.

    The hardware is often found only by the driver, like in the joystick
    case. Hopefully ACPIPnP will list all the devices ...

    > Currently you have to compile most of this stuff into the kernel.

    You don't. 

    -- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
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: Sid Boyce: "Re: 2.6.15-git latest build broken on UP x86-64"

    Relevant Pages

    • Re: Sidewinder Force Feedback Pro 1
      ... Others have answered your question about the joystick ... goto support.intel.com and download the latest Intel ... > joystick gameport connection to a USB port but when I try to install ... > know it means the driver is not installed correctly but I have no clue ...
      (microsoft.public.windowsxp.games)
    • Input patches for 2.6.12+
      ... patches from me (gameport support cleanup in OSS, ... Input: Wacom driver update ... Also make sure that serio core takes serio->drv_sem ...
      (Linux-Kernel)
    • Re: Vista fixes PCIe re-install problem ... why ?
      ... This would cause Server 2003 to avoid the power state transition ... their subsystem ID changes. ... If he sends the vendor/device IDs of the device, ... since a driver uninstall/reinstall doesn't cause the PDO to be recreated, ...
      (microsoft.public.development.device.drivers)
    • Linux IEEE 1394/ FireWire subsystem TODO list
      ... Another page related to FireWire ... driver development status is http://wiki.linux1394.org/JujuMigration. ... IEEE1394 Subsystem ... Implement MCAP and multicast support. ...
      (Linux-Kernel)
    • Re: [spi-devel-general] [Patch 1/4] Industrialio Core
      ... this subsystem is _huge_. ... how I imagine the ADC subsystem. ... then it will get moved to the main headers rather than being driver specific. ... If we know the device is an accelerometer rather than a general ADC is would be ...
      (Linux-Kernel)