devfs
[Top] [All Lists]

Re: Devfs and USB status

To: jerdfelt@xxxxxxxxxxx, rgooch@xxxxxxxxxxxxxxx
Subject: Re: Devfs and USB status
From: "Khimenko Victor" <devfs@xxxxxxxxxxxxxxxxx>
Date: Fri, 9 Jun 2000 20:03:17 +0400 (MSD)
Cc: devfs@xxxxxxxxxxx
Organization: MCCME
References: <20000607225256.C2108@valinux.com> <200006080545.e585j5d18700@vindaloo.ras.ucalgary.ca>
Sender: owner-devfs@xxxxxxxxxxx
7-Jun-00 22:52 you wrote:
> On Wed, Jun 07, 2000, Richard Gooch <rgooch@xxxxxxxxxxxxxxx> wrote:
>>   Hi, Johannes. I'm wondering what's happened as a result of our
>> discussions a couple of months ago? You were planning on making heavy
>> use of devfs+devfsd in the USB code. How's that going?

> Slowly. I had gotten most of the code developed and working, but then I
> received an email from Randy Dunlap, the USB maintainer. He had a
> discussion with Linus about the subject. I've included the email at the
> end of my mail.

> I don't know what to do now. I've been spending some time on a white
> paper which describes the problems we are running into and why I
> wanted to use devfs to facilitate solving the problems. However,
> I'm unsure it will make any difference. People seem to want a hacked
> together kludge than something sensible (devfs IMHO).

Looks like the only solution is to go "devfs (reiserfs, raid, etc) way":
keep it as separate patch for 2.4 (2.6, 2.8) and merge in 2.5 (2.7, 2.9).
Most peoples out there are NOT kernel developers. They want to hear sound,
use USB mouse and not think about kernel at all. They DO NOT want to play
with ALSA, devfs unless it's included in distribution by default. For them
devfs requirement for USB is evil. So USB can not rely on devfs (for now) :-/
This mean: we need some kludgy solution for 2.4. It does not mean that
such kludges should be with us forever.




<Prev in Thread] Current Thread [Next in Thread>