[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel

On 2014-12-26, Ian Campbell wrote:
> On Wed, 2014-12-24 at 12:42 -0800, Vagrant Cascadian wrote:
>> The following patch adds an additional Machine entry for the more
>> specific name. Not sure if there's a more elegant way to add an entry
>> that's simply a duplicate of another entry with a different Machine id.
> It's permissible to have multiple Machine entries in a stanza, so if the
> only difference is that field then it's fine to just add a new one (a
> bunch of the kirkwood TS-xxx enties follow this pattern since they have
> a boardfile name and a DTB name).

Ok, then I think we should simply add the second Machine entry to the
same stanza...

> I wonder though if the DTB-Id field should be different? I think not on
> the basis that the difference is down to
> git.kernel.org/linus/9a15fff05b702c3ea29ae64db0d3ff0355431eab 

If you change the DTB-Id to be for the BeagleBone white, it will break
on BeagleBone Black running kernels 3.16 or earlier, including the
kernel shipped on the BeagleBone Black eMMC by the vendor, making it
harder to "upgrade" to a pure Debian system.

I'm not sure that the BeagleBone white is actually supported in Debian's
kernel or in Debian's flash-kernel... so it doesn't make much sense to
add support now, when that would break a currently supported platform.

> I wonder if 9a15fff ought to be backported to the kernel in Jessie and
> correspondingly whether this flash-kernel change ought to happen in
> Jessie too (otherwise I'd just put it in experimental for the rest of
> the freeze).

I think it would make sense to support both Machine IDs for the
BeagleBone Black in Jessie's flash-kernel regardless of weather the
change was backported to the kernel, as it can result in an unbootable

Running 3.16.x, install linux-image-3.18*, flash-kernel updates the boot
script without complaint. Reboot to 3.18.x. Remove linux-image-3.18*,
flash-kernel fails to update /boot/boot.scr, system is unbootable...

Basically long-running inability to distinguish between the white and
black models make this impossible to "get right" for both, but I believe
there are far more BeagleBone Black systems in the wild, and is better
supported out of the box. It would be better to require manual
intervention on the BeagleBone white models than the other way around.

live well,

Attachment: signature.asc
Description: PGP signature

Reply to: