From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "'Ilija Kocho'" <ilijak@siva.com.mk>, <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Re: How to use IP/UDP/TCP checksum offload HW?
Date: Fri, 08 Jul 2011 11:37:00 -0000 [thread overview]
Message-ID: <004401cc3d63$589ef1d0$09dcd570$@netic.com> (raw)
In-Reply-To: <4E14B4D1.9000903@siva.com.mk>
Google only knows of CYGPKG_LWIP_CHECKSUMS in the email you sent.
I suspect it won't be much use to those of us that are using FreeBSD stack
either. Or will it?
...Laurie:{)
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Ilija Kocho
Sent: Thursday, 7 July 2011 5:18 AM
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: How to use IP/UDP/TCP checksum offload HW?
Regarding lwIP we have been knocking on open door.
Look for: CYGPKG_LWIP_CHECKSUMS
Ilija
On 07.06.2011 22:17, Laurie Gellatly wrote:
> Hi Simon,
> Are you doing anything about enabling hardware CRC in the new port
> that we should align to?
>
> ...Laurie:{)
>
>> -----Original Message-----
>> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
>> owner@ecos.sourceware.org] On Behalf Of John Dallaway
>> Sent: Wednesday, 8 June 2011 5:48 AM
>> To: Ilija Kocho
>> Cc: ecos-discuss@ecos.sourceware.org; Simon Kallweit
>> Subject: [ECOS] Re: How to use IP/UDP/TCP checksum offload HW?
>>
>> Hi Ilija
>>
>> Ilija Kocho wrote:
>>
>>>> It doesn't look like it's been touched for 5 years, but the guy who
>>>> set it up is still active on other projects on sourceforge.
>>> I guess this is fresher regarding lwIP:
>>> http://sourceware.org/ml/ecos-devel/2011-05/msg00003.html
>>> Only it might be stalled. John, is this an active project?
>> Yes. Simon Kallweit is working on the lwIP 1.4.0 port.
>>
>> John Dallaway
>> eCos maintainer
>> http://www.dallaway.org.uk/john
>>
>> --
>> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> and search the list archive:
>> http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2011-07-08 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 19:35 [ECOS] " Grant Edwards
2011-06-07 0:14 ` Laurie Gellatly
2011-06-07 0:57 ` [ECOS] " Grant Edwards
2011-06-07 2:18 ` Laurie Gellatly
2011-06-07 8:55 ` Ilija Kocho
2011-06-07 14:42 ` Grant Edwards
2011-06-07 16:06 ` Jay Foster
2011-06-07 16:46 ` Ilija Kocho
2011-06-07 19:48 ` John Dallaway
2011-06-07 20:17 ` Laurie Gellatly
2011-07-06 19:17 ` Ilija Kocho
2011-07-08 11:37 ` Laurie Gellatly [this message]
2011-06-07 20:27 ` Ilija Kocho
[not found] ` <34195.33997444$1307477887@news.gmane.org>
2011-06-07 20:29 ` Grant Edwards
2011-06-07 20:32 ` Ilija Kocho
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='004401cc3d63$589ef1d0$09dcd570$@netic.com' \
--to=laurie.gellatly@netic.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ilijak@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).