[U-Boot] [PATCH] eth_receive(): Do not assume that caller always wants full packet.

[Piotr Zięcik]

Thursday 16 July 2009 14:39:59 Wolfgang Denk napisał(a):
>
> But recv() is on another level. Here we are dealing with receiving raw
> ethernet frames.
>

I think that there is an analogy. Both function could be used for receiving 
_frames_. eth_receive() for ethernet frames and Linux recv() for UDP frames.

> > function. I do not see why we have to force application to prepare 1,5kB
> > buffer for received packets when for example it waits for ARP reply.
>
> Come on - what exactly is the extra effort you have to spend to
> prepare a bigger buffer?
>

Maybe I have used bad example. When application prepares a buffer
and chooses it's size to be less than interface MTU it means that application 
is not able to process larger packets. U-Boot should not expect that simple
application using API is able to handle every possible case (for example
9k packets on gigabyte ethernet).

-- 
Pozdrawiam.
Piotr Zięcik