From: "Georg Potthast" <nospam@georgpotthast.de>
To: LM <lmemsm@gmail.com>, ELKS <Linux-8086@vger.kernel.org>
Subject: Re: A tiny patch for env.sh & busyelks.
Date: Thu, 6 Feb 2020 17:14:07 +0100 [thread overview]
Message-ID: <82354F1839304B119CE128F466CF7FE5@PotthastHP> (raw)
In-Reply-To: <CAFipMOFyrQiF+GGP+dC0C-bzrQSca+8UCkkU5+Z1-xUKEZ4apA@mail.gmail.com>
Hi Laura,
I think ELKS would need additional memory support beyond 1 MB to properly
support busybox and further applications. ELKS could add support for the
80386 processor for that.
Georg
-----Ursprüngliche Nachricht-----
From: LM
Sent: Wednesday, February 5, 2020 9:11 PM
To: ELKS
Subject: Re: A tiny patch for env.sh & busyelks.
On Tue, Feb 4, 2020 at 2:36 PM Jody Bruchon <jody@jodybruchon.com> wrote:
>Things should be much better today, but I didn't feel like
working on it any longer. It would work if someone with a little C
coding skill massaged it a bit. The biggest challenge is keeping the
binaries small enough.
It's a really interesting project. I'm working on something similar
for some other platforms. I don't think I could write anything
efficient enough to suit this project. However, if anyone does pick
up development, I would love to compare notes, design ideas and
algorithms for doing this sort of thing.
prev parent reply other threads:[~2020-02-06 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABdhv6+xsYsMwyT76RhHqgidHBZS8-cOozypNpR5pzbEvyofAw@mail.gmail.com>
2020-02-04 18:33 ` A tiny patch for env.sh & busyelks Marc-F. Lucca-Daniau
2020-02-04 19:30 ` Jody Bruchon
[not found] ` <CAFipMOFfE2fYSiwH-ZhJf7FN-Bd2=DqgNA-tyZWea9HuPhsgPg@mail.gmail.com>
[not found] ` <CAFipMOFKvpDfyX9Sd1uw2gnhv3vAoACFue_iTTgFcksb-GLyig@mail.gmail.com>
2020-02-05 20:11 ` LM
2020-02-06 16:14 ` Georg Potthast [this message]
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=82354F1839304B119CE128F466CF7FE5@PotthastHP \
--to=nospam@georgpotthast.de \
--cc=Linux-8086@vger.kernel.org \
--cc=lmemsm@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).