FYI, sample output of Randy's "usbtree":
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=hub/4p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=hub/5p, 480M
|__ Port 4: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 3: Dev 3, If 0, Class=hub, Driver=hub/4p, 12M
Hi,
This patch lets more devices hook up to USB 2.0 hubs, stuff
like keyboards, mice, hubs that hasn't worked yet:
- schedules full/low speed interrupt transactions
- tracks CSPLIT bandwidth for full/low speed interrupt
transactions
- moves some bus bandwidth calculation out of the EHCI code
On Fri, May 24, 2002 at 10:19:07AM -0400, Stuffed Crust wrote:
<...>
> 1) Device plugged in on bootup.
> a) Without the device reset, the device does not initialize properly,
> and unplugging/replugging is necessary.
> b) With the device reset in the driver, on a KT266 (usb-uhci) the
>
On Fri, May 24, 2002, Thomas Sailer <[EMAIL PROTECTED]> wrote:
> Johannes Erdfelt wrote:
>
> > usb_control_msg() is probably what he wants. It waits.
>
> Yes. But still we should probably have control queueing for
> the uhci's (possibly at the HCD level?)
>
> Think about multi-interface devices
Johannes Erdfelt wrote:
> usb_control_msg() is probably what he wants. It waits.
Yes. But still we should probably have control queueing for
the uhci's (possibly at the HCD level?)
Think about multi-interface devices, where all interfaces have
different drivers that do not know about each other
Hi!
Regarding USB initialization bug - is there anybody there who has
problems with newest 19-pre or stock (not red hat) 2.4.18 kernel ?
BR,
Jacek
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in
On Fri, May 24, 2002 at 02:04:40PM -0400, Johannes Erdfelt wrote:
> Just to clarify, uhci-alt worked in every case, but usb-uhci would oops
> when resetting the device plugged into the root hub?
In every case I tried, yes. 'uhci' worked fine, while 'usb-uhci' oopsed
on some platforms when plugge
On Fri, May 24, 2002, Stuffed Crust <[EMAIL PROTECTED]> wrote:
> I've been doing a lot of work recently on the linux-wlan-ng prism2.5 USB
> driver, and I've finally reached the pointw here I have to break down
> and ask for help from someone more familiar with the USB way of things.
>
> Basically
On Fri, May 24, 2002, Martin Diehl <[EMAIL PROTECTED]> wrote:
> On Fri, 24 May 2002, Thomas Wahrenbruch wrote:
>
> > some Control URBs to the converter. Sending one Control URB works fine.
> > But if I want to send more than one Control URB, I have to wait for the
> > completion hanlder to finish
On Fri, May 24, 2002 at 12:42:24PM +0200, Thomas Wahrenbruch wrote:
> Hi all,
>
> when I attach our USB-Serial Converter I get a kernel oops.
> Is it possible that a module has problems to evaluate the device
> descriptor? (One interface with three alternate settings)
Which kernel version is th
On Fri, 24 May 2002, Gunther Mayer wrote:
> "Stephen J. Gowdy" wrote:
>
> > I don't have a problem with the new names. Users shouldn't care, and when
> > they do they want to report problems.
>
> You like to get these reports ?
> "USB does no longer works, since I upgraded to 2.5"
Best part of
>>See above ohci.o whoudl do it.
>
> FWIW, I agree - IMHO the 'ideal' naming would be "ehci.o", "uhci.o",
> and "ohci.o". Let the 2 uhcis get named "uhci-.o" until a
> decision is made, then rename the winner to "uhci.o".
>
> Adding "usb-" or "-hcd" is just baggage to the name.
I'd go for thi
> > Using that "-hcd" suffix is completely unambiguous.
> > (But if we go with the "usb-uhci-hcd" driver I'd vote
> > to rename it as "uhci-hcd".)
>
> I didn't kown ohci was already used.
> But if anything I would prefer the usb- prefix over
> the -hcd suffix and a move away of the old driver whi
"Stephen J. Gowdy" wrote:
> I don't have a problem with the new names. Users shouldn't care, and when
> they do they want to report problems.
You like to get these reports ?
"USB does no longer works, since I upgraded to 2.5"
> It would help to know what they are
> actually talking about withou
> - in the module's cleanup routine, i unregister the usb device
> which causes the diconnect routine to be
> invoked(with the device still attached)
If you unregister the _driver_ that'd be correct. And I'm hoping
that your disconnect() routine actually gets rid of all hooks that
your
On Fri, 24 May 2002, Martin Dalecki wrote:
>> 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.
FW
Uz.ytkownik David Brownell napisa?:
>> open-host-contoller-interface-host-controller-[driver]...
>>
>> Quite a lot of semanticla duplication if you ask me.
>
>
> If you split all acronyms into their component atoms
> before coming up with new names, I think you'll end
> up changing quite a lot o
> open-host-contoller-interface-host-controller-[driver]...
>
> Quite a lot of semanticla duplication if you ask me.
If you split all acronyms into their component atoms
before coming up with new names, I think you'll end
up changing quite a lot of technology nomenclature.
(Avoid starting names
hi...
guess i dint get accross
correctly...this is what i do...
- to start
with the driver is up,usb device is attached and
data transfer happens
- now i
remove the driver module(i have the device attached, i dont increment the MOD
COUNT in
the probe,so u are allowed to re
I don't have a problem with the new names. Users shouldn't care, and when
they do they want to report problems. It would help to know what they are
actually talking about without need to remember which kernel the rename
happened in (and that distributions may backport the changes to earlier
ke
Peter Wächtler wrote:
> Martin Dalecki wrote:
> > Uz.ytkownik Greg KH napisa?:
> >
> >> Anyway, here's the documentation that you need:
> >> The module usb-ohci is now gone. Use ohci-hcd instead.
> >>
> >> The people with UHCI controllers have a big more documentation to read:
> >> The m
> I have my usb driver as a linux module. the problem i have is this -
> i forcefully remove the module when the usb
> device is attached...
Presumably you mean "detached"?
> a proper cleanup happens and the device is
> unregistered succesfully...
That should happen regardless of wheth
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 sta
>> 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?
And later when someone says "I'm using the usb-ohci driver" (or
since
I've been doing a lot of work recently on the linux-wlan-ng prism2.5 USB
driver, and I've finally reached the pointw here I have to break down
and ask for help from someone more familiar with the USB way of things.
Basically, thanks to firmware bugs in the hardware, it's often necessary
to reset
On Fri, 24 May 2002, Thomas Wahrenbruch wrote:
> some Control URBs to the converter. Sending one Control URB works fine.
> But if I want to send more than one Control URB, I have to wait for the
> completion hanlder to finish, before I can send the next URB. (Please
> correct me, if I'm wrong) I
I habve problems with my USB Harddisk. I am getting following errors.
hub.c USB new device connect on bus 2/2 assigned device number 2
usb.c USB device 2 (vend/prod 0x4ce/0x2) is not claimed by any active
driver
SCSI subsystem driver Revision 1.00
Initializing USB Mass Storage driver ...
usb.c:
On Fri, 24 May 2002, Thomas Wahrenbruch wrote:
Sure, it should not Oops, but I'm just wondering how a
> T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=1.5 MxCh= 0
_lowspeed_ device
> D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
with vendorspecific features...
> P: Ven
Thomas Wahrenbruch wrote:
> Hi all,
>
> I'm writing a driver for our (custom-made) USB-serial converter using
> the usb_serial module. In order to setup the converter I have to send
> some Control URBs to the converter. Sending one Control URB works fine.
> But if I want to send more than one Con
Hi all,
when I attach our USB-Serial Converter I get a kernel oops.
Is it possible that a module has problems to evaluate the device
descriptor? (One interface with three alternate settings)
Best regards
Thomas Wahrenbruch
[root@darkred root]# cat /proc/bus/usb/devices
T: Bus=02 Lev
Hi all,
I'm writing a driver for our (custom-made) USB-serial converter using
the usb_serial module. In order to setup the converter I have to send
some Control URBs to the converter. Sending one Control URB works fine.
But if I want to send more than one Control URB, I have to wait for the
compl
Martin Dalecki wrote:
> Uz.ytkownik Greg KH napisa?:
>
>> Anyway, here's the documentation that you need:
>> The module usb-ohci is now gone. Use ohci-hcd instead.
>>
>> The people with UHCI controllers have a big more documentation to read:
>> The module uhci is now gone. If you used t
On 24 May 2002, Dmitri wrote:
> It is a Web server with built-in page editing features, so that any
> visitor (or authorized visitors) can edit pages. It is often used to
> collect FAQ entries from people, advices, and other collaboration. It
> could be easily used to collect USB IDs, even automa
On Thu, 2002-05-23 at 23:57, Jacek Pliszka wrote:
> On 21 May 2002, Dmitri wrote:
>
> > Public Wiki server sounds like the best option - and an easy hack too.
>
> What is it Wiki?
http://c2.com/cgi/wiki?WikiWikiWeb
It is a Web server with built-in page editing features, so that any
visitor (or
34 matches
Mail list logo
