public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Ilija Stanislevik <ilijas@siva.com.mk>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Ethernet over SPI driver for ENC424J600
Date: Mon, 26 Oct 2009 09:05:00 -0000	[thread overview]
Message-ID: <4AE56642.20201@dallaway.org.uk> (raw)
In-Reply-To: <4AE546ED.3000303@siva.com.mk>

Hi Ilija

Ilija Stanislevik wrote:

> Dear fellows,
> 
> I use this opportunity to announce our development project. It is a
> driver for Microchip's ENC424J600 Ethernet controller.
> 
> My company's goal is to obtain a low level Ethernet driver which will
> use standard SPI support to communicate with the Ethernet chip. The
> development is underway on STM3210E-EVAL board. We will be glad if we
> succeed to make it independent from platform and SPI hardware.
> 
> Further, we plan to contribute the result of this development, as
> proposed in http://ecos.sourceware.org/contrib.html. Please advise us on
> the next step in this direction.

This is great news. Thank you for letting the eCos community know of
your plans at an early stage.

This driver could be useful for many eCos developers who need to add
ethernet to an existing hardware design. I note that Microchip offers a
daughter board which includes the (similar) ENC624J600 and should make
it easy for others to start experimenting with these parts:

http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en543132

Are you intending to use lwIP or the FreeBSD TCP/IP stack in your
project? Regardless, I would encourage you to verify correct operation
with Simon Kallweit's port of lwIP 1.3.1:

  http://download.westlicht.ch/

lwIP is a good fit for eCos and I hope lwIP 1.3.1 will be integrated in
eCos CVS soon.

At some point, you will need to complete the FSF copyright assignment
paperwork. All contributors to your driver will need to make a copyright
assignment. I would recommend getting this sorted out early to avoid
delays when the driver is ready. Full instructions are available at:

  http://ecos.sourceware.org/assign.html

Finally, if you are able to collaborate with the wider eCos community on
this project, we can add it to the list of registered projects. Ref:

  http://ecos.sourceware.org/contrib.html#registered

John Dallaway

  reply	other threads:[~2009-10-26  9:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  6:51 Ilija Stanislevik
2009-10-26  9:05 ` John Dallaway [this message]
2009-10-26 11:18   ` Ilija Stanislevik
2009-10-26 12:04     ` John Dallaway
2009-10-29 17:40       ` Ilija Stanislevik
2009-10-31 10:00         ` John Dallaway
2009-10-26 11:46   ` Alex Schuilenburg
2009-10-26 21:28     ` Sergei Gavrikov
2009-10-26 22:17       ` John Dallaway
2009-10-27  7:57         ` Ilija Kocho
2009-10-27 10:08           ` Sergei Gavrikov
  -- strict thread matches above, loose matches on Subject: below --
2010-02-16  8:20 Ilija Stanislevik
2010-02-16 19:03 ` John Dallaway
2010-02-28 13:40   ` Ilija Stanislevik
2010-06-22  9:56     ` Ilija Stanislevik
2010-02-03  9:37 Ilija Stanislevik
2010-02-03 13:13 ` Simon Kallweit
2010-02-04  9:17 ` John Dallaway
2010-02-05  7:59   ` Ilija Stanislevik
2010-02-05  8:16   ` Ilija Kocho
2010-02-05 10:26     ` Ross Younger
     [not found] <894030.6104.qm@web8316.mail.in.yahoo.com>
2009-10-26  8:21 ` Ilija Stanislevik
2009-10-06 13:51 NAND technical review Ross Younger
2009-10-07  9:40 ` Jürgen Lambrecht
2009-10-13  2:44   ` Jonathan Larmour
2009-10-13 12:59     ` Rutger Hofman
2009-10-15  4:41       ` Jonathan Larmour
2009-10-19 10:53         ` Ross Younger
2009-10-20  1:40           ` Jonathan Larmour
2009-10-20 10:17             ` Ross Younger
2009-10-21  2:06               ` Jonathan Larmour
2009-10-22 10:05                 ` Ross Younger
2009-11-10  5:15                   ` Jonathan Larmour
2009-11-10 10:38                     ` Ross Younger
2009-11-10 11:28                       ` Ethernet over SPI driver for ENC424J600 Ilija Stanislevik
2009-11-10 12:16                         ` Chris Holgate

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=4AE56642.20201@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ilijas@siva.com.mk \
    /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).