From: Sylvain Munaut <tnt@246tnt.com>
To: ppc linux embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Getting rid of static IO mapping
Date: Wed, 07 Jul 2004 00:33:43 +0200 [thread overview]
Message-ID: <40EB28C7.5020105@246tNt.com> (raw)
In-Reply-To: <40EB1C28.3000402@246tNt.com>
Sylvain Munaut wrote:
> In the current situation, I use the physical address and there is a
> 1:1 mapping. The mapping is first done by directly manipulating
> {D,I}BAT2, then by setup_io_mappings.
Actually, looking at the code in arch/ppc/mm/init.c
/* Map in all of RAM starting at KERNELBASE */
if (ppc_md.progress)
ppc_md.progress("MMU:mapin", 0x301);
mapin_ram();
#ifdef CONFIG_HIGHMEM
ioremap_base = PKMAP_BASE;
#else
ioremap_base = 0xfe000000UL; /* for now, could be 0xfffff000 */
#endif /* CONFIG_HIGHMEM */
ioremap_bot = ioremap_base;
/* Map in I/O resources */
if (ppc_md.progress)
ppc_md.progress("MMU:setio", 0x302);
if (ppc_md.setup_io_mappings)
ppc_md.setup_io_mappings();
I wonder how it works. At the mapin_ram(), my BAT are overwritten,
then the "MMU:setio" progress is called, but at this point, my BAT is
no longer active and my setup_io_mappings is not yet called. Shouldn't
that crash ? During these two calls, the uart zone shouldn't be mapped.
Sylvain Munaut
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-06 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 21:39 Getting rid of static IO mapping Sylvain Munaut
2004-07-06 22:33 ` Sylvain Munaut [this message]
2004-07-07 3:58 ` Linh Dang
2004-07-07 8:40 ` Sylvain Munaut
2004-07-07 17:07 ` Sylvain Munaut
2004-07-07 20:49 ` Dan Malek
2004-07-07 22:45 ` Sylvain Munaut
2004-07-07 23:41 ` Linh Dang
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=40EB28C7.5020105@246tNt.com \
--to=tnt@246tnt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.