From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi: won't recognize the USB mouse
Date: Fri, 28 Feb 2014 08:24:49 -0800 [thread overview]
Message-ID: <20140228162449.BB1BFB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 28 Feb 2014 09:45:42 EST." <DAEA5DDB-72FB-4BE1-A231-FE8546294E41@9srv.net>
On Fri, 28 Feb 2014 09:45:42 EST Anthony Sorace <a@9srv.net> wrote:
>
> Based on my own experience with USB weirdness with the Pi, I still suspec
> power issues. How are you powering the Pi itself? Using a 1 amp supply yielded
> problems, regardless of the sort of hub I had, which all went away when I
> switched to a 2 amp supply. I'm told the second generation of these boards are
> a bit better on that regard, but I don't have any to test.
The RasPi FAQ suggest 1.2A or more. In rev 2 they replaced two
current limiting polyfuses with shunts so you can use a a
powered hub or connect periphs requiring > 100mA.
The RasPi wastes a lot of power. Its processor require 1.8V
and only the USB requires 5V. For battery powered use people
have tried a number of tricks to reduce power use: replace the
onboard linear reg. with a switcher or two, tie 5V + 3.3V
together and only use a USB periphs that runs on 3.3V & use
model A Raspi -- the ethernet chip on model B draws a lot of
power even when idle and you don't need it for wifi.
Apparently Ralink RT5370 basedt cheapo wifi dongles can run on
3.3V.
For robotics use we need a usb wifi driver!
next prev parent reply other threads:[~2014-02-28 16:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 16:27 Ramakrishnan Muthukrishnan
2014-02-26 17:19 ` Richard Miller
2014-02-27 16:27 ` Ramakrishnan Muthukrishnan
2014-02-27 16:35 ` Ramakrishnan Muthukrishnan
2014-02-27 17:05 ` Ramakrishnan Muthukrishnan
2014-02-27 17:08 ` Lyndon Nerenberg
2014-02-27 17:31 ` Ramakrishnan Muthukrishnan
2014-02-27 18:03 ` Bakul Shah
2014-02-28 11:10 ` Ramakrishnan Muthukrishnan
2014-02-28 11:28 ` Richard Miller
2014-02-28 14:12 ` Ramakrishnan Muthukrishnan
2014-02-28 14:35 ` Bakul Shah
2014-02-28 15:12 ` Ramakrishnan Muthukrishnan
2014-02-28 14:45 ` Anthony Sorace
2014-02-28 15:15 ` Ramakrishnan Muthukrishnan
2014-02-28 16:24 ` Bakul Shah [this message]
2014-03-04 14:12 ` Ramakrishnan Muthukrishnan
2014-03-04 14:27 ` erik quanstrom
2014-03-04 15:54 ` Ramakrishnan Muthukrishnan
2014-03-04 16:26 ` erik quanstrom
2014-03-04 18:18 ` Bakul Shah
2014-03-04 18:26 ` erik quanstrom
2014-03-08 14:56 ` Ramakrishnan Muthukrishnan
2014-03-08 14:59 ` erik quanstrom
2014-03-09 13:25 ` Ramakrishnan Muthukrishnan
2014-03-09 13:46 ` erik quanstrom
2014-03-05 10:57 ` Richard Miller
2014-03-05 10:59 ` Richard Miller
2014-02-27 17:10 ` erik quanstrom
2014-02-27 17:15 ` Steve Simon
2014-02-26 17:22 ` Ramakrishnan Muthukrishnan
2014-02-28 4:31 ` Grant Mather
2014-02-28 9:05 ` erik quanstrom
2014-03-01 5:43 Michael Hansen
2014-03-01 12:09 ` Richard Miller
2014-03-01 12:12 ` erik quanstrom
2014-03-02 10:46 ` Richard Miller
2014-03-02 14:57 ` erik quanstrom
2014-03-02 19:54 ` Richard Miller
2014-03-02 23:22 ` Winston Kodogo
2014-03-03 1:29 ` erik quanstrom
2014-03-03 11:05 ` Richard Miller
2014-03-03 11:24 ` Richard Miller
2014-03-03 13:39 ` erik quanstrom
2014-03-02 1:12 Michael Hansen
2014-03-02 1:39 ` erik quanstrom
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=20140228162449.BB1BFB827@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--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).