From: Jesper Skov <jskov@cygnus.co.uk>
To: "Patrick O'Grady" <patrick@plasticgrape.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] hal/i386/pc prerelease.
Date: Fri, 15 Oct 1999 01:55:00 -0000 [thread overview]
Message-ID: <otzoxlqbbm.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <Pine.BSF.4.05.9910141549090.24768-100000@pru.plasticgrape.com>
>>>>> "Patrick" == Patrick O'Grady <patrick@plasticgrape.com> writes:
Patrick> Just wanted to let you all know that I've posted a *very
Patrick> early* but actually functional version of a hal for running
Patrick> eCos on a standard '386 or better PC.
Nice one! :)
Patrick> A question for Cygnus: there was a lot of platform-specific
Patrick> initialization I had to put in the file vectors.S--since the
Patrick> linker is told to put that module first. Unfortunately
Patrick> vectors.S is stored in the 'arch' tree rather than the
Patrick> platform tree. Is there any plans to separate this? I'd
Patrick> suggest doing a careful audit of that file in order to split
Patrick> it into a platform specific part (for PCs which boot from a
Patrick> floppy or other PC-type boards which boot out of ROM) and an
Patrick> architecture part (for all 386's). I think that the first
Patrick> file in the linker script should be stored in the platform
Patrick> tree, not the arch tree.
The vectors.S should contain mostly platform neutral code. When
there's a need for platform specific stuff, it should be handled via
macros/calls defined by platform files.
The current i386 HAL is a bit out of shape in this regard. The ARM HAL
is a better example of how things should be handled for multiple
platforms.
Patrick> Anyway, I've been working on this for the past couple of
Patrick> weeks, and now that I've got the threading to work, I'm going
Patrick> to move over and start doing some actual applications work...
Patrick> which means that I'll be slowing down as far as completing
Patrick> the port. Anyone who cares to get involved is encouraged to
Patrick> tinker with this... I'm sure that I'll be posting updates
Patrick> fairly frequently, so if you're at all timid about dealing
Patrick> with the stuff that's missing here, just hang tight. Post
Patrick> any questions or observations to
Patrick> ecos-discuss@sourceware.cygnus.com... I'll try to answer any
Patrick> questions which come up there.
I'd like (obviously) to have a look at this, but it's unclear when I
will get the time to actually "tinker" with it. Unlikely to be within
the next couple of weeks though.
Jesper
next prev parent reply other threads:[~1999-10-15 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-14 16:21 Patrick O'Grady
1999-10-15 1:55 ` Jesper Skov [this message]
1999-10-15 3:30 ` Nick Garnett
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=otzoxlqbbm.fsf@thinktwice.zoftcorp.dk \
--to=jskov@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=patrick@plasticgrape.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).