Hi,
Am 04/15/2016 um 07:29 AM schrieb Sascha Hauer:
> On Thu, Apr 14, 2016 at 05:43:30PM +0200, Alexander Aring wrote:
>> Hi,
>>
>> since commit 25362dc ("ARM: 8501/1: mm: flip priority of CONFIG_DEBUG_RODATA")
>> which enables for (in my case) am335x CONFIG_DEBUG_RODATA by default, I notice
>> that my beaglebone white doesn't boot anymore when this config is enabled.
>>
>> I boot current linus/master via barebox v2016.04.0 with zImage format.
>> The following message will be printed:
>>
>> Error: unrecognized/unsupported machine ID (r1 = 0x00000ee0).
>>
>> When I turn off CONFIG_DEBUG_RODATA it boots fine again.
> Could you try booting with -v to print the addresses where the dtb gets
> located?
> If Russell is right then increasing image_decomp_size in
> arch/arm/lib/bootm.c should help.
barebox@TI AM335x BeagleBone:/ boot -v
blspec: blspec_scan_directory: net loader/entries
Loading ARM Linux zImage '/mnt/tftp/alex-linux-beaglebone'
OS image not yet relocated
Passing control to ARM zImage handler
no OS load address, defaulting to 0x80e8c000
no initrd load address, defaulting to 0x8132f000
Loading devicetree from '/mnt/tftp/alex-oftree-beaglebone'
commandline: console=ttyO0,115200n8 ip=dhcp root=/dev/nfs rw nfsroot=.....
Starting kernel at 0x80e8c000, oftree at 0x8132f000...
Error: unrecognized/unsupported machine ID (r1 = 0x00000ee0).
----
The increasing of image_decomp_size from "PAGE_ALIGN(image_size * 4)" to
"PAGE_ALIGN(image_size * 8)" will fix this issue, the new locations are:
Loading ARM Linux zImage '/mnt/tftp/alex-linux-beaglebone'
OS image not yet relocated
Passing control to ARM zImage handler
no OS load address, defaulting to 0x81d18000
no initrd load address, defaulting to 0x821bb000
Loading devicetree from '/mnt/tftp/alex-oftree-beaglebone'
commandline: console=ttyO0,115200n8 ip=dhcp root=/dev/nfs rw nfsroot=...
Starting kernel at 0x81d18000, oftree at 0x821bb000...
- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
