public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Peter Vandenabeele <peter.vandenabeele@mind.be>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: [ECOS] eCos on NET+50
Date: Mon, 04 Nov 2002 17:14:00 -0000	[thread overview]
Message-ID: <3DC71B81.1040104@eCosCentric.com> (raw)
In-Reply-To: <20021030183929.E4352@mind.be>

Peter Vandenabeele wrote:
> On Sat, Oct 19, 2002 at 01:35:42PM +0200, Peter Vandenabeele wrote:
> 
>>On Sat, Oct 19, 2002 at 04:59:35AM +0100, Jonathan Larmour wrote:
>>
>>>Olaf Peters wrote:
>>>
>>>>Hi,
>>>>
>>>>I sucessfully and happily run eCos on an AMD-520 processor. Now I need
>>>>some OS+TCP/IP for a custom NET+ARM board (the NET+50 processor from
>>>>NetSilicon). In the latest CVS snapshot it seems not supported, are
>>>>there any patches available somewhere?
>>>
>>>There are enough ARM7 ports around it shouldn't be that mammoth a task. 
>>>Another option is to approach NetSilicon and, as a customer, persuade them 
>>>to pay for an eCos port.
>>
>>We did an internal eCos port on a Net+ARM 50 Development System we received for 
>>this purpose from NetSilicon [...]
> 
> 
> The patch for the Net+ARM 50 is attached. It was tested on the NetSilicon Net+50 
> evaluation board.

Hi Peter,

Is there any chance of this being contributed back officially (i.e. with 
copyright assignment to Red Hat etc.)?

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

           reply	other threads:[~2002-11-05  1:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20021030183929.E4352@mind.be>]

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=3DC71B81.1040104@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=peter.vandenabeele@mind.be \
    /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).