From: u-vpoa@aetey.se
To: linux-8086@vger.kernel.org
Subject: Re: We have a whole new ton of goodies to investigate...
Date: Sun, 26 Apr 2015 23:22:23 +0200 [thread overview]
Message-ID: <20150426212223.GT8197@example.net> (raw)
[reading the list archive, that's why this is not a proper thread reply]
Alan Cox wrote 16 Apr 13:49 2015
> > Thanks for the interesting info about various toolchains for Fuzix. I
> > wonder why you include x86_16 target in the Fuzix challenge, as ELKS is
> > already playing on that ground, but that is your baby, so...
>
> I built the core that way mostly to check it compiled. Just portability
> testing.
I wonder, if Fuzix is sufficiently portable to run on 8086, could it
happen to offer a possibly even more suitable foundation for a usable
system, than the linux-derived code in ELKS?
I did not follow ELKS development over the years but it seems to be
a "from scratch" effort.
To compare, I saw once a fully functional BSD 2.9 kernel ported to 8086,
compatible with Venix/86 userspace and toolchain, which might have been
a more efficient (?) starting point too. Too bad, I think the port
is lost.
In other words, starting from a more limited (8-bit) or similar (16-bit)
platform might work better than "scaling down" from a 32-bit system.
The availability of the sources changed radically since the time when
ELKS was started. Now we have got even some pieces of Coherent/86.
> There certainly was
> plenty of stuff in ELKS that was taken from 386 Linux and is perhaps
> somewhat over-engineered for the job (buffer cache is perhaps one bit
> still)
I guess so. Sigh. The original V7's or even V6's quite basic design might
possibly suit 8086 better (I did not look at the ELKS kernel but I saw
V6/7 sources and also pieces of Venix/86 kernel which were apparently
build from literally the same C code, this seemed to work well).
> Going to multiple-segments for code isn't too difficult providing you
> don't follow every detail of pointers to function, but just stick to
> arrays of function pointers or function pointers within segment, but
> always seems to me like admitting defeat 8)
:)
The possiblity to use larger code makes life so much easier, without any
extra complexity in the compiler. Unfortunately there still are limits,
the total number of trampolines which are to fit in every code segment
and the size of a single function. Nevertheless it is very handy!
Rl
next reply other threads:[~2015-04-26 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 21:22 u-vpoa [this message]
2015-04-26 23:31 ` We have a whole new ton of goodies to investigate Alan Cox
2015-04-27 7:06 ` u-vpoa
2015-04-27 10:53 ` Alan Cox
2015-04-27 12:30 ` u-vpoa
2015-04-27 13:35 ` Alan Cox
2015-04-27 14:44 ` u-vpoa
-- strict thread matches above, loose matches on Subject: below --
2015-04-16 11:14 LM
2015-04-16 11:39 ` Alan Cox
2015-04-03 20:40 Alan Cox
2015-04-15 17:10 ` MFLD
2015-04-15 21:41 ` Alan Cox
2015-04-16 7:35 ` MFLD
2015-04-16 11:49 ` 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=20150426212223.GT8197@example.net \
--to=u-vpoa@aetey.se \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).