On Fri, May 30, 2014 at 12:28:00PM +0100, Ian Campbell wrote: > > Then I manually set the u-boot (setenv) and got the the > > sytem up and running. > > The are a few open issues left though. Any feedback and guidance if I am > > on the right track here is welcome. > > 1) For each reboot, I manually have to enter the u-boot setup > > I could use the u-boot cmd interface to save to set the settings when > > once configured correctly. Is that the way to go? > > Is there a way to set the proper settings from Debian itself (e.g. > > create a u-boot.img and dd it into the mmc) ? > > 2) For each kernel update, I have to convert them to u-boot images using > > mkimage > > Would creating a flash-kernel db here be the way to go? > I think so, yes. > The best answer to #1 would be that flash-kernel would create/populate > the right thing that the factory default u-boot settings would find and > boot it (what this involves depends very, much on the platform it might > mean writing /boot/boot.scr or it might mean writing uImage to a > specific flash partition etc) There is already a branch for this in flash-kernel git, which I was waiting for u-boot support on in unstable before proposing for merge. U-Boot support is there now, so maybe this is mergeable now. Ian, would you like a bug report for this? git://git.debian.org/d-i/flash-kernel.git cubox-i -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature