public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: MFLD <mfld.fr@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Cleaning up elkscmd and adding help text - Questions
Date: Fri, 27 Mar 2015 19:52:31 +0100	[thread overview]
Message-ID: <5515A6EF.4060002@gmail.com> (raw)
In-Reply-To: <5DA02C83-25D8-4C8B-859E-2814368CC566@jodybruchon.com>

I am not suggesting to build Linux on 8086, I do know it won't fit 
(protected mode...) and this is why I came to ELKS!

This is also why I cannot reuse coreboot for my project and I started to 
write a kind of boot86 / mon86.

I only suggested to try to build Busybox with dev86, and using the libc 
from dev86 for the glue between Busybox code and ELKS.

Was it tried before ?

MFLD


Le 27/03/2015 19:26, Jody Bruchon a écrit :
> On March 27, 2015 2:19:54 PM EDT, MFLD <mfld.fr@gmail.com> wrote:
>> I really wonder why you spend time on the ELKS userland... if I have a
>> look to the sizes of uclibc and busybox on a 32 bits embedded system,
> ...snip...
>> If I take the example of my 80188 system
> BusyBox and uClibc don't work on 16-bit segmented architectures with 64K code and data size limits. Linux doesn't either. If you want to run a Linux-like system on an 80x86 where x < 3, you can't use any of the software you just mentioned at all.
>

--
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

  reply	other threads:[~2015-03-27 18:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  8:19 Cleaning up elkscmd and adding help text - Questions Nils Stec
2015-03-27 13:19 ` Jody Bruchon
2015-03-27 14:10   ` Alan Cox
2015-03-27 16:17     ` Jody Bruchon
2015-03-27 18:19       ` MFLD
2015-03-27 18:26         ` Jody Bruchon
2015-03-27 18:52           ` MFLD [this message]
2015-03-27 22:19             ` Alan Cox
2015-03-28 15:35               ` LM
2015-03-27 18:41         ` Alan Cox
2015-03-27 17:59   ` Nils Stec
2015-03-27 18:31     ` Alan Cox
2015-03-27 13:54 ` Alan Cox

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=5515A6EF.4060002@gmail.com \
    --to=mfld.fr@gmail.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