From: Ferenc Cserepkei <csfera@gmail.com>
To: ecos-devel@sources.redhat.com
Subject: Re: porting ecos to a "new" hardavre.
Date: Mon, 05 Mar 2012 16:00:00 -0000 [thread overview]
Message-ID: <CANBX_3Y7Jt7CSPx33ysTF-md8KR5kMADRLW+OK9Q5OD0iVou3g@mail.gmail.com> (raw)
In-Reply-To: <CANBX_3baYa7z9rCuPDgbOUHLGYXb6qGPHe8g8z+bXo_UxjuhQQ@mail.gmail.com>
Welcome.
I am maintaining some embedded hardvare, the board has some custom
brew bios. We should add tcp/ip (preferably V6) functionlity soon. The
existing BIOS the board has rather dumb, its main functionalty is
BASIC configuration of the FPGAs and ASICs the board has, give a
9600/8N1 serial, and upgrade sw parts in motorola s-record format (can
be streamed over serial). I already built a GCC 4.6.2 sporting
newlib1.20 for the main processor what is freescale MPC8548.
My question is, how can i tell ecos 3.0, to use that compiler (it has
GDB 7.3, psim and python support) and how can i design a template
"build>templates" for our systems?
Any help are much elcome.
BR:
Ferenc
parent reply other threads:[~2012-03-05 16:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANBX_3baYa7z9rCuPDgbOUHLGYXb6qGPHe8g8z+bXo_UxjuhQQ@mail.gmail.com>]
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=CANBX_3Y7Jt7CSPx33ysTF-md8KR5kMADRLW+OK9Q5OD0iVou3g@mail.gmail.com \
--to=csfera@gmail.com \
--cc=ecos-devel@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).