From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Building a Raspberry Pi image / Keyboard support
Date: Mon, 7 Jul 2014 12:09:02 -0400 [thread overview]
Message-ID: <4c6f701f691988b89861e226ad2ce2b1@ladd.quanstro.net> (raw)
In-Reply-To: <CA+MHcSrwO8ZmoM3DceuTQ2Q8KRwUTqnEDny-Oh_j3ODba5h0hA@mail.gmail.com>
On Sat Jul 5 19:46:36 EDT 2014, anant@kix.in wrote:
> Thanks for the suggestions. The keyboard + mouse work fine with Linux. In
> fact they work on Plan 9 together, but only for a few seconds before I get:
>
> kb: /dev/usb/ep6.1: read: i/o error
> kb: exiting
> usbotg: ep5.1 error intr 00000082
> usb/kb... kb: exiting
i see these sometimes, too. a formerly working apple full sized wired keyboard
has stopped working with these errors. i assume it's something tricky.
however, 9atom has some keyboard/mouse fixes that might be worth checking up
on. the original version asked for pretty big descriptors from the device, and many
devices generate transaction errors, or otherwise do bad things™ when asked for
a descriptor bigger than they envisioned. the solution is to ask for the minimum size
descriptor plus enough space to get the descriptor length, then ask again with the
device-provided length.
- erik
next prev parent reply other threads:[~2014-07-07 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 6:01 Anant Narayanan
2014-07-02 6:32 ` Bakul Shah
2014-07-04 23:45 ` Anant Narayanan
2014-07-05 0:58 ` kokamoto
2014-07-05 7:01 ` Steve Simon
2014-07-06 1:15 ` kokamoto
2014-07-06 5:59 ` Shane Morris
2014-07-07 4:58 ` kokamoto
2014-07-07 5:58 ` kokamoto
2014-07-07 16:02 ` erik quanstrom
2014-07-07 23:12 ` kokamoto
2014-07-08 0:20 ` erik quanstrom
2014-07-08 23:35 ` kokamoto
2014-07-05 8:20 ` Charles Forsyth
2014-07-05 9:01 ` Bakul Shah
2014-07-05 13:13 ` Ramakrishnan Muthukrishnan
2014-07-05 23:44 ` Anant Narayanan
2014-07-07 16:09 ` erik quanstrom [this message]
2014-07-07 9:30 Richard Miller
2014-07-07 13:26 ` kokamoto
2014-07-07 9:30 Richard Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c6f701f691988b89861e226ad2ce2b1@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).