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. > >> > >> The mx6_cubox-i target which was not previously upstream, is now named > >> mx6cuboxi upstream; I've updated the u-boot package accordingly with > >> patches from mainline u-boot. It also supports the hummingboard-i1 and > >> hummingboard-i2ex, not sure how to make that clear. > > > > I suppose I'm a bit surprised that there are no added lines for > > hummingboard-*? > > 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)? 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? Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature