On Thu, Oct 16, 2008 at 10:10 PM, Corey Osgood corey.osgood@gmail.comwrote:
On Thu, Oct 16, 2008 at 9:28 PM, Eric W. Biederman ebiederm@xmission.comwrote:
Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net writes:
On 17.10.2008 02:50, Eric W. Biederman wrote:
Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net writes:
I added a special case for ROMCC in the 0x...ULL constants in
vt8237r.h.
Please see r3664. The remaining segfault is being investigated by Eric.
It is reproducible, and it happens as the intermediate expression is
being
translated into intermediate code so it should be to weird to track.
I'm
going to guess 4-5 hours to sort through it. I will aim to look at it
this
weekend.
Wow, that was unexpected. Thanks for investing your time!
Yes. If the bug was down in the optimizer it would take to long to track.
Eric
The break is caused by vt8237_early_spi_init(), most likely by spireg. Patch to disable that function in ROMCC is attached, I know that via epia-cn, pc2500, and jetway j7f2/4 don't use SPI, but I can't remember what the other C7/CN700 board is right this moment to check.
Bcom WinNet P680, which doesn't use SPI either, so we should be all good to disable that function as far as current boards go.
-Corey