Re: [linux-usb-devel] [gadget] Faking set_configuration

2004-04-17 Thread David Brownell
Robert Schwebel wrote: Unfortunately, the Hynix docs [1] are not very, hmmm, let's say detailed Right ... but the config descriptor on p. 91 strongly suggests that the only configuration number supported is "2". It also suggests: - idProduct and idVendor are settable - bDevice{Class,SubClass,

Re: [linux-usb-devel] [gadget] Faking set_configuration

2004-04-17 Thread Robert Schwebel
Dave, On Fri, Apr 16, 2004 at 10:47:09AM -0700, David Brownell wrote: > >I'm working on support for a chip which handles EP0 trafic almost > >completely in hardware (Hynix H7202). As you don't get things like Set > >Configuration Requests the usual state machines do not work, so I fake > >the call

Re: [linux-usb-devel] [gadget] Faking set_configuration

2004-04-16 Thread David Brownell
Robert Schwebel wrote: I'm working on support for a chip which handles EP0 trafic almost completely in hardware (Hynix H7202). As you don't get things like Set Configuration Requests the usual state machines do not work, so I fake the calls from the reset interrupt. How do the Hynix docs say drive

[linux-usb-devel] [gadget] Faking set_configuration

2004-04-15 Thread Robert Schwebel
I'm working on support for a chip which handles EP0 trafic almost completely in hardware (Hynix H7202). As you don't get things like Set Configuration Requests the usual state machines do not work, so I fake the calls from the reset interrupt. That means that I have to call dev->driver->setup() f