Kernel executation from ROM
A message that is not in the archive (sent off-list or not yet received): [email protected]
Dear Sirs,
Thanks for your help,
I see . The biggest negative point of running kernel from ROM is that ROM speed is slow :(
Any how , thanks for your help,
Best Regards,
Jaswinder.
--
These are my opinions not 3Di.
----- Original Message -----
From: "Peter Waltenberg" <[email protected]>
To: "Jaswinder Singh" <[email protected]>
Sent: Sunday, February 18, 2001 6:49 PM
Subject: RE: Kernel executation from ROM
Quoted 2 lines
You can laod the kernel from ROM, but it'll need RAM to execute. If you
get to
Quoted 1 line
be very good with the linker and loader, you can probably make a large
part of
Quoted 1 line
the kernel ROM resident, but it will still need significant amounts of RAM
to
Quoted 2 lines
be usable.
It's probably easier not to bother and do what everyone else does and copy
from
Quoted 19 lines
ROM->RAMat startup.Peter
Quoted 13 lines · On 19-Feb-2001 Jaswinder Singh wrote:
Dear Kernel mailing list ,
what changes i have to made in kernel so that i can run kernel from ROM, means i keep my kernel in ROM and i execute my kernel from ROM .
Thanks ,
Happy Hacking,
Jaswinder.
--
These are my opinions not 3Di.
---------------------
----- Original Message -----
From: "Albert D. Cahalan" <[email protected]>
To: "Jaswinder Singh" <[email protected]>
Sent: Sunday, February 18, 2001 6:57 PM
Subject: Re: Kernel executation from ROM
Quoted 18 lines
Quoted 3 lines
what changes i have to made in kernel so that i can run kernel from ROM, means i keep my kernel in ROM and i execute my kernel from ROM .
1. write boot code to copy initialized variables into RAM
2. adjust the linker script to know about the above
3. adjust the linker script for other sections tooFor better performance, assuming ROM is slow and costly:
1. compress the "
__init" code and data; use it in RAM
2. profile your kernel; put the critical parts in RAMIf you want the details, take Red Hat's embedded systems development class. If you have a dozen people, get the class done at your location and have it modified to fit your needs. I just took the class; it was pretty good. It is "RHD248".
Quoted 2 lines · In article <01e701c09a2a$21e789a0$bba6b3d0@Toshiba> you wrote:
I see . The biggest negative point of running kernel from ROM is that ROM speed is slow :(
Well, normally you use the ROM only as a "boot device". You copy the Kernel into RAM and run it. Ram is not more expensive than ROM :)
What is your Reason for keeping the Kernel in ROM? Security? Do you have a special limited Device? In that case you might want to look at the embedded Linux Versions which run without MMU. Those might even have a decent ROM Performance (compared to RAM).
Greetings
Bernd
Quoted 6 lines · Jaswinder Singh
Dear Sirs,
Thanks for your help,
I see . The biggest negative point of running kernel from ROM is that ROM speed is slow :(
Also, the PCI specification forbids executing code from ROMs over the PCI bus. The system BIOS in a PC is not on the PCI bus, bus, but everything else is.
Quoted 11 lines · Jeremy Jackson
Quoted 6 lines · Jaswinder Singh
Dear Sirs,
Thanks for your help,
I see . The biggest negative point of running kernel from ROM is that ROM speed is slow :(
Also, the PCI specification forbids executing code from ROMs over the PCI bus. The system BIOS in a PC is not on the PCI bus, bus, but everything else is.
No it forbids executing boot roms that way, by a standard pc bios. The system BIOS in a PC is normally on the ISA bus which is reached across via the PCI bus with a PCI->ISA bridge.
The thing is slow it really doesn't matter, all you need to do is enable caching on that area of the physical address space. You can't do this on the alpha currently but only because the alpha sucks that way. You can on practically everything else.
As for ROM being slow on x86 you can enable the MTRR to speed things up. Usually though ROMs are at least as expensive as RAM, so it is pointless.
Eric
Quoted 3 lines · Eric W. Biederman
No it forbids executing boot roms that way, by a standard pc bios. The system BIOS in a PC is normally on the ISA bus which is reached across via the PCI bus with a
PCI->ISAbridge.
Son of a gun, I missed that... sure enough my PIIX4 docs beside me here show a #BIOSCS pin on the southbridge... Can anybody clarify what this restriction does and doesn't apply to ? The MindShare PCI Arch. book where I got that info from doesn't elaborate that much.
Quoted 6 lines
The thing is slow it really doesn't matter, all you need to do is enable caching on that area of the physical address space. You can't do this on the alpha currently but only because the alpha sucks that way. You can on practically everything else.
As for ROM being slow on x86 you can enable the MTRR to speed things
Don't MTRR's just do write combining?
Quoted 3 lines
up. Usually though ROMs are at least as expensive as RAM, so it is pointless.