On 11.10.2014 03:03, ron minnich wrote:
Android defaults sometimes surprise me.
When we've had this kind of issue in the past a disassembly diff of good vs bad has sometimes led to diagnosis. I think you have a rough idea what's broken so start there. Painful but necessary.
.car.data is linked at wrong address. Working: 4 .car.data 000000b4 ff7f0000 ff7f0000 00012b00 2**5 CONTENTS Broken: 4 .car.data 000000ac 00000000 00000000 00012b00 2**5 CONTENTS
Ron
What intrigues me is that I have been building x86 coreboot with this patch in place for a year. I wonder if we're missing a subsequent patch...
On 11.10.2014 03:20, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 11.10.2014 03:03, ron minnich wrote:
Android defaults sometimes surprise me.
When we've had this kind of issue in the past a disassembly diff of good vs bad has sometimes led to diagnosis. I think you have a rough idea what's broken so start there. Painful but necessary.
.car.data is linked at wrong address. Working: 4 .car.data 000000b4 ff7f0000 ff7f0000 00012b00 2**5 CONTENTS Broken: 4 .car.data 000000ac 00000000 00000000 00012b00 2**5 CONTENTS
http://review.coreboot.org/7042
Ron
Nice work :-)
see you in a few days!
ron
On Fri, Oct 10, 2014 at 6:50 PM, Vladimir 'φ-coder/phcoder' Serbinenko phcoder@gmail.com wrote:
On 11.10.2014 03:20, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 11.10.2014 03:03, ron minnich wrote:
Android defaults sometimes surprise me.
When we've had this kind of issue in the past a disassembly diff of good vs bad has sometimes led to diagnosis. I think you have a rough idea what's broken so start there. Painful but necessary.
.car.data is linked at wrong address. Working: 4 .car.data 000000b4 ff7f0000 ff7f0000 00012b00 2**5 CONTENTS Broken: 4 .car.data 000000ac 00000000 00000000 00012b00 2**5 CONTENTS
http://review.coreboot.org/7042
Ron