From: Ralph Siemsen <rsiemsen@rossvideo.com>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: ppcembed <linuxppc-embedded@ozlabs.org>
Subject: Re: 2.6 4xx GPIO OCP driver?
Date: Fri, 25 Feb 2005 16:19:41 -0500 [thread overview]
Message-ID: <421F966D.4060206@rossvideo.com> (raw)
In-Reply-To: <20050225133055.A28918@cox.net>
Matt Porter wrote:
> I didn't bother merging it upstream at one time. It wasn't clear
> if the driver had any value over just mmaping /dev/mem to bang
> on the couple gpio registers directly. [...]
Will that work on the 440 where the devices sit above 4GB mark? Or must
one rely on there being an existing TLB mapping to bring them into
32-bit space?
-Ralph
next prev parent reply other threads:[~2005-02-25 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 19:40 2.6 4xx GPIO OCP driver? Steven Blakeslee
2005-02-25 20:25 ` Travis B. Sawyer
2005-02-25 20:30 ` Matt Porter
2005-02-25 20:51 ` Travis B. Sawyer
2005-02-25 21:19 ` Ralph Siemsen [this message]
2005-02-26 0:29 ` Matt Porter
2005-02-26 22:31 ` Travis Sawyer
2005-02-26 22:31 ` Travis B. Sawyer
-- strict thread matches above, loose matches on Subject: below --
2005-02-25 17:17 Travis B. Sawyer
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=421F966D.4060206@rossvideo.com \
--to=rsiemsen@rossvideo.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mporter@kernel.crashing.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).