I put two new posting apps, a vm86 version and emu86 version out on:
bk://mesa3d.bkbits.net/rom
Get klibc from:
http://kernel.org/pub/linux/libs/klibc/
Install it somewhere and build it. You need to make a link to the
kernel source in the top level klibc directory. In this directory make
a link from the klibc-xxx directory to klibc.
Both projects will then build.
v86bios uses vm86 to run the rom
post uses emu86
Use an environment variable to pick the card to be acted on:
export DEVPATH=/bus/pci/devices/0000:01:00.0
vm86 is 20K non-debug
emu86 is 40K non-debug
Currently they don't use Ben's VGA arbiter which isn't ready yet. When
finished these app will automatically be triggered on driver load as
part of the hotplug process.
The source to vm86 is from the linux BIOS project where is has been
worked on to make it substantially smaller. I like to keep everyone on
the same source code base if possible.
Once we get these cleaned up and working I'm hoping to get them added
to the klibc project. Once in klibc, klibc is schedule to go into the
kernel sooner or later.
They are both partially working but fail part way through the posting
process. I've been playing with them a couple of days and I can't
figure out why they are failing. They are both failing for different
reasons. Can anyone help?
--
Jon Smirl
jonsmirl(a)gmail.com
I used mkelfImage to combined Linux Kernel 2.4.20 and initrd into elf image for netboot. then I try to use "mount -o loop my_elfImage" to mount this image as a loop device. I get a error message like this:
#mount: you must specify the filesystem type
I have specified the my_elfImage in /etc/fstab as this: (I add a line in fstab because mount ask me to do that)
/root/loop/my_elfImage /root/loop/tl auto noauto,owner,kudzu 0 0
I changed the file type from auto to ext3 and etc. but nothing work for me.
Could anybody kindly help me on this?
Thanks
tony
Hello,
this patch adds following options, for the use of OEM ROM section,
eg: onboard PCI device's BIOS in boot ROM or MAC address saved in boot ROM
ROM_TOTAL_SIZE: the total size of boot ROM
ROM_OEM_SIZE: the size of boot ROM used by OEM_ROM section
ROM_SIZE: the size of boot ROM used by LinuxBIOS
ROM_OEM_START: OEM_ROM start address
OEM ROM exists in the low address end of boot ROM, so
default ROM_OEM_SIZE = 0
default ROM_SIZE = ROM_TOTAL_SIZE - ROM_OEM_SIZE
default ROM_OEM_START = 0xffffffff - ROM_TOTAL_SIZE + 1
OEM devices should know the offset of their data in OEM ROM,
so they can visit their data at address (ROM_OEM_START + oem_my_data_offset)
to use OEM ROM, one should define ROM_TOTAL_SIZE and ROM_OEM_SIZE
in mainboard's Options.lb file.
this patch won't break mainboards which defines ROM_SIZE and don't mentions
ROM_TOTAL_SIZE and ROM_OEM_SIZE.
--- freebios2-20050305-0000-orig/src/config/Options.lb 2005-01-15
05:54:16.000000000 +0800
+++ freebios2-20050305-0000/src/config/Options.lb 2005-03-30
20:49:16.000000000 +0800
@@ -190,11 +190,29 @@
export used
comment "Default fallback image size"
end
-define ROM_SIZE
+define ROM_TOTAL_SIZE
default none
format "0x%x"
export used
- comment "Size of your ROM"
+ comment "Size of your boot ROM"
+end
+define ROM_OEM_SIZE
+ default 0
+ format "0x%x"
+ export used
+ comment "Size of your ROM used by OEM vendors"
+end
+define ROM_OEM_START
+ default {0xffffffff - ROM_TOTAL_SIZE + 1}
+ format "0x%x"
+ export used
+ comment "OEM ROM start location"
+end
+define ROM_SIZE
+ default {ROM_TOTAL_SIZE - ROM_OEM_SIZE}
+ format "0x%x"
+ export used
+ comment "Size of your ROM used by LinuxBIOS"
end
define ROM_IMAGE_SIZE
default 65535
--
Liu Tao
Hello Linux BIOS developers.
As far as I understand, current Linux BIOS does not boot from USB memory
stick if it is USB 2.0, Right?. But, I also understand that EHCI (= USB 2.0)
can also work as UHCI/OHCI( = USB1.1).
Then, if I use a M/B which has EHCI and put USB 2.0 stick to it,
and put Linux kernel supports EHCI driver there.
And if I boot it with Etherboot/FILO with USB 1.1 support in this case,
can it boot as USB 1.1? and can I switch USB mode to 2.0 after booting?
What I want to do is like this.
1. Boot linux kernel by Etherboot/FILO/USB1.1 from USB stick.
2. Reading Linux kernel itself is slow.
But after that, it works with 2.0 performance?.
--- Okajima, Jun. Tokyo, Japan.
The Athlon 64 939 support dual channel.
but in the test in s2865 with d0 Athlon64 939 in LinuxBIOS, it only work
with one DIMM in socket 1.
weird....
the same code with Opteron d0 ....
YH
> -----Original Message-----
> From: YhLu
> Sent: Wednesday, March 30, 2005 3:09 PM
> To: ebiederman(a)lnxi.com; Kevin O'Connor
> Cc: linuxbios(a)openbios.org
> Subject: RE: [LinuxBIOS] Re: Error in compiling STPC Consumer
>
> Eric,
>
> the code in raminit.c is_opteron will treat my athlon 64
> (939) as Opteron too.
>
> YH
>
> static int is_opteron(const struct mem_controller *ctrl) {
> /* Test to see if I am an Opteron.
> * FIXME Testing dual channel capability is correct for now
> * but a beter test is probably required.
> */
> #warning "FIXME implement a better test for opterons"
> uint32_t nbcap;
> nbcap = pci_read_config32(ctrl->f3, NORTHBRIDGE_CAP);
> return !!(nbcap & NBCAP_128Bit); }
>
>
> _______________________________________________
> LinuxBIOS mailing list
> LinuxBIOS(a)openbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios
>
Hi all ,
I want any simulator that i can use as virtual machine to test my romimage without burning it in to actual chip.
I there is any such software or alternative .
Thank you
Ramesh Chander
Yahoo! India Matrimony: Find your life partneronline.