On 26/04/2010 6:34 AM, Myles Watson wrote:
The problem with Truxton booting in trunk seems to have appeared in the
migration to the new Makefile system.
If I drop a CONFIG_SSE=y into the .config file using a trunk build I can
boot!
However, I don't really see how this flag gets set. Doing a '
On Mon, Apr 26, 2010 at 7:43 AM, Stefan Reinauer wrote:
> On 4/26/10 3:34 PM, Myles Watson wrote:
>>> The problem with Truxton booting in trunk seems to have appeared in the
>>> migration to the new Makefile system.
>>>
>>> If I drop a CONFIG_SSE=y into the .config file using a trunk build I can
>
Eric,
do you have a hint what could cause romcc to produce incorrect code
without -fno-simplify-phi ?
Stefan
On 4/26/10 4:23 PM, Myles Watson wrote:
> On Mon, Apr 26, 2010 at 7:43 AM, Stefan Reinauer
> wrote:
>
>> On 4/26/10 3:34 PM, Myles Watson wrote:
>>
The problem with Truxton
On 4/26/10 3:34 PM, Myles Watson wrote:
>> The problem with Truxton booting in trunk seems to have appeared in the
>> migration to the new Makefile system.
>>
>> If I drop a CONFIG_SSE=y into the .config file using a trunk build I can
>> boot!
>>
>> However, I don't really see how this flag gets se
On 4/26/10 3:34 PM, Myles Watson wrote:
>> The problem with Truxton booting in trunk seems to have appeared in the
>> migration to the new Makefile system.
>>
>> If I drop a CONFIG_SSE=y into the .config file using a trunk build I can
>> boot!
>>
>> However, I don't really see how this flag gets se
> The problem with Truxton booting in trunk seems to have appeared in the
> migration to the new Makefile system.
>
> If I drop a CONFIG_SSE=y into the .config file using a trunk build I can
> boot!
>
> However, I don't really see how this flag gets set. Doing a 'grep -RH
> CONFIG_SSE' points to t
Am 26.04.2010 08:24, schrieb Dustin Harrison:
> However, I don't really see how this flag gets set. Doing a 'grep -RH
> CONFIG_SSE' points to the two makefile includes that add the enable_sse
> code, but no references to setting the flag.
Such flags are set in Kconfig, and there the CONFIG_ prefix
On 22/04/2010 11:16 AM, Dustin Harrison wrote:
When I get done with my RAM timing I'll try an svn bisect to narrow it
down.
The problem with Truxton booting in trunk seems to have appeared in the
migration to the new Makefile system.
If I drop a CONFIG_SSE=y into the .config file using a t
On 4/24/10 4:52 AM, Dustin Harrison wrote:
> Thanks for the idea Stefan.
>
> I have yet to get SerialICE up, but I did manage to get the Truxton
> BIOS into QEMU. Interesting that QEMU exceptions at the same (at least
> relative to C code) spot as my board hangs. As a comparison (since so
> much of
Thanks for the idea Stefan.
I have yet to get SerialICE up, but I did manage to get the Truxton BIOS
into QEMU. Interesting that QEMU exceptions at the same (at least
relative to C code) spot as my board hangs. As a comparison (since so
much of the i3100 code is shared) I was able to get the
Try tracing the original BIOS and coreboot with SerialICE and compare
the differences ... It's a bunch of work but not as ugly as debugging
ROMCC assembler output... :-) http://www.serialice.com/
Stefan
On 22.04.2010, at 20:16, Dustin Harrison
wrote:
I did a diff of romstage.inc, using
I did a diff of romstage.inc, using the same codebase (rev 5351) the
only difference between romcc 4051 and 5351 was the timestamp. This is
consistent with my finding that compiling trunk with an older romcc
didn't help the situation.
When I get done with my RAM timing I'll try an svn bisect
Dustin Harrison wrote:
> if anyone has some ideas I'll give them a shot in between hacking
> the RAM.
It would be interesting to also look at output from a recent version
of romcc compiling the old code, and an old romcc compiling the new
code. That could hint to either a romcc bug or something go
On Thu, Apr 15, 2010 at 2:04 PM, Dustin Harrison
Question: I thought I read somewhere the ROMCC is no longer used?
Is that
true for the entire project? Because I see that ROMCC is still used
for
romstage.c
I don't know the status of romcc, but it wouldn't be a shock to
discover that a bug
On 15/04/2010 2:18 PM, Ed Swierk wrote:
On Thu, Apr 15, 2010 at 2:04 PM, Dustin Harrison
wrote:
Yes -- I did the following:
# rm .xcompile
# cd util/crossgcc
# ./buildgcc
# cd ../../
# make clean; make
I also printed out the $(CC) variable in the Makefile to confirm:
CC = CCACHE_COMPILERC
On Thu, Apr 15, 2010 at 9:53 AM, Dustin Harrison
wrote:
> I've tried my BIOS build on Truxton to no avail. I get stuck at the same
> spot.
>
> Does someone have a reference to an archive of a working Truxton build
> directory? At least I can start to compare differences in the
> assembly/.config
On 14/04/2010 1:14 PM, Dustin Harrison wrote:
I am also in the process of trying my BIOS in the truxton platform,
but it will take me a while to get things up and going. In the
meantime I'm out of ideas on how to narrow this down any further.
I've tried my BIOS build on Truxton to no avail
On 13/04/2010 11:56 PM, Stefan Reinauer wrote:
On 4/14/10 4:18 AM, Dustin Harrison wrote:
I've put several print_info statements in romstage.c and narrowed it
down to the following line in i3100_early_lpc.c:
pci_write_config32(dev, 0x44, pci_read_config32(dev, 0x44) | (1 << 7));
Further debu
On 4/14/10 4:18 AM, Dustin Harrison wrote:
> I've put several print_info statements in romstage.c and narrowed it
> down to the following line in i3100_early_lpc.c:
>
> pci_write_config32(dev, 0x44, pci_read_config32(dev, 0x44) | (1 << 7));
>
> Further debug shows that in general I can not read a
19 matches
Mail list logo
