So next week, we can get the updated romcc?
-----邮件原件-----
发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com]
发送时间: 2004年6月25日 17:41
收件人: YhLu
抄送: LinuxBIOS
主题: Re: [COMMIT] romcc 0.63 and some fixes...
YhLu <YhLu(a)tyan.com> writes:
> Eric,
>
> The
> printo_debug("this mainboard is only designed for 2 cpus\r\n");
>
> causes the segment dump.
A update on this...
I took some time and tracked the problem down. So far
I have exposed 2 problems in romcc with your code.
The first that was causing the core dump I have fixed.
The second is a little more insidious. Basically
when call/return instructions are introduced the control
flow graph is no longer a graph. Because the structure
changes depending on which path you take through the code.
What happens currently is I treat it like a graph and get
a conservative estimate on the control flow structure. So no
incorrect transformations happen to the code. However there are a
number of cases and your code was one where code that is correct
does not appear to be. Because it appears that there are additional
paths to a basic block, when there are not.
The result is some legitimate cases will not compile. And likely
that some optimization opportunities are lost. I suspect the lost
optimization opportunities are responsible for the code size growth.
Without calls and returns the dominance relationship between
instructions is transitive. Instruction X dominates instruction Y if
you must execute X before Y. With call/return pairs the dominance
relationship is no longer quite transitive which is going to take
some delicate manipulation to let romcc understand this without
breaking it.
I am going to spend a little more time looking at this and when I am
done I am going to commit however many fixes/enhancements that I have.
Eric
Eric,
The
printo_debug("this mainboard is only designed for 2 cpus\r\n");
causes the segment dump.
Another problem. After only change print_debug in raminit.c, the final image
size get bigger from 68663 to 70203.
Regards
YH
-----邮件原件-----
发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com]
发送时间: 2004年6月3日 1:31
收件人: YhLu
抄送: LinuxBIOS
主题: Re: 答复: 答复: 答复: [COMMIT] romcc 0.63 and some fixes...
YhLu <YhLu(a)tyan.com> writes:
> Eric,
> I add in console.c
> static void printo_debug(const char *str) __attribute__((noinline))
> {
> print_debug(str);
> }
>
> About only chang print_debug in auto.c
>
> It said
> ./romcc -O2 -mcpu=k8 -o auto.inc --label-prefix=auto ./auto.E
> make[1]: *** [auto.inc] Segmentation fault
>
> ./romcc -O -mcpu=k8 -o auto.inc --label-prefix=auto ./auto.E
> make[1]: *** [auto.inc] Segmentation fault
Cool, my first bug report. I knew I had touched to much code
for the new release to run without a hitch.
Could you look at the core dump with gdb and give me a back trace?
That should help even if I can't reproduce the problem on this end.
Eric
The VIA EPIA MII can be bought with an LVDS port on it and I was
wondering the compatibility of this. Obviously its not supported under
LinuxBIOS, but would it work under Linux? A guy told me that the LCD
panel had to be supported by VIA's BIOS for it to work. Should Linux be
able to setup something like this since LinuxBIOS leaves most of that
stuff to Linux or does it have to be done by the BIOS (ie if Linux
doesn't support LVDS)?
Thanks,
Michael Robinson
mrobinson(a)fuzzymuzzle.com
www.fuzzymuzzle.com
---The trend seems to be NOT to use DiskOnChip but rather a CF <> IDE
adapter. Using FILO you can boot from the CF.---
So I'd flash FILO to the BIOS, then it would load the LinuxBIOS kernel
image, and then the kernel image would do whatever you want LinuxBIOS to
do, right? Or am I wrong... It says FILO loads a "boot image", whats the
definition of a "boot image", is it just the kernel?
Thanks,
Michael Robinson
mrobinson(a)fuzzymuzzle.com
www.fuzzymuzzle.com
Larry Matter wrote:
>>what
>>does the DiskOnChip provide to the LinuxBIOs project that the standard
>>flash chip can't?
>>
>>
>
>More than 2 megabits of storage.
>
>
>
>>My second is that I'm going to be using the VIA EPIA
>>MII motherboard which has a PLCC BIOS, as far as I can tell PLCC
>>DiskOnChips aren't very readily available. Should I use a DIP to PLCC
>>adapter; how did the other people who used this board do it?
>>
>>
>
>The trend seems to be NOT to use DiskOnChip but rather a CF <> IDE
>adapter. Using FILO you can boot from the CF.
>
>
>
>
>>My final
>>question is how do I pick the size of the DiskOnChip.
>>
>>
>
>So if you're going to go for the CF <> IDE, then it just needs to be as
>big as your root partition (or even just an initrd). There are many
>other alternatives depending on network, disk, etc.
>
>And if you've been following this list for a bit you'll know that you
>can't (yet) boot off of the CF adapter on the EPIA MII.
>
>One last word of advice, get a bios savior.
>
>Larry
>
>
>
>
>
Hey guys,
Please bear with me, I have some questions that are probably pretty
basic but I can't find the answers anywhere. My first question is what
does the DiskOnChip provide to the LinuxBIOs project that the standard
flash chip can't? My second is that I'm going to be using the VIA EPIA
MII motherboard which has a PLCC BIOS, as far as I can tell PLCC
DiskOnChips aren't very readily available. Should I use a DIP to PLCC
adapter; how did the other people who used this board do it? My final
question is how do I pick the size of the DiskOnChip. What is
LinuxBIOS's typical size requirement; do motherboards have a maximum
BIOS size limitation? If BIOSs do have a maximum size limitation how do
I figure it out, VIA says says the BIOS for my board is 2/4Mbit flash
memory. Sorry if these seem very basic.
Thanks,
Michael Robinson
mrobinson(a)fuzzymuzzle.com
www.fuzzymuzzle.com
Hello,
It seems that the resource allocation for option rom
is not implemented in LinuxBIOS, is it ? Is there one
have any idea how to add this ?
Ollie
I'm looking for a good/adequate tool for LinuxBIOS software
integration/development for dual Opteron mainboards.
The American Arium has recently added AMD64 support to their ECM-50
emulator. I've heard that the ECM-50 is $11K plus $4K for AMD64
module and $1.5K for support for a total of $16.5K. I've looked for
other AMD64 emulators, but didn't find any. Are there cheaper AMD64
emulators?
Something less than an in-circuit emulator may suffice. Maybe a bus
analyzer that simply filters and records bus signals on the mainboard.
The bus analyzed could be the processor bus, PCI bus, etc.
I'm looking for at least a POST card. Maybe a POST card with extra
features.
I suppose even a processor adapter that allows processor pins to be
probed with a logic analyzer might do as well.
What hardware tools (emulators, bus analyzers, POST card, etc.) would
you recommend for LinuxBIOS integration/development for dual Opteron
mainboards?
------
Thank you Ron, YH and David for your comments concerning Nvidia CK8-04
support in LinuxBIOS! It was/is most appreciated!
Sincerely,
Ken Fuchs <kfuchs(a)winternet.com>
Hello all,
I'm trying to boot from the CF reader on the VIA Epia platform. After
reading forums and mailinglist this could be possible by the FastBoot
Utility.
http://downloads.viaarena.com/WinCE/Apr04/fastboot%20v2.01.zip
But I was a bit surpriced what I found in there...
grep linux `find` and look at the 'loader*.obj'-files.
Can somebody confirm this is _not_ distributed GPL code as a binary?
Greetings,
Stefan de Konink
