These are the sources from Adam Agnew and Adam Sulmicki that let you boot
OpenBSD, Windows, etc.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
> These are the sources from Adam Agnew and Adam Sulmicki that let you boot
> OpenBSD, Windows, etc.
Is this the recommended way to boot a Linux kernel from CompactFlash or should
I continue trying to figure out why elfboot won't look at IDE with option
BOOT_IDE=1?
The Bochs BIOS is built aroun
> Is this the recommended way to boot a Linux kernel from CompactFlash or
> should I continue trying to figure out why elfboot won't look at IDE
> with option BOOT_IDE=1?
maybe someone else can answer this.
I'll just add that when ADLO is used an plain linux kernel without any
modifications can
What size does all this take up in flash?
LinuxBIOS + BOCHS BIOS + Video BIOS =?
Bari
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
> What size does all this take up in flash?
>
> LinuxBIOS + BOCHS BIOS + Video BIOS =?
BOCHS BIOS standard size is 64kb. If you gzip it it goes down to 20kb.
We are currently using binary only video bios. The video bios as it is
with SIS630 is 48kb. For paranoia sake we are using full 64kb.
gzipp
Adam Sulmicki wrote:
What size does all this take up in flash?
LinuxBIOS + BOCHS BIOS + Video BIOS =?
BOCHS BIOS standard size is 64kb. If you gzip it it goes down to 20kb.
We are currently using binary only video bios. The video bios as it is
with SIS630 is 48kb. For paranoia sake we are
On Mon, 2002-11-25 at 10:08, Ronald G. Minnich wrote:
> These are the sources from Adam Agnew and Adam Sulmicki that let you boot
> OpenBSD, Windows, etc.
>
Is there any HOWTO on this ??
Ollie
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.
> > These are the sources from Adam Agnew and Adam Sulmicki that let you boot
> > OpenBSD, Windows, etc.
> >
>
> Is there any HOWTO on this ??
Just read throughout the files provied with ADLO. the "INSTALL" file is a
fairly good start, README would be next. But you probably want to go over
all of
It fits well under the 256kB of flash. And yes, I should think its about
time they got worried. What's not to be worried about? Getting Bochs BIOS
to run should be pretty trivial on just about every board LinuxBIOS
supports.
Contributions are welcome. It's by no means a completed product. And we'd
Adam Sulmicki wrote:
LinuxBIOS + BOCHS BIOS + Video BIOS =?
Doesn't it seem like much of problem:
64+64+48 = 176KB
176 < 512KB
and you probably could gzip it for even more space saving.
(though I'm not sure of exact sizes of LinuxBIOS as bulk of my
time was spent on BOCHS bios part.)
Linu
> Linux Kernel 448KB + BOCHS 64 KB + Video BIOS 48 KB = 560KB ouch!
you don't need a linux kernel in your flash though then..
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
Greetings,
I've been looking at the issue of LinuxBIOS functions as well. The
baremetal toolkit is about 90% code drawn from LinuxBIOS
itself. Currently, it is standalone and does not address chipset specifics
itself.
One approach I've given some thought to is a simple function
table. Another is
Greetings,
I don't know how Adam feels about it, but if I were Phoenix, AMI,
et. al. I'd be worried now, and very interested in getting involved in
LinuxBIOS.
G'day,
sjames
On Sun, 24 Nov 2002, Bari Ari wrote:
> Adam Sulmicki wrote:
>
> >>What size does all this take up in flash?
> >>
> >>Li
One of the big issues is that for compatibility reasons we have to have
our bios at 0xF and video bios at 0xC.
However it occured to me that while we keep our bios in RAM, the LinuxBIOS
is still out there in the ROM. So perhaps BIOS function could switch
on/off some 16kb area in RAM to RO
Greetings,
I was thinking of locating the function table somewhere in ram. Perhaps it
and the code itself could go in the 64 K at 0x10 and A20 could be
turned on to access that small highmem area with the segment register set
at 0x. I hadn't considered that this would be Real mode (though
> I don't know how Adam feels about it, but if I were Phoenix, AMI,
> et. al. I'd be worried now, and very interested in getting involved in
> LinuxBIOS.
I agree. Especially with some of the talk about personalities and being able
to detect the chipset.
Regards,
Andrew
_
On Sun, 24 Nov 2002, Andrew Kohlsmith wrote:
> Is this the recommended way to boot a Linux kernel from CompactFlash or should
> I continue trying to figure out why elfboot won't look at IDE with option
> BOOT_IDE=1?
I would like to know that. I think it is useful.
ron
Andrew Kohlsmith <[EMAIL PROTECTED]> writes:
> > These are the sources from Adam Agnew and Adam Sulmicki that let you boot
> > OpenBSD, Windows, etc.
>
> Is this the recommended way to boot a Linux kernel from CompactFlash or should
> I continue trying to figure out why elfboot won't look at IDE
Adam Sulmicki <[EMAIL PROTECTED]> writes:
> > Is this the recommended way to boot a Linux kernel from CompactFlash or
> > should I continue trying to figure out why elfboot won't look at IDE
> > with option BOOT_IDE=1?
>
> maybe someone else can answer this.
>
> I'll just add that when ADLO is u
> What size does all this take up in flash?
>
> LinuxBIOS + BOCHS BIOS + Video BIOS =?
By the way. It all does not have to be in flash.
For example for the development, I was using LinuxBIOS and EtherBOOT in
flash, and I was grabbing the BOCHS BIOS over network from a differnet
computer. But you
steven james <[EMAIL PROTECTED]> writes:
> Greetings,
>
> I was thinking of locating the function table somewhere in ram. Perhaps it
> and the code itself could go in the 64 K at 0x10 and A20 could be
> turned on to access that small highmem area with the segment register set
> at 0x. I h
One thing we should keep in mind for the shadow ram thing:
Just about every chipset I have seen has shadow ram registers that can
correctly be set with the following info:
VendorID, DeviceID, Function, register, AndMask, OrMask.
This rapidly leads to a simple table something like this:
struct
"Ronald G. Minnich" <[EMAIL PROTECTED]> writes:
> One thing we should keep in mind for the shadow ram thing:
> Just about every chipset I have seen has shadow ram registers that can
> correctly be set with the following info:
>
> VendorID, DeviceID, Function, register, AndMask, OrMask.
>
> Thi
On 25 Nov 2002, Eric W. Biederman wrote:
> Except for the Athlons? Which control this in the CPU?
yes but ... that's a test for cpuid.
> For the most part we should just enable these area in LinuxBIOS.
For motherboards that will work if we do that. There are still weirdo ones
out there that
"Ronald G. Minnich" <[EMAIL PROTECTED]> writes:
> On 25 Nov 2002, Eric W. Biederman wrote:
>
> > Except for the Athlons? Which control this in the CPU?
>
> yes but ... that's a test for cpuid.
>
> > For the most part we should just enable these area in LinuxBIOS.
>
> For motherboards that w
"Ronald G. Minnich" <[EMAIL PROTECTED]> writes:
> One thing we should keep in mind for the shadow ram thing:
> Just about every chipset I have seen has shadow ram registers that can
> correctly be set with the following info:
>
> VendorID, DeviceID, Function, register, AndMask, OrMask.
>
> Thi
> > One thing we should keep in mind for the shadow ram thing:
> > Just about every chipset I have seen has shadow ram registers that can
> > correctly be set with the following info:
> >
> > VendorID, DeviceID, Function, register, AndMask, OrMask.
> >
> > ...
> > I haven't stumbled across a ch
On 26 Nov 2002, Christer Weinigel wrote:
> "Ronald G. Minnich" <[EMAIL PROTECTED]> writes:
>
> > One thing we should keep in mind for the shadow ram thing:
> > Just about every chipset I have seen has shadow ram registers that can
> > correctly be set with the following info:
> >
> > VendorID,
> well, looks like my beautiful theory just got killed by a brutal gang of
> facts. Now it's somebody else's turn to figure this out :-)
well it always could be intermediate solution. In this way we only have 4
data structures and no functions.
--
Adam Sulmicki
http://www.eax.com The Suprem
On Tue, 26 Nov 2002, Adam Sulmicki wrote:
> well it always could be intermediate solution. In this way we only have 4
> data structures and no functions.
sounds like we need a union, with a tag, and then the descriptors. In the
limit, the tag can be TAG_CODE, meaning you have to call the attache
On Tue, 26 Nov 2002, Ronald G. Minnich wrote:
> On Tue, 26 Nov 2002, Adam Sulmicki wrote:
>
> > well it always could be intermediate solution. In this way we only have 4
> > data structures and no functions.
>
> sounds like we need a union, with a tag, and then the descriptors. In the
> limit,
31 matches
Mail list logo
