r1 is 0x53555151, which is looks more likely to be garbage than to be a real, but misaligned, address. I guess we'll need to figure out where that value is coming from...''
It's stuck at the moment.
Freescale: The LT is currently having some difficulties building the kernel completely with Thumb2 instructions. The major reason is the suspend/resume code which is very SoC specific and low level, uses ARM instructions which they need to convert into thumb2 compatible firstly. It's currently on their wish list.
ARM: The Virtual Express builds have this set and it seems to work.
Some notes from the LT's on Thumb2 kernels (CONFIG_ THUMB2_ KERNEL= y)
TI: The LT tested it when Dave Martin sent out the call, it blows chunks for us in power management patches on tracking -->
''From the crash dump, the faulting code seems to be:
f503 7182 add.w r1, r3, #260 ; 0x104
** e851 0f00 ldrex r0, [r1] **
f100 0001 add.w r0, r0, #1
r1 is 0x53555151, which is looks more likely to be garbage than to be a real, but misaligned, address. I guess we'll need to figure out where that value is coming from...''
It's stuck at the moment.
Freescale: The LT is currently having some difficulties building the kernel completely with Thumb2 instructions. The major reason is the suspend/resume code which is very SoC specific and low level, uses ARM instructions which they need to convert into thumb2 compatible firstly. It's currently on their wish list.
ARM: The Virtual Express builds have this set and it seems to work.
STE: Need to investigate. I expect problems.
Samsung: Unknown at this time.