From: David Saada <David.Saada@ecitele.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Wondering about the PPC parallel I/O handling
Date: Mon, 10 Dec 2007 00:59:17 -0800 (PST) [thread overview]
Message-ID: <14249304.post@talk.nabble.com> (raw)
Hi,
Looking at U-boot's handling of PPC parallel I/O, there are some things I
was wondering about:
- There's no module that's responsible of it. Handling is done in the
cpu_init module alone (among other things). This means that there's some
duplicated code (for instance in the 85xx and 83xx cpu_init modules).
- There's no easy way to read from a port or write to it - one needs to
perform some cumbersome actions on the port registers instead of having
simple read_port and write_port functions.
- For some reason, in the QE PIO configuration table, there's no field for
the port data (relevant for output ports) as it was with CPM2. This requires
to setup all initial values manually.
Are there any plans to reform this piece of code?
Regards,
David.
--
View this message in context: http://www.nabble.com/Wondering-about-the-PPC-parallel-I-O-handling-tp14249304p14249304.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
reply other threads:[~2007-12-10 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14249304.post@talk.nabble.com \
--to=david.saada@ecitele.com \
--cc=u-boot@lists.denx.de \
/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