On Fri, 11 Nov 2005, Mike King wrote:
> Alan,
>
> I finally go 2.6.14 running and the same thing happens. On initial connect
> my driver is loaded and configuration 1 is selected. When I perform :
>
>echo '2' >/sys/bus/usb/devices/2-2/bConfigurationValue
>
> and I read the bConfiguration
Alan,
I finally go 2.6.14 running and the same thing happens. On initial connect
my driver is loaded and configuration 1 is selected. When I perform :
echo '2' >/sys/bus/usb/devices/2-2/bConfigurationValue
and I read the bConfigurationValue it is null. Additionally, as expected,
my driver
On Tue, 1 Nov 2005, Mike King wrote:
> Alan,
>
> Nothing was resolved on this failure. I haven't been able to try it
> on 2.6.14 because I can't get mkinitrd to build an image. It keeps
> complaining about 'No module ata_piix found'.
>
> I don't think it is the device because it works find on
Alan,
Nothing was resolved on this failure. I haven't been able to try it
on 2.6.14 because I can't get mkinitrd to build an image. It keeps
complaining about 'No module ata_piix found'.
I don't think it is the device because it works find on WinXP with the
test program and WinXP kernel driver
On Tue, 25 Oct 2005, Mike King wrote:
> Oliver,
>
> > Ok. So it is not the obvious. Is there anything in the syslog after you
> > enable USB debugging?
> > And does it work on younger kernels?
> >
>
> Here is the list of what is going on with the usb core when I change the
> config from 1 to 2.
Oliver,
> Ok. So it is not the obvious. Is there anything in the syslog after you
> enable USB debugging?
> And does it work on younger kernels?
>
Here is the list of what is going on with the usb core when I change the
config from 1 to 2. I started at poweron and captured the different states.
>
> Am Dienstag, 25. Oktober 2005 22:01 schrieb Mike King:
> > Oliver,
> >
> > > Hi,
> > >
> > > could you post the decoded version? Are you sure your driver's tables
> > > match the second configuration's interface?
> > >
> > > Regards
> > > Oliver
> > >
> >
> > A quick c
Am Dienstag, 25. Oktober 2005 22:01 schrieb Mike King:
> Oliver,
>
> > Hi,
> >
> > could you post the decoded version? Are you sure your driver's tables
> > match the second configuration's interface?
> >
> > Regards
> > Oliver
> >
>
> A quick cut-n-paste from Greg's usbvie
Oliver,
> Hi,
>
> could you post the decoded version? Are you sure your driver's tables
> match the second configuration's interface?
>
> Regards
> Oliver
>
A quick cut-n-paste from Greg's usbview yields the following. And my driver
does match the second config. Actually,
Am Dienstag, 25. Oktober 2005 21:42 schrieb Mike King:
> Device Desc
> : 12 01 10 01 ff ff ff 08 ff 08 06 34 21 05 00 02
> 0010: 00 02
> Config 1 Desc
> : 09 02 49 00 02 01 00 a0 32 09 04 00 00 02 ff ff
> 0010: ff 00 07 05 81 02 20 00 00 07 05 02 02 08 00 00
Oliver,
>
> Am Dienstag, 25. Oktober 2005 20:22 schrieb Mike King:
> > Usb Gurus,
> >
> > I am working on a biometric device (fingerprint reader) for Linux. This
> > device has 2 configs and I need to use the 2nd config. On initial connect
> > to the system usb core selects config #1 and my dr
Am Dienstag, 25. Oktober 2005 20:22 schrieb Mike King:
> Usb Gurus,
>
> I am working on a biometric device (fingerprint reader) for Linux. This
> device has 2 configs and I need to use the 2nd config. On initial connect
> to the system usb core selects config #1 and my driver claims the interfac
12 matches
Mail list logo
