public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: danc@iobjects.com (Dan Conti)
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Re: Red Hat eCos and RedBoot news
Date: Tue, 10 Apr 2001 10:07:00 -0000	[thread overview]
Message-ID: <CAEMICOOKMKAGHPNGNFNOEPOCHAA.danc@iobjects.com> (raw)
In-Reply-To: <200104091617.f39GHot05863@mailhost.sv.trimedia.com>

just in case someone else hasn't already informed you, it's considered
really poor etiquette to send 15mb attachments to a mailing list.

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [ mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Julius
> Vanderspek
> Sent: Monday, April 09, 2001 9:18 AM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Re: Red Hat eCos and RedBoot news
>
>
>
> Hi Jonathan,
>
> A few months ago I ported eCos to the TriMedia TM1300
> (www.trimedia.com), and I would like to publish the
> results on your website.
>
> The problem is, however, that we maintain an ANSI SDE for
> our TriMedia processors, and this SDE does not support
> the gcc extensions; therefore I had to make
> a few patches in the directories that actually should not
> have been touched during porting. Most of these patches are
> in the build files. See also the attached port log for getting
> an idea on what I changed. I have also attached the complete
> ported source base for further reference.
>
> Do you have any suggestion on how to handle such a non-gcc port?
>
> Thanks,
>
> Juul VanderSpek,
>
>
>
>
>
>
> > X-Spam-Filter: check_local@mailhost.trimedia.com by digitalanswers.org
> > Mailing-List: contact ecos-announce-help@sourceware.cygnus.com;
> run by ezmlm
> > List-Unsubscribe:
> < mailto:ecos-announce-unsubscribe-juul=trimedia.com@sources.redhat.com >
> > List-Subscribe: < mailto:ecos-announce-subscribe@sources.redhat.com >
> > List-Archive: < http://sources.redhat.com/ml/ecos-announce/ >
> > List-Post: < mailto:ecos-announce@sources.redhat.com >
> > List-Help: < mailto:ecos-announce-help@sources.redhat.com >,
> < http://sources.redhat.com/ml/#faqs >
> > Delivered-To: mailing list ecos-announce@sources.redhat.com
> > Delivered-To: moderator for ecos-announce@sources.redhat.com
> > Date: Sat, 07 Apr 2001 02:59:58 +0100
> > From: Jonathan Larmour <jlarmour@redhat.com>
> > X-Accept-Language: en
> > MIME-Version: 1.0
> > To: ecos-announce@sources.redhat.com, eCos discussion
> <ecos-discuss@sources.redhat.com>
> > Subject: Red Hat eCos and RedBoot news
> > Content-Transfer-Encoding: 7bit
> > X-Logged: Logged by mailhost.trimedia.com as f39C7qU12879 at Mon Apr  9
> 05:07:52 2001
> >
> > Again Red Hat and the eCos community have been working hard to
> deliver more
> > new ports and features to eCos and RedBoot. Here's a highlight of some
> > exciting new functionality we've added recently:
> >
> > o eCos and RedBoot ported to the Compaq iPAQ PocketPC. Try out
> >   our eCos Microwindows demo for the iPAQ at
> >   http://sources.redhat.com/redboot/ipaq/ ! Support includes
> >   keypad, touch screen, watchdog, FLASH, PCMCIA and Compact
> >   Flash drivers. RedBoot includes support for booting ARM Linux.
> >   Derived from an initial port by Richard Panton of 3G Lab and
> >   enhanced significantly by Red Hat.
> >
> > o eCos/RedBoot port to the ARM Evaluator-7T. Currently beta quality.
> >
> > o eCos/RedBoot port to QED RM7000 Ocelot, including PCI, ethernet and
> >   FLASH support.
> >
> > o RedBoot ported to the MIPS Atlas eval board with MIPS32 4Kc or
> >   MIPS64 5Kc processor modules, including PCI, serial, ethernet and
> >   FLASH drivers.
> >
> > o RedBoot support for ARM PID/EPI Dev7/EPI Dev9 targets.
> >
> > o Port added to the Cosmo CEB-V850/SB1
> >
> > o Compressed image support has been added to RedBoot
> >
> > o ROM based file system support has been added, contributed by
> >   Richard Panton of 3G Lab.
> >
> > o Generic FLASH drivers added for Intel FlashFile 28Fxxx,
> >   AMD AM29xxxxx, Atmel AT29C040 and Intel StrataFLASH
> >
> > o Watchdog driver for Intel SA11x0 StrongARM added.
> >
> >
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> > Red Hat is exhibiting at the Embedded Systems Conference San Francisco,
> > from Tuesday April 10th to Thursday April 12th inclusive. Come
> and see us
> > demo RedBoot, eCos, and Embedded Linux on stand 2110! Visit
> > http://www.esconline.com/sf/ for more details about the show.
> >
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> > We've given parts of the eCos net site -
http://sources.redhat.com/ecos/ -
> a new look, particularly the Supported Hardware section, and we've added a
> new area dedicated to RedBoot at http://sources.redhat.com/redboot/
> Let us know what you think!
>
>
> Jonathan Larmour
> eCos Net maintainer
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062

  parent reply	other threads:[~2001-04-10 10:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09  9:34 Julius Vanderspek
2001-04-10  0:45 ` Christian Plessl
2001-04-10 13:35   ` Jonathan Larmour
2001-04-10 10:07 ` Dan Conti [this message]
2001-04-13  3:39 ` Jeff Lasslett
  -- strict thread matches above, loose matches on Subject: below --
2001-04-10  8:27 Julius Vanderspek
2001-04-06 19:00 [ECOS] " Jonathan Larmour
2001-04-09  7:23 ` [ECOS] " Markus Meng

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=CAEMICOOKMKAGHPNGNFNOEPOCHAA.danc@iobjects.com \
    --to=danc@iobjects.com \
    --cc=ecos-discuss@sources.redhat.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).