Bug#658759: u-boot: fails to boot compressed 3.2.y kernels
reassign 658759 src:linux-2.6 3.2.2-1
tags 658759 + upstream
quit
Loïc Minier wrote:
> * kirkwood: disable L2 cache before Linux boot; thanks to Ian Campbell.
> closes: #658904
Thanks!
The next question is what to do to handle Linux upgrades.
Should the kirkwood kernel have "Breaks: u-boot (<< 2011.12-3)" to
encourage people to update their bootloader when they are lucky enough
to be on a machine where the bootloader is installed through the
package management system?
Should there be a flavor-specific NEWS.Debian.gz to warn sysadmins
about the problem? (I think "yes".)
Should the kirkwood flavor disable CONFIG_ARM_PATCH_PHYS_VIRT? (My
hunch is "no, it shouldn't", but that possibility's available if we
wanted to return to the behavior of the good old days of 3.1.y.)
Context: [1]
| Okay, so this should mean that the kernel's own decompressor has run,
| which should turn on/off the mmu and caches, cleaning and invalidating
| them, which will take the boot loader completely out of the picture at
| this stage.
Could the decompressor disable the L2 cache itself as a workaround?
Given that no one with the right familiarity with the decompressor
code has volunteered to do that, I'd suggest:
- teaching u-boot in stable to follow the boot protocol correctly
- adding a NEWS.Debian.gz in the kernel package to warn people
- mentioning this in the armel variant of the wheezy release notes.
Jonathan
[1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/143666/focus=143875
Reply to: