Re: USB device allocation

david parsons (o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s)
5 Oct 1999 18:04:25 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Zachary Amsden: "Re: predictable IP ID"
Previous message: Andi Kleen: "Re: SMP system panic with down/up calls for locking. Need help on as sembly compiling."
Maybe in reply to: Pavel Machek: "USB device allocation"

In article <linux.kernel.37FA5D6B.E147FAA0@transmeta.com>,
H. Peter Anvin <hpa@transmeta.com> wrote:
>Dan Hollis wrote:
>>
>> On Tue, 5 Oct 1999, Steffen Grunewald wrote:
>> > That's 32 entries for 16 devices...
>> > > 64 = /dev/usbscanner0 USB HP scanner
>> > > ...
>> > > 95 = /dev/usbscanner15
>> > Same here...
>> > > 128 = /dev/ttyACM0 USB modem
>> > > ...
>> > > 255 = /dev/ttyACM127
>> > What about some spare entries for USB monitors, speakers, CDrecorders ?
>>
>> The desperate need for devfs becomes all more clear.
>>
>
>Actually, the need is for a decent-sized dev_t.

Devfs doesn't require human intervention to safely allocate major
and minor numbers.

____
david parsons \bi/ Remember that one of the selling points for ELF was
\/ that people didn't have to go to an administrator to
get address ranges for their shared libraries.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Zachary Amsden: "Re: predictable IP ID"
Previous message: Andi Kleen: "Re: SMP system panic with down/up calls for locking. Need help on as sembly compiling."
Maybe in reply to: Pavel Machek: "USB device allocation"