From: Vipin Malik <vipin.malik@daniel.com>
To: David Woodhouse <dwmw2@redhat.com>
Cc: Vipin Malik <vipin@embeddedlinuxworks.com>,
olea@hispafuentes.com, linux-mtd@lists.infradead.org,
juan@hispafuentes.com
Subject: Re: Ask for some guidance...
Date: Wed, 25 Jul 2001 15:53:32 -0500 [thread overview]
Message-ID: <3B5F31CC.6705F4B0@daniel.com> (raw)
In-Reply-To: Pine.LNX.4.33.0107252008450.4023-100000@passion.cambridge.redhat.com
>
> > What BIOS is it using? I know that General Software's Embedded BIOS
> > supports that functionality.
>
> Do you know the format used?
Nope-sorry! Though GSW may be willing to share that info (if it is that).
>
> For booting, compatibility with the existing BIOS extension is useful.
Actually, for a x86 solution, most of these BIOS int 13 extensions can detect and
load a "floppy boot sector" format from resident flash disk (I think so, unless
I've lost my mind- which is quite a possibility :)
One can then use rolo (see web site www.embeddedlinuxworks.com under "ROLO: A
developers guide") to load a bzImage kernel into ram and boot it. The kernel can
then just detect the flash as MTD and mount JFFS2 on it.
You really don't even need the BIOS if you don't need thinks like video etc. in
your system- but having a BIOS makes life a bit easy- you don't have to figure out
chipset/peripheral initializations etc.
Vipin
next prev parent reply other threads:[~2001-07-25 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 18:32 Ask for some guidance olea
2001-07-25 3:12 ` Vipin Malik
2001-07-25 19:15 ` David Woodhouse
2001-07-25 20:53 ` Vipin Malik [this message]
2001-07-25 19:06 ` David Woodhouse
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=3B5F31CC.6705F4B0@daniel.com \
--to=vipin.malik@daniel.com \
--cc=dwmw2@redhat.com \
--cc=juan@hispafuentes.com \
--cc=linux-mtd@lists.infradead.org \
--cc=olea@hispafuentes.com \
--cc=vipin@embeddedlinuxworks.com \
/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