On Mon, 3 Dec 2012, Jan Lübbe wrote:
> Hi,
>
> On Sun, 2012-12-02 at 04:24 -0500, Robert P. J. Day wrote:
> > i've isolated the commit that introduces the apparent booting
> > problem on my xM:
> >
> > $ git show 154496f
> > commit 154496f736db54123c3f6daaba18809fab54ed9b
> > Merge: 05d251f bd6d12b
> > Author: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>
> > Date: Fri Nov 16 14:02:49 2012 +0100
> >
> > Merge branch 'for-next/omap'
>
> *snip*
>
> > so something in that omap merge is causing this.
>
> The merge itself does not actually introduce new code.
>
> Could you try finding the commit with git bisect?
>
> ~/git/barebox $ git bisect start
> ~/git/barebox $ git bisect bad 154496f736db54123c3f6daaba18809fab54ed9b
> ~/git/barebox $ git bisect good 05d251f
> Bisecting: 3 revisions left to test after this (roughly 2 steps)
> [663c466794382f803a69414c935cf0a13d4f0761] ARM OMAP4 panda: switch to new environment
> ~/git/barebox $
>
> Then test this checkout and tell git using "git bisect good" or "git
> bisect bad".
*sigh* ... i *think* i figured out what's happening. in order to
play with barebox on my xM, until recently, i'd done nothing more than
create a single FAT partition on a micro SD card, put MLO and
barebox.bin on it, put it in my xM, and let it boot. until that OMAP
merge, it worked fine.
as i read it, the new default environment for the xM *requires* a
second (ext3) partition or the boot process simply hangs, am i reading
that right? if that's true, how can i adjust that so i can once again
just boot to barebox without having a kernel and root fs created yet?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
