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

n is expected to make sure it received a proper packet to begin with. Changing the semantics of the API and require all applications to allocate a bigger buffer to handle this is not a solution in my opinion. In any case: the final verdict is with the U-Boot community. I stated my case a

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

en the smallest amount of data (say an ARP response) needs to allocate a 9K buffer. The question is not of effort -- there's virtually none. The question is whether this is good engineering. Worst case buffer allocation doesn't strike me as portable nor reasonable. My $0.02. -- Marcel Moolenaar xcl...@mac.com ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot