From: Michael Burkey <mdburkey@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Porting barebox (devicetree) to Variscite iMX6 SOM
Date: Thu, 9 Jan 2014 14:59:33 -0500 [thread overview]
Message-ID: <CAJyuEefHk_D6U5Tkrf0CKVfRZ2VSxmfOE4TepG9G1yP9YvF24Q@mail.gmail.com> (raw)
In-Reply-To: <CAJyuEedJxNN9mPJzAvE6d6kNHCaEqcF-BED0L+r2VCv7e6=T6A@mail.gmail.com>
Sascha,
Since I am still having issues with the kernel booting -- and needed a
bit of a break to clear my mind -- I decided to delve into the initial
barebox bootup from NAND a bit more.
Correct me if I am wrong, but how I understand things right now...
The iMX6 requires a BCB header prior to the actual barebox partition
(e.g. nand0.bootstream). This bootstream partition would contain the
BCB data specific to the iMX6 (i.e. an FCB and at least a partial
DBBT).
It also looks like this functionality is already present in barebox
for the MX23/28 series of parts (i.e. the "bcb" command).
I also have the source for kobs-ng v1.3, which does properly generate
the BCB for the MX6 series (and is what I am currently using to flash
barebox into NAND).
So, basically, it sounds like what I need to do is migrate the bcb.c
file from the arm/mach-mxs folder into the MX6 portion of the tree and
then update it based on the datasheet and the "known good" parameters
from kobs-ng v1.3 (which look fairly similar to the definitions you
already have in place for the MX23/28 FCB).
Does this sound like a reasonable plan of action?
It really looks like life with the iMX6 would be much easier if I had
a SPI-NOR on this SOM, instead of NAND only.
Thanks,
Michael Burkey
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-01-09 19:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 17:07 Michael Burkey
2013-12-11 23:17 ` Alexander Aring
2013-12-12 8:04 ` Sascha Hauer
2013-12-12 18:49 ` Michael Burkey
2013-12-12 18:56 ` Michael Burkey
2013-12-12 19:12 ` Alexander Aring
2013-12-12 19:24 ` Michael Burkey
2013-12-12 19:58 ` Sascha Hauer
2013-12-12 22:44 ` Michael Burkey
2013-12-18 16:39 ` Michael Burkey
2013-12-18 21:34 ` Michael Burkey
2013-12-19 8:09 ` Sascha Hauer
2014-01-09 7:20 ` Michael Burkey
2014-01-09 19:59 ` Michael Burkey [this message]
2014-01-10 8:00 ` Sascha Hauer
2014-01-10 8:13 ` Sascha Hauer
2014-01-15 18:35 ` Michael Burkey
2014-01-16 14:13 ` Sascha Hauer
2014-01-16 21:18 ` Michael Burkey
2014-01-20 8:00 ` Sascha Hauer
2014-01-29 21:10 ` Michael Burkey
2014-01-29 21:53 ` Michael Burkey
2014-02-01 18:35 ` Sascha Hauer
2014-02-04 21:44 ` Michael D. Burkey
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=CAJyuEefHk_D6U5Tkrf0CKVfRZ2VSxmfOE4TepG9G1yP9YvF24Q@mail.gmail.com \
--to=mdburkey@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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