public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vikas Kumar" <walburn@gmail.com>
To: Dave Mills <dave@webshed.org>
Cc: linux-8086@vger.kernel.org
Subject: Re: Minimum RAM for ELKS?
Date: Mon, 15 May 2006 12:34:15 -0400	[thread overview]
Message-ID: <792c60620605150934l78bd0e66m2cec38e64593d888@mail.gmail.com> (raw)
In-Reply-To: <4468A9C2.40703@webshed.org>

Hey Dave
Use Bochs emulator. Set the RAM to how much ever your target machine
has, and use an elks image and see if it works.  iF it works on this
setting, it should work on your target hardware as well.

Vikas


On 5/15/06, Dave Mills <dave@webshed.org> wrote:
> Hi,
>
> I'm planning to fiddle with ELKS on an 8086 system at some time in the
> near future. The system has very minimal RAM (~200k). Does anyone have
> any idea (or even better, experience) about ELKS in such a low RAM
> configuration?  I realise that I'll probably not get much more than the
> kernel booting, as other software running will require more RAM than I have.
>
> Getting to the stage where ELKS boots and my application prints "I'm
> alive!" over the serial port is my first target.
>
> cheers,
> Dave
> -
> 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
>


-- 
Capitalization is the difference between "I had to help my uncle Jack
off a horse.." and "I had to help my uncle jack off a horse.."

  reply	other threads:[~2006-05-15 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 16:18 Minimum RAM for ELKS? Dave Mills
2006-05-15 16:34 ` Vikas Kumar [this message]
2006-05-15 19:52   ` Tom McCabe
2006-05-17 10:05     ` Dave Mills

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=792c60620605150934l78bd0e66m2cec38e64593d888@mail.gmail.com \
    --to=walburn@gmail.com \
    --cc=dave@webshed.org \
    --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