From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
Adrian Bunk <bunk@fs.tum.de>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] document that udev isn't yet ready (fwd)
Date: Thu, 20 Nov 2003 09:03:03 -0800 [thread overview]
Message-ID: <20031120170303.GJ26720@kroah.com> (raw)
In-Reply-To: <20031120125228.GC432@openzaurus.ucw.cz>
On Thu, Nov 20, 2003 at 01:52:29PM +0100, Pavel Machek wrote:
> Hi!
>
> > > > Hm, with the 006 release, what do you find lacking in udev?
> > > >
> > >
> > > I am guessing its more driver support, etc. Input devices for
> > > instance do not seem to have any sysfs support yet,
> >
> > Yes, we do need better driver support. But that's nothing that udev
> > itself can do :)
> >
> > I have a number of patches pending for 2.6.1 that will add more driver
> > support for sysfs.
> >
> What drivers did you convert? sysfs-for-inputs would
> be *very* welcome.
I have patches for the memory devices, all sound drivers (ALSA and OSS),
frame buffer devices, and misc devices in my linuxusb.bkbits.net/usb-2.5
tree. Hanna Linder is working on the input sysfs patches, and has
posted some work in the past.
thanks,
greg k-h
next prev parent reply other threads:[~2003-11-20 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 21:32 [2.6 patch] document that udev isn't yet ready (fwd) Adrian Bunk
2003-11-19 22:14 ` Greg KH
2003-11-19 23:12 ` Martin Schlemmer
2003-11-19 23:26 ` Greg KH
2003-11-20 12:52 ` Pavel Machek
2003-11-20 17:03 ` Greg KH [this message]
2003-11-20 22:24 ` Pavel Machek
2003-11-20 22:28 ` driver model for inputs Pavel Machek
2003-11-20 22:48 ` Hanna Linder
2003-11-20 22:55 ` Pavel Machek
2003-11-20 23:18 ` Hanna Linder
2003-11-20 23:54 ` Pavel Machek
2003-11-21 0:35 ` Hanna Linder
2003-11-20 23:09 ` viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031120170303.GJ26720@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=azarah@nosferatu.za.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox