From: Nishanth Menon <menon.nishanth@gmail.com>
To: Juha Kuikka <juha.kuikka@gmail.com>
Cc: Nishanth Menon <nm@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Greg Ungerer <gerg@snapgear.com>
Subject: Re: OMAP3: Linux Without a Boot Loader?
Date: Mon, 26 Apr 2010 20:31:57 -0500 [thread overview]
Message-ID: <4BD63E8D.1090701@gmail.com> (raw)
In-Reply-To: <i2ra46a26fd1004261722sd0c56aafj90275e805502e9db@mail.gmail.com>
On 04/26/2010 07:22 PM, Juha Kuikka wrote:
> On Mon, Apr 26, 2010 at 4:19 PM, Nishanth Menon<nm@ti.com> wrote:
>>
>> The final image looks as follows:
>> +---------------------+
>> | Configuration |
>> | Header |
>> +---------------------+
>> | "Sty" |
>> +---------------------+
>> | kernel piggy |
>> | bzImage |
>> +---------------------+
>>
> Looks very interesting! I was thinking of trying something like this
> after ELC but unfortunately real work got the better of me.
>
> This Configuration Header stuff looks very similar to what TI's
> Davinci-chips use. They call it AIS but from a short dive into
> omap-u-boot-utils it is very similar, encoded commands to mask ROM
> code to initialize HW and load image(s).
>
> Now I need to find some time to do this with the Beagle.
>
> This may be a stupid question but is the CH format documented somewhere?
Yep, I had blogged about it some time back:
http://nishanthmenon.blogspot.com/2009/05/configuration-header-no-more-x-loader.html
You can find more about CH and references there, and yes, Beagle is one
of the first platforms I had working :)
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-04-27 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 23:19 OMAP3: Linux Without a Boot Loader? Nishanth Menon
2010-04-27 0:22 ` Juha Kuikka
2010-04-27 1:31 ` Nishanth Menon [this message]
2010-04-27 3:53 ` Greg Ungerer
2010-04-27 3:53 ` Greg Ungerer
2010-04-27 10:31 ` Nishanth Menon
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=4BD63E8D.1090701@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=gerg@snapgear.com \
--cc=juha.kuikka@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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.