[U-Boot] [PATCH 0/4] Network defrag

Robin Getz rgetz at blackfin.uclinux.org
Wed Aug 12 22:53:23 CEST 2009


On Wed 12 Aug 2009 16:05, Ben Warren pondered:
> Hi Robin,
> 
> Robin Getz wrote:
> > On Mon 10 Aug 2009 15:57, Ben Warren pondered:
> >   
> >> Robin Getz wrote:
> >>     
> >>> Thanks to Alessandro for putting it together.
> >>>
> >>> Feel free to add my Signed-off (once the docs have been updated
> >>> explaining what this is all for).
> >>>
> >>>   
> >>>       
> >> I'll do that.  Thanks for all your help.
> >>     
> >
> > Some info for the docs, when I was troubleshooting a Ubuntu 9.04 install.
> > ======
> >
> > It appears that some tftp servers (the older BSD version,
> > Debian's "tftpd") doesn't support RFC 2348 (blksize), and always use
> > a block size of 512 :( You  need to make sure that you install the 
> > the Peter Anvin version, which does support  RFC 2348, and blksize up
> > to 65,464 bytes (Debian's "tftpd-hpa"):
> > http://www.kernel.org/pub/software/network/tftp/ 
> >   
> Maybe it would make sense to have a message printed if the user 
> specifies a higher blocksize but the TFTP server doesn't respond to the 
> 'blksize' request.  Thoughts?

It doesn't happen today...

We request 1468 (today), and if don't get an respose to the blksize request, 
it falls back to 512 (with the BSD tftpd) - no message to the user - it just 
takes longer, and people complain about a crappy network driver...

To me - this is independent of the defragmentation patch. If we request 1468 
(MTU) or 1469 (which will be fragmented) - the logic in tftp.c is the same...

There is already a debug("Blocksize ack... in the code - so I'm assuming that 
if someone wanted to figure it out - they just need to turn on DEBUG in 
tftp.c - rather than printing it out all the time...

-Robin


More information about the U-Boot mailing list