From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: Ilija Stanislevik <ilijas@siva.com.mk>, ecos-devel@ecos.sourceware.org
Subject: Re: Ethernet over SPI driver for ENC424J600
Date: Mon, 26 Oct 2009 21:28:00 -0000 [thread overview]
Message-ID: <20091026212810.GA12538@sg-laptop> (raw)
In-Reply-To: <4AE58C05.9000305@ecoscentric.com>
On Mon, Oct 26, 2009 at 11:46:13AM +0000, Alex Schuilenburg wrote:
> John Dallaway wrote on 2009-10-26 09:05:
> > Ilija Stanislevik wrote:
> >> Dear fellows,
> >>
> >> I use this opportunity to announce our development project. It is
> >> a driver for Microchip's ENC424J600 Ethernet controller.
[snip]
Thank you!
> > This is great news. Thank you for letting the eCos community know
> > of your plans at an early stage.
[snip]
> > 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/
[snip]
> I think it is fair to advise you of the risks involved in using the
> newer lwIP 1.3.1 stack and of more stable options available to you
> when developing new code for eCos. Since you are developing a new
> device driver, I suggest you initially stick with the FreeBSD port
> (and optionally older lwIP port) which are known to work reliably,
> rather
Hello guys, may be I miss something but I thought that any Ethernet
eCos driver is enough abstract thing to manage ETH L2 and that does
not depend (well, depends a bit) on any next layer, e.g., a TCP/IP
implementation (RedBoot TCP/IP, *BSD, lwIP* stacks) even if the driver
uses another channel (SPI) to get a memory access to MAC buffers. I
talk about generic io/eth/* stuff and..., well some kind of a future
devs/eth/mc/spi/* eth_drv_.* routines, for example. Why do you "link"
ya L2 controller with some kind of the TCP/IP? I do not understand it
enough. Will it be able to use that driver w/out interrupts in a
polling mode, i.e. to use RedBoot's TCP/IP=GDB? If it won't be, well,
that is code limits, why the lwIP 1.X.X TCP/IP only then?
Thank you for any clarifications, Regards
Sergei
next prev parent reply other threads:[~2009-10-26 21:28 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
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 [this message]
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=20091026212810.GA12538@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=alexs@ecoscentric.com \
--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).