On Mar 12, 2014 5:28 PM, "Peter Robinson" <pbrobinson@xxxxxxxxx> wrote:
>
> >>> Bad news: I've tested it with the Pandaboard ES B3 boards, and the
> >>RAM
> >>> issue is still present.
> >>
> >>What version of the uboot did you use? Did you read my point and link
> >>to the 2014.01 that should have the fix for that?
> >
> > Ah yes, of course. I'll see if I can look into that tomorrow.
> >
> >>> Where can I store the uEnv commands to avoid having to enter them
> >>manually
> >>> each time that I boot the board?
> >>
> >>It will come in an updated version of the arm-boot-config package as
> >>mentioned. We're just testing the changes to make sure it doesn't
> >>regress other platforms, it'll come via the usual Fedora update
> >>process and I'll be announcing it here once it's ready to go.
> >
> > Okay, thanks. Will there be a respin of the official ARM images? What sort of timescale are we talking about here?
>
> No, although there will be a new arm-boot-config rpm likely tomorrow
> which will go out through the usual update mechanism. Once it's on
> it's way to updates I'll add the details here for reference.
>
I also tested omap5 uEVM with the same setup (using f21 xfce vfat nightly) and it happily booted into the Initrd but the switch root failed because external mmc (micro sdcard) device was not found. The internal mmc is visible from dracut emergency shell, so I guess the driver works. :-)
so the good news is the uboot setup works elsewhere, and omap5 kernel boots (mostly). Will give bone black a whirl with same configuration later. (Also has internal & external mmc)
Sry to hijack the thread, but it seems to me a "works for me too" situation. Congrats for solving panda omap4 issue! ;-)
Thanks
-jon
_______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
