public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@cygnus.co.uk>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] hal/i386/pc prerelease.
Date: Fri, 15 Oct 1999 03:30:00 -0000	[thread overview]
Message-ID: <pozoxlylq4.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <otzoxlqbbm.fsf@thinktwice.zoftcorp.dk>

Jesper Skov <jskov@cygnus.co.uk> writes:

> 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.

Even better, look at the MIPS HAL. This is the way all future HALs
will be built, with architecture, variant and platform sub-HALs with
well-defined ways for them to pass information to each other and
override things.



-- 
Nick Garnett           mailto:nickg@cygnus.co.uk
Cygnus Solutions, UK   http://www.cygnus.co.uk

      reply	other threads:[~1999-10-15  3:30 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
1999-10-15  3:30   ` Nick Garnett [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=pozoxlylq4.fsf@balti.cygnus.co.uk \
    --to=nickg@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.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).