From: Gary Thomas <gary@mlbassoc.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Are the HALs in the eCos repository meant for deployment?
Date: Mon, 14 Aug 2006 12:00:00 -0000 [thread overview]
Message-ID: <44E065F1.6070604@mlbassoc.com> (raw)
In-Reply-To: <c09652430608140454i6188b779vc361ab6909fde721@mail.gmail.com>
Ãyvind Harboe wrote:
> On 8/14/06, Gary Thomas <gary@mlbassoc.com> wrote:
>> Ãyvind Harboe wrote:
>> > Are the HALs in the eCos repository meant for deployment?
>>
>> Absolutely! Every one that's in the repository is for some board or
>> device that [at least at
>> some time in the past] existed and the platform could be built and run
>> with no software "tweaks".
>
> But are development/eval boards deployed? I would have thought that
> largely microcontrollers would go on some custom PCB
>
I disagree - there are many "development/eval" boards that make it
into the real world (I personally know of many*many thousands...)
Yes, there may be some development boards that are modified, however
slightly, before deployment, but I firmly believe that the basic
structure of eCos should be sound enough that these changes should
be easily added/adjusted in the various HAL and other packages.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-08-14 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 19:37 Øyvind Harboe
2006-08-14 11:21 ` Gary Thomas
2006-08-14 11:54 ` Øyvind Harboe
2006-08-14 12:00 ` Gary Thomas [this message]
2006-08-14 12:08 ` Andrew Lunn
2006-08-14 12:17 ` Øyvind Harboe
2006-08-14 12:33 ` Andrew Lunn
2006-08-14 12:35 ` Gary Thomas
2006-08-14 12:52 ` Øyvind Harboe
2006-08-14 13:28 ` Bart Veer
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=44E065F1.6070604@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=oyvind.harboe@zylin.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).