From: Andrew Lunn <andrew@lunn.ch>
To: James Yates <j.yates@quartzuk.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] SH2 Ports
Date: Thu, 16 Oct 2003 11:53:00 -0000 [thread overview]
Message-ID: <20031016115343.GG32391@lunn.ch> (raw)
In-Reply-To: <CB39E7B8FC98924D85DFBED207E4CC98344211@ip02.quartzelec.adsl.gxn.net>
> I tried building my platform for an SH3 variant with complete
> success, so I am guessing something is wrong with the SH2 variant
> but without any other SH2 platform ports, it is difficult for me to
> judge. I have seen mentions of a few people requiring a port of eCos
> to SH2 but no mention of anyone actually having done it. My feeling
> was that maybe this is a compiler bug, gcc v3.2.1 so I have
> downloaded and tried to build gcc for SH-elf target v 3.3.1 and
> v3.2.2 but also without success.
Reading what little information that is in eCos, it looks like there
has been a SH2 port in the past. There is a driver for the SH2-etherC
Ethernet Controller as well. What this normally means is that the
(ex)RedHat guys where contracted to port to a customers SH2
board. This was never made public either because it was a custom
designed board not a development board, or the customer did not want
it made public.
I suggest you contact the exRedHat guys who now work at eCosCentric
and see what they can tell you. Maybe the port also had a custom
version of gcc and the changes never got rolled back into the
mainstream version? Maybe they can point you towards the old compiler
sources etc...
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-10-16 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 11:33 James Yates
2003-10-16 11:53 ` Andrew Lunn [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=20031016115343.GG32391@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=j.yates@quartzuk.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).