From: Wolfgang Denk <wd@denx.de>
To: Dean Matsen <deanmatsen@earthlink.net>
Cc: Stephan Linke <Stephan.Linke@epygi.de>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: parallel I/O ports & opend darin pins on MPC8xx
Date: Wed, 09 Jul 2003 21:57:14 +0200 [thread overview]
Message-ID: <20030709195719.9BBF5C6D82@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 09 Jul 2003 12:25:00 PDT." <3F0C6C0C.8040306@earthlink.net>
In message <3F0C6C0C.8040306@earthlink.net> you wrote:
>
> >Solution? What is so difficult about latching your output value in a
> >variable?
> >
> What he's saying is that OTHER drivers read the input and then write
> that value to the output.
I did understand this.
> In his driver, he can latch the output through a variable, but that
> won't affect what other
Obviously all drivers that may modify bits in this I/O port will have
to share the variable used to latch the value.
Yes, this may include modifying existing code in the UART or Ethernet
or other drivers.
> Unless there is kernel support to alias the data in a memory variable
> (and it doesn't sound like
> there is), then this is going to continue to be a problem. Might I
Don't make it unnecessary complicated. You don't need "kernel support
to alias the data in a memory variable". This is really not so
difficult to implement yourself when you need it.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The so-called "desktop metaphor" of today's workstations is instead
an "airplane-seat" metaphor. Anyone who has shuffled a lap full of
papers while seated between two portly passengers will recognize the
difference -- one can see only a very few things at once.
- Fred Brooks, Jr.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-07-09 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F0C6C0C.8040306@earthlink.net>
2003-07-09 19:57 ` Wolfgang Denk [this message]
[not found] ` <3F0C7782.3060704@earthlink.net>
2003-07-09 20:17 ` parallel I/O ports & opend darin pins on MPC8xx Wolfgang Denk
2003-07-09 20:20 ` Dean Matsen
[not found] <FCEAKDJJAPHPLJFINDAJEEGGDEAA.Stephan.Linke@epygi.de>
2003-07-09 12:09 ` Wolfgang Denk
[not found] <FCEAKDJJAPHPLJFINDAJCEGCDEAA.Stephan.Linke@epygi.de>
2003-07-09 10:24 ` Wolfgang Denk
2003-07-08 15:31 Stephan Linke
2003-07-08 15:49 ` Craig Hollabaugh
2003-07-08 21:36 ` Wolfgang Denk
2003-07-09 4:57 ` None Atall
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=20030709195719.9BBF5C6D82@atlas.denx.de \
--to=wd@denx.de \
--cc=Stephan.Linke@epygi.de \
--cc=deanmatsen@earthlink.net \
--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).