Uz.ytkownik David Brownell napisa?:
>>> 1. Rename usb-ohci to usb-ohci-old
>>
> 
> Keeping the old-style drivers would defeat the purposes
> of having new-style ones, though.
> 
> 
>>> 2. Rename ohci-hcd to usb-ohci
>>
> 
> But during the transition period when both exist, what then?

ohci-ncd stand then for

open-host-contoller-interface-host-controller-device...

Quite a lot of semanticla duplication if you ask me.


> 
> And later when someone says "I'm using the usb-ohci driver" (or
> since ostensibly this thread is about UHCI, "usb-uhci") just what
> code would they talking about?
> 
> 
>> hcd stands for Host Controller Device. 

See above ohci.o whoudl do it.

> 
> 
> Actually "Host Controller Driver", for what it's worth.
> One of the changes in 2.5 is to shrink the amount of HCD
> code by moving duplicated (or worse, partially-duplicated)
> code into a newish HCD-only part of the usbcore code.  The
> "-hcd" suffix flags drivers that have taken significant
> steps down that {bug,size}-reduction path.

Yes yes I see and I second the changes.
But I still have some "esthetical" problems with the
new naming conventions.


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to