From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com
Subject: 3-color led too bright
Date: Sat, 30 Jan 2016 21:07:50 +0100 [thread overview]
Message-ID: <20160130200750.GB30429@amd> (raw)
Hi!
The indicator 3-color LED in mainline kernel seem to be a bit too
bright. .. more bright to look at comfortably. I believe it is also
brighter than in original maemo... I believe I've seen note somewhere
that hardware may allow too much current to the 3-color led damaging
hardware... but I can't find the link now.
Does anyone know more?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: 3-color led too bright
Date: Sat, 30 Jan 2016 21:07:50 +0100 [thread overview]
Message-ID: <20160130200750.GB30429@amd> (raw)
Hi!
The indicator 3-color LED in mainline kernel seem to be a bit too
bright. .. more bright to look at comfortably. I believe it is also
brighter than in original maemo... I believe I've seen note somewhere
that hardware may allow too much current to the 3-color led damaging
hardware... but I can't find the link now.
Does anyone know more?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2016-01-30 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 20:07 Pavel Machek [this message]
2016-01-30 20:07 ` 3-color led too bright Pavel Machek
2016-01-31 0:24 ` Sebastian Reichel
2016-01-31 0:24 ` Sebastian Reichel
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=20160130200750.GB30429@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.