public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Hardware support
Date: Sat, 21 Aug 2004 20:23:00 -0000	[thread overview]
Message-ID: <4127AF49.4020403@eCosCentric.com> (raw)
In-Reply-To: <001a01c4875c$fba0fff0$450aa8c0@hierzo>

Udo van den Heuvel wrote:
> Hello,
> 
> I tried to build a toolchain for the CalmRISC16 (calm16_ceb) target using
> the info at http://ecos.sourceware.org/ecos/build-toolchain.html but found
> that the calm16 target is not supported. (errormessages, no references in
> sources, responses on the eCos mailinglist, etc)
> 
> Could you please let me know what is additionally needed to build a CalmRISC
> toolchain for eCos?

You're right in that I can't find any trace of a GNU toolchain made 
available by Samsung or publically. Note, as described at 
<http://ecos.sourceware.org/ecos/boards/calm16ceb.html>, the port was only 
even ever for core emulation hardware, not the real CPU. Also note that 
CalmRISC16 support is RedBoot-only, not eCos.

Mark Salter would know more authoratitively, but your only route may be to 
approach Samsung directly asking for it. It does exist, but was done under 
contract for Samsung so they're the ones to ask.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

      reply	other threads:[~2004-08-21 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21  8:58 Udo van den Heuvel
2004-08-21 20:23 ` Jonathan Larmour [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=4127AF49.4020403@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=udovdh@xs4all.nl \
    /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).