From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: <peterw@dascom.com.au>, "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: <linux-kernel@vger.kernel.org>,
"Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Kernel executation from ROM
Date: Sun, 18 Feb 2001 20:12:10 -0800 [thread overview]
Message-ID: <01e701c09a2a$21e789a0$bba6b3d0@Toshiba> (raw)
In-Reply-To: <XFMail.20010219124909.peterw@dascom.com.au>
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" <peterw@dascom.com.au>
To: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Sent: Sunday, February 18, 2001 6:49 PM
Subject: RE: Kernel executation from ROM
>
> You can laod the kernel from ROM, but it'll need RAM to execute. If you
get to
> be very good with the linker and loader, you can probably make a large
part of
> the kernel ROM resident, but it will still need significant amounts of RAM
to
> be usable.
> It's probably easier not to bother and do what everyone else does and copy
from
> ROM->RAM at startup.
>
> Peter
>
> 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" <acahalan@cs.uml.edu>
To: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Sent: Sunday, February 18, 2001 6:57 PM
Subject: Re: Kernel executation from ROM
> > 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 too
>
> For 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 RAM
>
> If 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".
>
next parent reply other threads:[~2001-02-19 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <XFMail.20010219124909.peterw@dascom.com.au>
2001-02-19 4:12 ` Jaswinder Singh [this message]
2001-02-19 9:28 ` Kernel executation from ROM Bernd Eckenfels
2001-02-19 16:48 ` Jeremy Jackson
2001-02-19 19:50 ` Eric W. Biederman
2001-02-19 22:26 ` Jeremy Jackson
[not found] <XFMail.20010220082732.peterw@dascom.com.au>
2001-02-20 5:04 ` Eric W. Biederman
2001-02-19 2:38 Jaswinder Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01e701c09a2a$21e789a0$bba6b3d0@Toshiba' \
--to=jaswinder.singh@3disystems.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=peterw@dascom.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox