From: Robert Jarzmik <robert.jarzmik@free.fr>
To: barebox@lists.infradead.org
Subject: ARM, MMU and IO space mapping
Date: Thu, 24 Nov 2011 12:24:55 +0100 [thread overview]
Message-ID: <87ipm9yd88.fsf@free.fr> (raw)
Hi,
I was wandering in the MMU arm implementation and I'm wondering if anybody is
using it and accessing some IO mapped space.
My trouble is that mmu_init() only maps the RAM space (and with cacheable memory
type). For the PXA, I would need a non-cacheable non-bufferable memory type,
which could be allocated either :
- through dev_request_mem_region(), which would be amended for the MMU case
- or through a dedicated ioremap() function, which will be empty in no MMU case
The current issue I'm facing is that when I launch barebox with MMU enabled, the
UDC device doesn't work (I presume because the IO space is not mapped into the
MMU). This prevents me from using barebox in MMU context (and therefore I have
no D-Cache).
Would the evolution of dev_request_mem_region() be acceptable, or should I
consider another way ?
Cheers.
--
Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-11-24 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 11:24 Robert Jarzmik [this message]
2011-11-24 12:04 ` Sascha Hauer
2011-11-24 14:23 ` Marc Kleine-Budde
2011-11-24 20:09 ` Robert Jarzmik
2011-11-24 20:25 ` Marc Kleine-Budde
2011-11-25 0:01 ` Sascha Hauer
2011-11-27 22:30 ` Robert Jarzmik
2011-11-28 7:43 ` Sascha Hauer
2011-11-28 17:43 ` Robert Jarzmik
2011-11-29 8:15 ` Sascha Hauer
2011-11-30 22:06 ` Robert Jarzmik
2011-12-01 14:26 ` Sascha Hauer
2011-12-01 14:34 ` Marc Kleine-Budde
2011-12-11 13:01 ` Robert Jarzmik
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=87ipm9yd88.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=barebox@lists.infradead.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