From: David Given <dg@cowlark.com>
To: linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Kernel size over 64K: what is needed, how to implement?
Date: Wed, 22 Feb 2012 00:31:00 +0000 [thread overview]
Message-ID: <4F443744.1040409@cowlark.com> (raw)
In-Reply-To: <CAD6VGuaWLJ1O9J1mXpRpjS1=Ri4LHDpJQm6aLJ6Uj-8Tt_t1ZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On 21/02/12 18:24, Juan Perez-Sanchez wrote:
[...]
> The suggestion is to use watcom to produce exe files and use the
> tcc4elks utility
> to convert to elks executables.
Allegedly the Watcom linker can produce flat files directly:
http://wiki.osdev.org/Watcom
ELKS binaries are really simple; IIRC they're just a file header and
then the text and data segments concatenated together. (Anyone got a
link?) It may be possible to persuade the linker to emit them without
needing conversion.
I also see that the Watcom linker can emit ELF and COFF files, but I
don't know whether it can emit the 16-bit versions (which are a rather
esoteric discipline).
What format is the kernel image in?
The hard-to-find Watcom linker manual is here, and the FORMAT directive
is documentated on page 61:
http://www.openwatcom.org/ftp/manuals/current/lguide.pdf
PS. Please don't cc me with replies; I am a list subscriber!
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Never attribute to malice what can be adequately explained by
│ stupidity." --- Nick Diamos (Hanlon's Razor)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2012-02-22 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 18:20 Kernel size over 64K: what is needed, how to implement? Jody Bruchon
2012-02-17 22:51 ` 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 [this message]
[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=4F443744.1040409@cowlark.com \
--to=dg@cowlark.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