From: Bart Veer <bartv@redhat.com>
To: Jitendrak@netbrahma.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] About Hal isolation.
Date: Mon, 22 Jan 2001 04:19:00 -0000 [thread overview]
Message-ID: <200101221219.f0MCJEt02019@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <13D467F625FAD511AE2A00D0B7B917D7089CB9@BRAHMA01>
>>>>> "Jitendra" == JITENDRA kanitkar <Jitendrak@netbrahma.com> writes:
Jitendra> i am new to the list. The question I am asking might be
Jitendra> trivial bur expecting some help from all of you.
Jitendra> Can we isolate HAL from Ecos so that we can put
Jitendra> something else on top of HAL (might be application
Jitendra> specific only)
Yes, that is one of the design goals. However please note that the HAL
is not completely self-contained, you must also have at least the
infrastructure package in place. If you use the "minimal" template
for an appropriate target that should give you a sensible starting
point: HAL, device drivers, infrastructure, and a couple of other
small support packages; no kernel, C library, or anything like that.
Bart
prev parent reply other threads:[~2001-01-22 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 6:34 JITENDRA kanitkar
2001-01-21 10:19 ` Jonathan Larmour
2001-01-22 4:19 ` Bart Veer [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=200101221219.f0MCJEt02019@sheesh.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=Jitendrak@netbrahma.com \
--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).