From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [beagleboard] Re: [PATCH v3] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr
Date: Fri, 04 Mar 2011 02:30:40 +0100 [thread overview]
Message-ID: <4D7040C0.8070006@ahsoftware.de> (raw)
In-Reply-To: <AANLkTi=TSfb+Mqf2UWOEN+cSyiSNshqyjTin6K4VAxE2@mail.gmail.com>
Hello,
Am 03.03.2011 16:04, schrieb Jason Kridner:
> On Wed, Mar 2, 2011 at 6:48 PM, Robert Nelson<robertcnelson@gmail.com> wrote:
>> On Wed, Mar 2, 2011 at 5:41 PM, Alexander Holler<holler@ahsoftware.de> wrote:
>>> Hello Jason,
>>>
>>> Am 02.03.2011 21:26, schrieb Jason Kridner:
>>>>
>>>> For backwards compatibility the use of boot.scr is still supported.
>>>>
>>>
>>> Sorry, but I think that line in the description should get removed too.
>
> I'll submit a v4.
>
>>>
>>
>> So, just a thought.. Are you guys planning to push this same boot
>> method to all the other "omap" devices that just finally got boot.scr
>> boot support by default in u-boot? It also seems's like it'll end up
>> be the FAQ of the month for the beagleboard group.. ;)
>
> Indeed it is likely to be FAQ of the month, especially if it lands in
> the next software update that gets shipped with the board. It is a
> case, however, in which I like the answer--no more need to run
> mkimage. The conversion process of a boot.scr script (commands) to a
> uEnv.txt file (variable setting) won't be exactly trivial, so that has
> me a tiny bit concerned. Still, most cases will be solved by a *much*
> simpler uEnv.txt script and an overall simpler process.
Hmm, if someone will write such an FAQ-entry, be sure to mention that
people shouldn't use a windows-editor. I haven't tried it, but I don't
believe env import likes carriage returns.
Regards,
Alexander
next prev parent reply other threads:[~2011-03-04 1:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 23:08 [U-Boot] [PATCH] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr Alexander Holler
2011-02-04 17:41 ` Jason Kridner
2011-03-01 23:37 ` [U-Boot] [PATCH v2] " Jason Kridner
2011-03-02 2:54 ` Alexander Holler
2011-03-02 15:44 ` Jason Kridner
2011-03-02 17:47 ` Alexander Holler
2011-03-02 19:55 ` Alexander Holler
2011-03-02 20:26 ` [U-Boot] [PATCH v3] " Jason Kridner
2011-03-02 23:41 ` Alexander Holler
2011-03-02 23:48 ` [U-Boot] [beagleboard] " Robert Nelson
2011-03-03 15:04 ` Jason Kridner
2011-03-04 1:30 ` Alexander Holler [this message]
2011-03-04 1:43 ` [U-Boot] " Alexander Holler
2011-03-04 1:51 ` Robert Nelson
2011-03-03 15:08 ` [U-Boot] [PATCH v4] " Jason Kridner
2011-03-05 12:31 ` Alexander Holler
2011-03-05 12:50 ` Alexander Holler
2011-03-13 21:26 ` Wolfgang Denk
2011-04-18 21:35 ` [U-Boot] [PATCH v3] " Paulraj, Sandeep
2011-04-18 23:01 ` Wolfgang Denk
2011-04-18 23:32 ` Paulraj, Sandeep
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=4D7040C0.8070006@ahsoftware.de \
--to=holler@ahsoftware.de \
--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