From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Fri, 04 Mar 2011 02:30:40 +0100 Subject: [U-Boot] [beagleboard] Re: [PATCH v3] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr In-Reply-To: References: <1299022621-2780-1-git-send-email-jkridner@beagleboard.org> <1299097582-12206-1-git-send-email-jkridner@beagleboard.org> <4D6ED59B.7060409@ahsoftware.de> Message-ID: <4D7040C0.8070006@ahsoftware.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello, Am 03.03.2011 16:04, schrieb Jason Kridner: > On Wed, Mar 2, 2011 at 6:48 PM, Robert Nelson wrote: >> On Wed, Mar 2, 2011 at 5:41 PM, Alexander Holler 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