On Mon, 30 Jul 2007, Chris Ball wrote:
> Here's a screenshot comparing the broken/working traces, with NAKs hidden:
>
>http://dev.laptop.org/~cjb/macntouch.png
Too low-resolution to see anything. But it doesn't matter since the
log file has most of the info.
> Both traces are from pluggin
Hi Alan,
> So I guess the next step is to try the USB analyzer. It will allow
> us to see the missing data and to check that the interrupt endpoint
> is getting polled as it should be.
Here's a screenshot comparing the broken/working traces, with NAKs hidden:
http://dev.laptop.org/~
On Sun, 29 Jul 2007, Chris Ball wrote:
> Thanks very much for the reply, Alan.
>
>>> I have a MacNTouch keyboard[1]. The keyboard works on all of my
>>> Linux machines except one, a Powerbook. Other USB keyboards work
>>> in the same USB port on the Powerbook, so it doesn't seem lik
Thanks very much for the reply, Alan.
>> I have a MacNTouch keyboard[1]. The keyboard works on all of my
>> Linux machines except one, a Powerbook. Other USB keyboards work
>> in the same USB port on the Powerbook, so it doesn't seem like a
>> hardware failure on either the Powerbook
On Fri, 27 Jul 2007, Chris Ball wrote:
> Hello,
>
> I have a MacNTouch keyboard[1]. The keyboard works on all of my Linux
> machines except one, a Powerbook. Other USB keyboards work in the same
> USB port on the Powerbook, so it doesn't seem like a hardware failure
> on either the Powerbook or
