Author: ward
Date: 2007-09-20 17:01:14 +0200 (Thu, 20 Sep 2007)
New Revision: 2792
Modified:
trunk/LinuxBIOSv2/src/mainboard/tyan/s2891/Config.lb
Log:
The s2891 ships with a 1MB rom chip. The targets/tyan/s2891/Config.lb file assumes a 1MB rom chip.
Hence the default position for the VGA bios should also assume a 1MB rom chip, instead of a 512KB chip.
Signed-off-by: Ward Vandewege <ward(a)gnu.org>
Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de>
Modified: trunk/LinuxBIOSv2/src/…
[View More]mainboard/tyan/s2891/Config.lb
===================================================================
--- trunk/LinuxBIOSv2/src/mainboard/tyan/s2891/Config.lb 2007-09-20 00:00:49 UTC (rev 2791)
+++ trunk/LinuxBIOSv2/src/mainboard/tyan/s2891/Config.lb 2007-09-20 15:01:14 UTC (rev 2792)
@@ -314,8 +314,8 @@
# chip drivers/ati/ragexl
chip drivers/pci/onboard
device pci 7.0 on end
- register "rom_address" = "0xfff80000" #for 512K
- # register "rom_address" = "0xfff00000" #for 1M
+ #register "rom_address" = "0xfff80000" #for 512K
+ register "rom_address" = "0xfff00000" #for 1M
end
end
device pci a.0 off end # NIC
[View Less]
Hello!
I hope I'm not too far off the mark, and this is semi-offtopic, but what
I'm wondering about is udev and compact flash.
What I'm doing is installing Debian with FAI[1] and afterwards would be
flashing the bios with LinuxBios. The FAI installation works on a regular
hard drive just perfectly.
The problem: I'm not seeing the cflash /dev/hde. It's found a-ok by
lspcmcia and pccardctl, as well as cating /sys (which is apparently
pretty much what udevinfo does as well)
I searched the …
[View More]archives and they seem to point me towards etherboot
like http://www.mail-archive.com/linuxbios@clustermatic.org/msg03583.html
but especially stages 4-6 in that list seem to be something I'm not
planing on doing at the moment.
My idea is to do whatever it takes to get FAI to install on the cflash
and use that to make an initrd payload to the make a root of the card.
What do I need to get this thing going?
Thanks!
[1] http://www.informatik.uni-koeln.de/fai/
PS.
Unfortunately a lot of the other mail traffic is about using an adapter;
imo that sort of defeats the purpose of having an integrated bridge...
--
mjt
[View Less]
I'd appreciate your help with this:
I haven't programmed with bcc or as86 before, and I'm having trouble using
the Bochs BIOS print routines.
I don't know what I've done, but adding printfs regularly breaks the code.
Adding another (or two) will sometimes fix it again.
Does anyone have an idea of what to look for?
I have the FILO driver working as far as identifying my drives and
populating the BIOS structures. There is only a little bit left to do, and
if it didn't hang so often it would …
[View More]help me progress a bit faster.
I would have posted the output or the code, but just about any printf kills
it, and I've looked through the assembly and various c files, and verified
that they are the only things getting added.
I'm thinking the most likely candidate is extra arguments being pushed onto
the stack, or extra ones being popped off, or something.
Thanks in advance for your suggestions,
Myles
[View Less]