On 2015-05-25, Cyril Brulebois wrote: > Vagrant Cascadian <vagrant@debian.org> (2015-05-24): >> On 2015-05-24, Cyril Brulebois wrote: >> > Vagrant Cascadian <vagrant@debian.org> (2015-05-20): >> >> The version of u-boot in experimental requires some changes for >> >> debian-installer to generate appropriate u-boot images. ... >> Both hummingboard and cubox-i use the new mx6cuboxi u-boot target, not >> sure where exactly to document that. They're nearly identical hardware, >> largely differing in physical form-factor; cubox-i is crammed into a >> tiny cube, hummingboard is your more typical dev board (in fact, >> virtually identical footprint to the raspberry pi). > > Sorry, I was a bit lazy yesterday… > > Now that I've looked at board/solidrun/mx6cuboxi/mx6cuboxi.c it seems > one is supposed to distinguish between boards by toying with GPIOs > (mx6cuboxi.c in u-boot), so nothing for d-i to worry about, as long as > the user picks the right bits for the relevant device (e.g. the right > SD-Card concatenateable images)? Exactly. > This means this list (including board → devices mapping) should be kept > uptodate: > https://www.debian.org/releases/jessie/armhf/ch02s01.html#armhf-armmp-supported-platforms > > Does that make sense, or did I just lose myself in (h)arm-land? None of these changes apply to jessie yet; they're all targeted at stretch so far. That page also only lists the information about the kernel, not u-boot or the SD-card images... might require some restructuring to get more specific about the images available. live well, vagrant
Attachment:
signature.asc
Description: PGP signature