From: Michael Stevens <mstevens@etla.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry 9
Date: Wed, 24 Apr 2013 13:24:44 +0100 [thread overview]
Message-ID: <20130424122443.GB9540@ceres.etla.org> (raw)
In-Reply-To: <081a1c3e84eaabe3786cc55aaaab8309@coraid.com>
On Tue, Apr 23, 2013 at 05:48:15PM -0400, erik quanstrom wrote:
> > I've started trying this this week, and it works, but I get a lot of USB
> > errors from my keyboard. However so far the keyboard works.
>
> use a powered hub.
Tried this, seems to eliminate the runtime console errors, but I still
get a "Report type 0x13 bad" at boot time.
Michael
next prev parent reply other threads:[~2013-04-24 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 21:13 OrangeCalx01
2013-04-23 21:23 ` Michael Stevens
2013-04-23 21:45 ` Jeremy Jackins
2013-04-23 21:48 ` erik quanstrom
2013-04-24 12:24 ` Michael Stevens [this message]
2013-04-24 20:19 ` Jeremy Jackins
2013-04-23 22:59 ` Andrés Domínguez
2013-04-24 0:33 ` a
2013-04-24 9:17 ` Richard Miller
2013-04-25 11:38 OrangeCalx01
2013-06-02 18:46 Richard Miller
2013-06-24 9:10 ` Ralf Schülke
2013-06-24 13:55 ` Richard Miller
2013-06-26 13:44 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=20130424122443.GB9540@ceres.etla.org \
--to=mstevens@etla.org \
--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).