From: Roland Dreier <roland@topspin.com>
To: "Sangmoon Kim" <dogoil@etinsys.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: map iomem in linux_2_4_dev
Date: 28 May 2002 22:47:21 -0700 [thread overview]
Message-ID: <52k7pntsie.fsf@topspin.com> (raw)
In-Reply-To: <002b01c206cd$59f7a760$1a11efcb@industrialDiv.hanasys.co.kr>
>>>>> "Sangmoon" == Sangmoon Kim <dogoil@etinsys.com> writes:
Sangmoon> Actually, I'm a hardware guy. In most cases, mapping
Sangmoon> UART is not needed, but on the hardware I designed, it
Sangmoon> is needed. Because its physical addres is 0x78000000.
You do not need to remap the UART. It doesn't matter that 0x78000000
is its address. Linux will not get confused between physical address
of the UART and any virtual address space it may be using. Just call
ioremap() and give it the address 0x78000000. It will give you a
virtual address you can use to access the UART.
Best,
Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-29 5:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 10:38 map iomem in linux_2_4_dev Sangmoon Kim
2002-05-28 13:23 ` Matt Porter
2002-05-29 4:57 ` Sangmoon Kim
2002-05-29 5:47 ` Roland Dreier [this message]
2002-05-29 6:01 ` Sangmoon Kim
2002-05-29 5:47 ` David Gibson
2002-05-29 6:14 ` Sangmoon Kim
2002-05-29 12:48 ` shaowei dai
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 5:59 shaowei dai
2002-05-27 6:34 ` David Gibson
2002-05-27 6:51 ` shaowei dai
2002-05-27 8:13 ` Sangmoon Kim
2002-05-27 8:13 ` shaowei dai
2002-05-28 0:36 ` David Gibson
2002-05-28 4:42 ` Sangmoon Kim
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=52k7pntsie.fsf@topspin.com \
--to=roland@topspin.com \
--cc=dogoil@etinsys.com \
--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).