From: DaveKucharczyk <david.kucharczyk@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] porting u-boot, MMU question
Date: Wed, 5 Nov 2014 10:16:42 -0700 (MST) [thread overview]
Message-ID: <1415207802518-194767.post@n7.nabble.com> (raw)
In-Reply-To: <545A5726.70800@denx.de>
Stefano, thank you for the very fast response. :)
Stefano Babic wrote
> Instead of doing this, I think it will be easier if you start from the
> current mx53loco nad make the customization for your board. Freescale's
> U-Boot (2009.08) and mainline diverged, as well as some internal API.
Initially that's what I wanted to do, but we have too many changes and I was
told to do it this way. Needless to say it's very slow going.
Stefano Babic wrote
> You do not need to care about that. Cache is activated per default with
> mx5/mx6, if you do not explicitely deactivate it in your config file.
> You do not need to bother about MMU setup in your board files.
Ok thanks. Why did the old U-Boot (2009.08) loco board file have the MMU
stuff and the new U-Boot (2014.07) loco board file doesn't?
--
View this message in context: http://u-boot.10912.n7.nabble.com/porting-u-boot-MMU-question-tp194761p194767.html
Sent from the U-Boot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-11-05 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 16:36 [U-Boot] porting u-boot, MMU question DaveKucharczyk
2014-11-05 16:58 ` Stefano Babic
2014-11-05 17:16 ` DaveKucharczyk [this message]
2014-11-05 21:04 ` Stefano Babic
2014-11-05 21:24 ` Otavio Salvador
2014-11-06 20:03 ` DaveKucharczyk
2014-11-10 15:14 ` [U-Boot] porting u-boot, few final questions DaveKucharczyk
2014-11-10 15:30 ` Fabio Estevam
2014-11-10 15:47 ` Wolfgang Denk
2014-11-10 16:04 ` Fabio Estevam
2014-11-10 17:54 ` Nikolay Dimitrov
2014-11-10 20:45 ` DaveKucharczyk
2014-11-10 22:21 ` DaveKucharczyk
2014-11-11 17:39 ` DaveKucharczyk
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=1415207802518-194767.post@n7.nabble.com \
--to=david.kucharczyk@gmail.com \
--cc=u-boot@lists.denx.de \
/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