On Tue, Jun 11, 2002 at 07:01:46PM -0700, David Brownell wrote:
<... ENXIO ...>
> It could be "usbmodules" talking to the device. I've noticed it doing
> that in the midel of some of my testing ... :)
But it happens also without and any other hotplug stuff. I can reproduce the
ENXIO just with
On Tue, Jun 11, 2002 at 07:01:46PM -0700, David Brownell wrote:
> Jun 6 00:56:06 thunderbird kernel: usb-uhci-hcd.c: ENXIO (Control)
> 8400, flags 0, urb efc879c0, burb efc87940, probably device driver
> bug
> >>>
> >>
> >>Ok, this is the usual ENXIO-problem:
> >>
> >>
> >>
Jun 6 00:56:06 thunderbird kernel: usb-uhci-hcd.c: ENXIO (Control)
8400, flags 0, urb efc879c0, burb efc87940, probably device driver
bug
>>>
>>
>>Ok, this is the usual ENXIO-problem:
>>
>>
>> UHCI cannot queue control transfers!
>>
>
>
> Well, the HID cod
On Thu, Jun 06, 2002 at 08:27:34PM +0200, Georg Acher wrote:
> On Thu, Jun 06, 2002 at 10:17:38AM -0700, David Brownell wrote:
> > This info needs to get to HID and/or usb-uhci-hcd folk, not me ... :)
> >
> >
> > Marcelo de Paula Bezerra wrote:
> > >On Thu, 2002-06-06 at 00:55, David Brownell wr
On Fri, 7 Jun 2002 14:35, Marcelo de Paula Bezerra wrote:
> So the keyboard generates 2 event devices?
> 1 for the regular keys, and another for the special keys? (this is
> expected behavior).
Yes. All works fine with OHCI (2.4 and 2.5).
> Anyway, I'll contact the uchi mantainer again.
I did a q
On Thu, 6 Jun 2002 13:52, Brad Hards wrote:
> On Thu, 6 Jun 2002 13:40, Marcelo de Paula Bezerra wrote:
> > On Thu, 2002-06-06 at 00:24, Brad Hards wrote:
> > > I have a similar keyboard (only Rev 1.14). I'll try it out on 2.5.
> > >
> > > Is there any chance that you can test this on another moth
On Thu, Jun 06, 2002 at 10:17:38AM -0700, David Brownell wrote:
> This info needs to get to HID and/or usb-uhci-hcd folk, not me ... :)
>
>
> Marcelo de Paula Bezerra wrote:
> >On Thu, 2002-06-06 at 00:55, David Brownell wrote:
> >
> >
> >>Modify the dbg statement -- it's just a regular printf f
This info needs to get to HID and/or usb-uhci-hcd folk, not me ... :)
Marcelo de Paula Bezerra wrote:
> On Thu, 2002-06-06 at 00:55, David Brownell wrote:
>
>
>>Modify the dbg statement -- it's just a regular printf format,
>>so add a "%d" and pass the return value in the argument list.
>>
>>-
On Thu, 6 Jun 2002 13:46, Marcelo de Paula Bezerra wrote:
> On Thu, 2002-06-06 at 00:24, David Brownell wrote:
> > So, why dies it give up? The diagnostic should give the status code.
> > Just knowing some call fails isn't so useful, but knowing _why_ it
> > does so is half way to knowing what's
On Thu, 6 Jun 2002 13:40, Marcelo de Paula Bezerra wrote:
> On Thu, 2002-06-06 at 00:24, Brad Hards wrote:
> > I have a similar keyboard (only Rev 1.14). I'll try it out on 2.5.
> >
> > Is there any chance that you can test this on another motherboard
> > (especially on OHCI, or an Intel UHCI)?
>
On Thu, 6 Jun 2002 13:06, Marcelo de Paula Bezerra wrote:
> My motherboard is an ASUS A7V133 based on VIA KT133A, the keyboard is a
> Microsoft Internet Keyboard Pro.
I have a similar keyboard (only Rev 1.14). I'll try it out on 2.5.
Is there any chance that you can test this on another motherboa
Marcelo de Paula Bezerra wrote:
> I exchanged some e-mail with Vojtech (input layer and usb_hid mantainer)
> until we found out that hid-core.c was giving up here:
>
> hid-core.c line 1331
> if ((n = hid_get_class_descriptor(dev, interface->bInterfaceNumber,
> HID_DT_REPORT, rdesc, rsize)) < 0) {
I exchanged some e-mail with Vojtech (input layer and usb_hid mantainer)
until we found out that hid-core.c was giving up here:
hid-core.c line 1331
if ((n = hid_get_class_descriptor(dev, interface->bInterfaceNumber,
HID_DT_REPORT, rdesc, rsize)) < 0) {
dbg("reading report descriptor fail
13 matches
Mail list logo
