lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] Stable release with IPv6 support


From: vincent cui
Subject: Re: [lwip-users] Stable release with IPv6 support
Date: Fri, 4 Nov 2011 05:31:54 +0000

Hi:

When will LWIP1.5.0 released ?

Vincent Cui
Sr. Firmware Engineer
Mobile: +8613255150315
Tel: +86 21 34612525x6104
Fax: +86 21 34619770
E-Mail: address@hidden
Shanghai EnLogic Electric Technology Co., Ltd.
Address: 1104-1106, Building A, No.391, Guiping Road, Xuhui District, Shanghai, 
200233
 

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of vincent cui
Sent: 2011年11月1日 21:57
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Stable release with IPv6 support

Hi:

I just wonder to know that the release code for IPV6 could be ported to 
LWIIP1.3.2 , anyone care this?



Vincent Cui
Sr. Firmware Engineer
Mobile: +8613255150315
Tel: +86 21 34612525x6104
Fax: +86 21 34619770
E-Mail: address@hidden
Shanghai EnLogic Electric Technology Co., Ltd.
Address: 1104-1106, Building A, No.391, Guiping Road, Xuhui District, Shanghai, 
200233
 

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Mason
Sent: 2011年10月27日 16:48
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Stable release with IPv6 support

Kieran Mansley wrote:
> I haven't yet decided, or given enough thought to, what features
> other than IPv6 should be included in the 1.5.0 release.

Support for zero-copy DMA drivers (RX and TX) with netconn API  :-)

On RX, I used
CORE_LOCKING=1
CORE_LOCKING_INPUT=1
PBUF_REF custom pbuf with custom free function

Simon wrote:
> For the RX side, using a *custom* PBUF_REF would be the best solution. 
> That's a pbuf that has a 'freed' callback and references external 
> memory. However, that doesn't work, yet (though I planned to add support 
> for it as I can see it's one possible solution to implement DMA MAC 
> drivers). The problem here is that pbuf_header() can't grow such pbufs 
> (as it doesn't know the original length). This would have to be fixed by 
> changing the struct pbuf (if only for PBUF_REF pbufs).

I haven't found how to make TX work without copying the frame before
sending, yet.

-- 
Regards.

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

reply via email to

[Prev in Thread] Current Thread [Next in Thread]