From: Vidhiyadharan <vdharan2001@yahoo.co.uk>
To: blaz.antonic@havn.com
Cc: linux-8086@vger.kernel.org
Subject: Re: Ram , Flash requirements?
Date: Wed, 12 Jun 2002 06:43:16 +0100 (BST) [thread overview]
Message-ID: <20020612054316.578.qmail@web13508.mail.yahoo.com> (raw)
In-Reply-To: <3D06BA94.5DCD@havn.com>
Thanks to all,
We have our 512Kb flash memory mapped.We have a keypad and a LCD
display. We have also developed a PC like bios for our system.
We have 2 serial ports & 1 can be used for console.
Therefore from your discussion i come to know that it is possible to
port ELKS to this board.
Is there any documentation for ELKS kernel ?.
ThankYou
vdharan
--- Blaz Antonic <blaz.antonic@havn.com> wrote: > > lacking a BIOS
area. Don't get me wrong, ELKS doesn't need to
> have PC
> > compatible hardware to run, but it would take a lot of hacking to
> modify
> > it as it seems like it relies on BIOS calls for most of it's I/O
> > currently.
>
> No it doesn't; the only bit that _needs_ BIOS to work is BIOS HD/FH
> driver (d'oh) - if flash is mapped to 186's memory there's no need
> for
> such a driver, slightly modified ramdisk driver will do the trick.
> Other
> bits (serial, parallel, direct console) don't need BIOS to work,
> they
> just get port addresses from it (but these can be hardcoded anyway)
> ..
> and console driver will be replaced with serial console in embedded
> application.
>
> Blaz Antonic
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
next prev parent reply other threads:[~2002-06-12 5:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020611125006.57604.qmail@web13506.mail.yahoo.com>
2002-06-11 18:07 ` Ram , Flash requirements? Gregg C Levine
2002-06-11 18:15 ` Dan Olson
2002-06-12 1:28 ` Gregg C Levine
2002-06-12 20:08 ` Dan Olson
2002-06-13 5:57 ` Alan Cox
2002-06-12 3:05 ` Blaz Antonic
2002-06-11 19:45 ` Dan Olson
2002-06-12 5:43 ` Vidhiyadharan [this message]
2002-06-12 6:51 ` Alan Cox
2002-06-12 20:25 ` Dan Olson
2002-06-13 5:56 ` Alan Cox
2002-07-04 22:13 ` Bdale Garbee
2002-06-11 5:43 Vidhiyadharan
2002-06-11 9:32 ` Gregg C Levine
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=20020612054316.578.qmail@web13508.mail.yahoo.com \
--to=vdharan2001@yahoo.co.uk \
--cc=blaz.antonic@havn.com \
--cc=linux-8086@vger.kernel.org \
/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