Hi Ian,
On Aug 30, 2012, Ian Campbell wrote:
I've just tried injecting the following onto the head of the zImage (in
a similar manner to flash-kernel's set_machine_id function):
[...]
This works around the issue on my dreamplug (this is effectively the
same code sequence as what the u-boot
On Mon, 2012-09-10 at 23:09 -0700, Jonathan Nieder wrote:
Hi Ian,
On Aug 30, 2012, Ian Campbell wrote:
I've just tried injecting the following onto the head of the zImage (in
a similar manner to flash-kernel's set_machine_id function):
[...]
This works around the issue on my dreamplug
Ian Campbell wrote:
My main concern with doing this on the kernel side is that it will
eventually fall foul of the attempts to reduce everything to a single
kernel image, since the code will necessarily be quite kirkwood specific
and run very early on.
Is it possible to do something
On Tue, 2012-09-11 at 03:57 -0700, Jonathan Nieder wrote:
Ian Campbell wrote:
My main concern with doing this on the kernel side is that it will
eventually fall foul of the attempts to reduce everything to a single
kernel image, since the code will necessarily be quite kirkwood specific
A while back a bug was discovered in u-boot on the kirkwood platform
which prevented modern kernels from booting[0]. Specifically u-boot was
failing to disable the L2 cache which interacts badly with kernels using
CONFIG_ARM_PATCH_PHYS_VIRT. CONFIG_ARM_PATCH_PHYS_VIRT relates to
running a single
5 matches
Mail list logo