From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <greg@kroah.com>
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 23:24:31 +0100 [thread overview]
Message-ID: <20031120222431.GD196@elf.ucw.cz> (raw)
In-Reply-To: <20031120170303.GJ26720@kroah.com>
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.
Do you have URL/her e-mail address? I don't remember seeing anything
:-(.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-11-20 22:23 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
2003-11-20 22:24 ` Pavel Machek [this message]
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=20031120222431.GD196@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=azarah@nosferatu.za.org \
--cc=bunk@fs.tum.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.