public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Chiou, Charles" <charleschiou@mips.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: RE: eCos port/update for MIPS malta & sead3 platforms
Date: Thu, 06 Dec 2012 07:23:00 -0000	[thread overview]
Message-ID: <CD9FF9C3FDCD2E44BAB54EDCC176E15EC0C8E3@exchdb03.mips.com> (raw)
In-Reply-To: <50BCBE0E.6040104@dallaway.org.uk>

Hi John,

> > Specifically, the patches will:
> >
> >         - Update outdated drivers for proper hardware support on modern
> malta
> >         - Support the SEAD3 board
> >         - Retain compatibility with QEMU's malta emulator
> 
> I have experimented with QEMU's Malta emulation and the eCos
> malta_mips32_4kc target in the past. I was able to boot RedBoot but QEMU's
> PCI support (required for eCos/RedBoot networking) seemed to be broken. Is
> this working now?

Yes, we've fixed this problem. The QEMU and real hardware addresses are different, but we've created different configs so that both are supported.

> 
> >         - Support the newest mips-sde-elf-gcc toolchain (Sourcery
> > CodeBench Lite 2012.03-64)
> 
> Does your current eCos code continue to build with the eCos mipsisa32-elf
> toolchain (GCC 4.3.2)?


No. Building with mipsisa32-elf hasn't been verified. I'll give it a try.

> > Since we only focused on booting from Yamon and u-boot, we only tested
> > RAM configurations. However, if RedBoot support is required, we can
> > work with the maintainer to get a clean patch in, too.
> 
> It would be good to support RedBoot, certainly we would wish to avoid
> breaking the existing RedBoot support for MIPS Malta.

Ok, I'll try with RedBoot, too.

> > Please let me know how I can proceed with sending the patch upstream.
> 
> The procedure for contributing to eCos (via a Bugzilla report) is described at:
> 
>    http://ecos.sourceware.org/fom-serv/ecos/cache/45.html

I'll send the existing patch as is and get some feedback while the items mentioned above are being investigated from our end.

Thank you!

--
Best,
Charles Chiou

      reply	other threads:[~2012-12-06  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 12:50 Chiou, Charles
2012-12-03 14:58 ` John Dallaway
2012-12-06  7:23   ` Chiou, Charles [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=CD9FF9C3FDCD2E44BAB54EDCC176E15EC0C8E3@exchdb03.mips.com \
    --to=charleschiou@mips.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).