From: Wolfgang Denk <wd@denx.de>
To: Christopher Huffine <huffine@wopr.nrl.navy.mil>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 823 ports access question
Date: Mon, 28 Aug 2000 16:26:04 +0200 [thread overview]
Message-ID: <200008281426.QAA29658@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 28 Aug 2000 07:18:55 EDT." <Pine.LNX.3.96.1000828071718.5707A-100000@wopr.nrl.navy.mil>
In message <Pine.LNX.3.96.1000828071718.5707A-100000@wopr.nrl.navy.mil> you wrote:
>
> Sorry to write another simplistic question; hopefully
> there is a simplistic answer as well:
There is :-)
> PPC ports. For example, the Bright Star
> ipEngine I have has LEDs connected to the LCD ports
> from the PowerPC. I'm looking for the right
> sequence to actually write to these ports and
> get these LEDs to turn on and off.
>
> I've looked in 8xx_immap.h and I start to see
> what I need to make this work (im_lcd), but I'm missing
> the bigger picture. Anyone have any example
> code for anything like this?
See the tqm_led demo driver code under
http://www.denx.de/solutions-en.html#drivers
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Do we define evil as the absence of goodness? It seems only logical
that shit happens--we discover this by the process of elimination."
-- Larry Wall
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-28 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-28 11:18 823 ports access question Christopher Huffine
2000-08-28 14:26 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-28 14:05 Brown, David (dbrown03)
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=200008281426.QAA29658@denx.local.net \
--to=wd@denx.de \
--cc=huffine@wopr.nrl.navy.mil \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).