On 2014-10-01, Karsten Merker wrote:
> On Wed, Oct 01, 2014 at 07:01:44AM +0200, Cyril Brulebois wrote:
>> Karsten Merker <merker@debian.org> (2014-10-01):
> attached is V3 of the patch. I have run a full armhf installer
> build with it without problems and I have done two test installs
> on a Cubietruck with the result (one from USB to SATA and one from
> USB to MMC). Those also have shown no problems.
I got a chance to test the d-i daily images... Thanks for your work on
it!
Overall, it appears to be working quite well. I've thought about
creating a similar bootscript for the netboot images.
> +if test -n "${console}"; then
> + setenv bootargs "${bootargs} console=${console}"
> +fi
It would seem that the console variable isn't consistant across u-boot
platforms. On some (sunxi) it sets both the device and the baudrate
(i.e. console=ttyS0,115200), but on many other platforms console only
sets the device (i.e. console=ttyS0) and linux then reverts to 9600
baud. But the u-boot baudrate is often 115200 with u-boot itself, and
set in a baudrate variable. It doesn't seem possible to set a sane
default...
So basically this "generic" boot script only works with platforms where
the baudrate is included in the "console" variable (or where the
baudrate defaults to 9600, to match linux's default, though I think most
of the armhf platforms at least default to 115200). *sigh*
Not sure if u-boot's shell has the ability to match contents of
variables, so the baudrate could be conditionally added only if not
already present. The only other thing I can think of is setting a
different default serial console baud rate in the kernel, at least for
armhf, but that may have all manner of other consequences.
live well,
vagrant
Attachment:
pgp0hgJMQAYIt.pgp
Description: PGP signature