From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS Mailing List <linux-8086@vger.kernel.org>
Subject: Kernel size over 64K: what is needed, how to implement?
Date: Fri, 17 Feb 2012 13:20:56 -0500 [thread overview]
Message-ID: <4F3E9A88.7030105@jodybruchon.com> (raw)
ELKS can't compile to a size over 64K (the entire kernel must be in the
same code segment). ELKS will quickly expand beyond 64K simply by
selecting too many features. We need to be able to grow larger than 64K,
and I would like to discuss how to do this. My understanding is that
bcc/ld86 doesn't deal with 8086 far pointers at all. The outline of the
process as it appears to me is as follows:
* Support must be added to bcc/ld86 need to be able to use far pointers.
* A file format must be specified that includes relocation tables for
far pointers.
* A loader stub must be added to the kernel to relocate its own far
pointers at boot.
* After this is done, support should be added to load userland
executables this way too.
I'd like to know what everyone's thoughts are on this. If we do this
work, we will be further tying ourselves to bcc. I am seriously
considering adding a repository for dev86 to the ELKS project so that we
can change the toolchain as needed with more convenience (comments on
this are also welcome.) I see that there is an "ELKS format executable"
but it appears that it only deals with memory allocation technicalities,
so that isn't very helpful.
Thoughts?
Jody Bruchon
next reply other threads:[~2012-02-17 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 18:20 Jody Bruchon [this message]
2012-02-17 22:51 ` Kernel size over 64K: what is needed, how to implement? David Given
2012-02-19 21:36 ` David Given
2012-02-19 23:01 ` Kirn Gill
2012-02-20 0:51 ` David Given
2012-02-20 13:13 ` Alan Carvalho de Assis
2012-02-21 18:24 ` Juan Perez-Sanchez
2012-02-22 0:31 ` David Given
[not found] ` <FC79A7424F669341A72EFA787A3C767541F8ECD7@exchdb1-vm-srv.infopulse.local>
2012-02-22 14:53 ` Andrey Romanenko
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=4F3E9A88.7030105@jodybruchon.com \
--to=jody@jodybruchon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).