public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Patrick Doyle" <wpd@delcomsys.com>
To: "Jonathan Larmour" <jifl@eCosCentric.com>
Cc: "eCos Discussion" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Possible typo in hal/arm/arm9/var/current/include/hal_cache.h
Date: Wed, 08 Jan 2003 14:31:00 -0000	[thread overview]
Message-ID: <NFBBJAJICAKJPMMKDAGBKEFODIAA.wpd@delcomsys.com> (raw)
In-Reply-To: <3E1B489D.5010701@eCosCentric.com>

Thanks... I'll do that right now.  BTW, I didn't mean to imply that full
support for eCos would not be forthcoming, it's just not on the roadmap for
the quickest route to our end goal.  (Getting a bootloader that we knew,
such as RedBoot, was on that roadmap.  Getting a full version of eCos up and
running is also on the roadmap, just not as soon).

--wpd


> -----Original Message-----
> From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
> Sent: Tuesday, January 07, 2003 4:38 PM
> To: Patrick Doyle
> Cc: eCos Discussion
> Subject: Re: [ECOS] Possible typo
> inhal/arm/arm9/var/current/include/hal_cache.h
specific" tests).
>
> Patrick, one other thing you could do is ask Red Hat to release
> their OMAP
> port. I'm fairly sure that included the support required for eCOs (ints,
> rtc, etc.) too, not just redboot, but I could be wrong.
> <msalter@redhat.com> is probably the best starting point.
>


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2003-01-08 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 18:53 Patrick Doyle
2003-01-07 20:18 ` Jonathan Larmour
2003-01-07 20:24   ` Gary D. Thomas
2003-01-07 21:00     ` Patrick Doyle
2003-01-07 21:14       ` Gary D. Thomas
2003-01-07 21:31         ` [ECOS] Possible typo inhal/arm/arm9/var/current/include/hal_cache.h Patrick Doyle
2003-01-07 21:36           ` Gary D. Thomas
2003-01-07 21:39             ` Jonathan Larmour
2003-01-08 14:31               ` Patrick Doyle [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=NFBBJAJICAKJPMMKDAGBKEFODIAA.wpd@delcomsys.com \
    --to=wpd@delcomsys.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jifl@eCosCentric.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).