From: Harri Haataja <realblades@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9pi + apple keyboard
Date: Wed, 23 Jan 2013 10:05:25 +0200 [thread overview]
Message-ID: <CAD8V-zA+1cYJWfMbgduKeqKiSqYoaD_cqyi2SxPOJg=19dsOLw@mail.gmail.com> (raw)
In-Reply-To: <4e3ec2c35ebbcea203b84f774fab99fe@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
On 22 January 2013 19:06, erik quanstrom <quanstro@quanstro.net> wrote:
> > I've seen similar things with my apple keyboard on plan9 with
> > the pi (as well as the failure you noted earlier). the pi is *very*
> > picky about power.
>
USB power management is pretty smart in its way, but can do odd things. And
what different devices do seems to vary. I've tested a wireless dongle that
works in a hub (no extra power) connected to the pi, but won't even detect
when plugged in directly.
sort of sad when the keyboard uses more power than the computer.
>
>
Coming from the embedded side of things, it seems natural to me that the
electromechanical bits tend to eat most of the power budget. I have several
things where a burning indicator LED would more than double the overall
power consumption. On the other hand, good old raw LCD's basically take
nothing. You can run a pocket calculator on a thumbprint's worth of old
solar panel in room light. I always found that kind of amazing.
A desktop keyboard shouldn't be that demanding, though. Saving power just
probably hasn't been a priority in the design.
--
I appear to be temporarily using gmail's horrible interface. I apologise
for any failure in my part in trying to make it do the right thing with
post formatting.
[-- Attachment #2: Type: text/html, Size: 1944 bytes --]
next prev parent reply other threads:[~2013-01-23 8:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 10:31 James Chapman
2013-01-22 10:39 ` Richard Miller
2013-01-22 10:58 ` James Chapman
2013-01-22 17:02 ` a
2013-01-22 17:06 ` erik quanstrom
2013-01-22 17:45 ` Nicolas Bercher
2013-01-22 18:50 ` Aram Hăvărneanu
2013-01-23 7:46 ` Lyndon Nerenberg
2013-01-22 21:36 ` erik quanstrom
2013-01-23 10:36 ` Richard Miller
2013-01-23 10:55 ` Lluís Batlle i Rossell
2013-01-23 12:11 ` Richard Miller
2013-01-23 15:45 ` Nicolas Bercher
2013-01-23 15:48 ` erik quanstrom
2013-01-23 21:10 ` erik quanstrom
2013-01-23 22:21 ` Richard Miller
2013-01-23 22:37 ` erik quanstrom
2013-01-23 23:15 ` Richard Miller
2013-01-23 23:33 ` erik quanstrom
2013-01-24 1:37 ` erik quanstrom
2013-01-24 10:29 ` Phineas Pett
2013-01-24 12:42 ` lucio
2013-01-24 13:06 ` Phineas Pett
2013-01-24 13:33 ` lucio
2013-01-24 13:40 ` Richard Miller
2013-01-24 14:55 ` lucio
2013-01-24 20:56 ` Steve Simon
2013-01-24 15:16 ` erik quanstrom
2013-01-26 11:59 ` Lluís Batlle i Rossell
2013-01-26 12:12 ` erik quanstrom
2013-01-26 13:18 ` Lluís Batlle i Rossell
2013-01-23 8:05 ` Harri Haataja [this message]
2013-01-23 10:45 ` Richard Miller
2013-01-23 12:05 ` James Chapman
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='CAD8V-zA+1cYJWfMbgduKeqKiSqYoaD_cqyi2SxPOJg=19dsOLw@mail.gmail.com' \
--to=realblades@gmail.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).