[RFC v2 00/16] barebox picotcp integration (2015.07.19)
s.hauer at pengutronix.de
Mon Jul 20 00:10:13 PDT 2015
On Sun, Jul 19, 2015 at 11:07:07PM +0300, Antony Pavlov wrote:
> I have just published latest picotcp-enabled barebox.
> Please see my 20150719.picotcp branch in my github barebox repo
> This version is based on the latest barebox-next and picotcp v1.5.0
> (there is also picotcp v1.5.1, but is has no interested
> for barebox changes since v1.5.0).
> Changes since 2015.07.15 (see http://lists.infradead.org/pipermail/barebox/2015-June/024174.html):
> * net: UDP API changed to satisfy the picotcp integration needs;
> * nfs, tftp and dns subsystems have no picotcp-related stuff anymore.
> * netconsole works on top of picotcp with no additional changes.
> Here are some notes:
> 1. just now tftp/nfs file transfer on top of picotcp is slower than
> the same transfer on top of legacy network stack;
> 2. there is no $<current network interface> anymore,
> so dhcp, tftp and ifup commands don't work on top of picotcp.
> The ifconfig command is used for network interfaces setup.
> N.B. There is an old patch for dhcp support on top of picotcp
> 3. The picoping command is used insted of traditional ping command.
First of all I applied patches 1-4 to next.
I can't get this version to work. I have done:
# mount -t tftp 192.168.23.4 /mnt/
# cp mnt/b b
T T T T could not open mnt/b: Interrupted system call
# picoping 192.168.23.4
---- Ping timeout!!!
PING 1 to 192.168.23.4: Error 1
picoping: I/O error
Anything I have missed?
I noticed that the MAC address is no longer set and the stack no longer
checks for a link. I believe picotcp should call eth_send rather than
invoking eth->send directly.
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox