public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Tran, Linh Q" <TranLQ@navair.navy.mil>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Writing BSP for PowerPC 750
Date: Wed, 07 Jul 2004 16:25:00 -0000	[thread overview]
Message-ID: <1089217544.3988.1542.camel@hermes> (raw)
In-Reply-To: <22747B115F69AD47B2530DB230CCF15C37770D@nwms12.chinalake.navy.mil>

On Tue, 2004-07-06 at 18:20, Tran, Linh Q wrote:
> Hello,
> 
> I'm trying to port eCos to a board using PowerPC 750 process (it is the
> DMV-179 board from DY4).  Does anybody know which current eCos HAL platform
> would make a good baseline to start the porting process?
> Appreciate your help.
> 
> Alex Tran
> F/A-18 SHARP SWDTT
> 41K200D
> (760) 939-4468
tranlq@navair.navy.mil

Firstly, this question would have been better asked on eCos discuss.  
This [the maintainers] list is not really for technical questions.

That said, the proper HAL variant would be the PPC60x.  Your platform
would be a target that uses this variant.  Since the 750 has no builtin
I/O (as most of the other PPC platforms do), you'll have some work to
port various I/O drivers (serial, interrupts, ethernet, ...)  We don't
really have a similar PPC platform to give as an example.

This may be a non-trivial task (I don't know much about your board), but
you may want to consider [professional] help.  The online documentation
can guide you, but it's still going to be an effort.

Support/consultation is available from
  MLB Associates (me) - info@mlbassoc.com
  eCosCentric         - info@ecoscentric.com

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates

      reply	other threads:[~2004-07-07 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07  0:20 Tran, Linh Q
2004-07-07 16:25 ` Gary Thomas [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=1089217544.3988.1542.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=TranLQ@navair.navy.mil \
    --cc=ecos-maintainers@ecos.sourceware.org \
    /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).