u-boot.git/net, branch v2015.10-rc5

net: support NETCONSOLE option via Kconfig

2015-09-30T02:54:46+00:00

This patch introduces CONFIG_NETCONSOLE as an option to the
Kconfig system.

Joe Hershberger pointed out that it may not be entirely free of
problems, as many boards predating the driver model define this
symbol directly via include files. In case they're not properly
migrated, their NetConsole might 'vanish' if they start to use
CONFIG_NET or CONFIG_NETDEVICES.

Signed-off-by: Bernhard Nortmann 
Acked-by: Joe Hershberger

net: expose eth_is_active() function to test network device state

2015-09-30T02:54:45+00:00

The previous eth_device struct returned by eth_get_dev() allowed
code to directly query the state member field. However, with
CONFIG_DM_ETH this data gets encapsulated (i.e. private), and
eth_get_dev() returns a udevice struct 'abstraction' instead.

This breaks legacy code relying on the former behaviour - e.g.
netconsole.
(see http://lists.denx.de/pipermail/u-boot/2015-June/216528.html)

The patch introduces a method to retrieve the ethernet device
state in a 'clean' and uniform way, supporting both legacy code
and driver model. The new function eth_is_active() accepts a
device struct pointer and tests it for ETH_STATE_ACTIVE.

Signed-off-by: Bernhard Nortmann 
Reviewed-by: Simon Glass 
Acked-by: Joe Hershberger

dm: eth: Correctly detect alias in eth_get_dev_by_name()

2015-09-09T13:48:03+00:00

When given a device name string, we should test to see if it is
really an alias like "eth#".

Signed-off-by: Bin Meng 
Acked-by: Joe Hershberger

dm: eth: Do not print misleading "Net Initialization Skipped"

2015-09-09T13:48:03+00:00

With driver model, board_eth_init() or cpu_eth_init() is not a must.
Thus we don't need print a misleading "Net Initialization Skipped".

Signed-off-by: Bin Meng 
Acked-by: Joe Hershberger

net: Revert "tftp: adjust settings to be suitable for 100Mbit ethernet"

2015-09-09T13:48:03+00:00

Commit 620776d "tftp: adjust settings to be suitable for 100Mbit ethernet"
causes the following error message when trying to load a file using 'tftp'
command via a tftp server.

    TFTP error: 'Unsupported option(s) requested' (8)

This is due to with commit 620776d changes, the tftp option 'timeout'
value is now set to zero which is an invalid value as per RFC2349 [1].
Valid values range between "1" and "255" seconds, inclusive. With some
tftp servers that strictly implement the RFC requirement, it reports
such an error message.

Revert commit 620776d for RFC compliance.

[1] https://www.ietf.org/rfc/rfc2349.txt

Signed-off-by: Bin Meng 
Acked-by: Joe Hershberger

net: tftp: Move tftp.h file from ./net to ./include/net

2015-09-07T11:41:04+00:00

This change gives the ability to reuse the  header file by other
subsystems (like e.g. dfu).

Without this change compilation error emerges for the legacy update.c file.

Signed-off-by: Lukasz Majewski 
Acked-by: Joe Hershberger

net: Return -EINTR when ctrl+c is pressed

2015-08-21T21:32:05+00:00

Current behavior is that if CTRL+C is pressed command returns 0 that was
successful which is not correct behavior.
The easiest test case is "tftpboot 80000 uImage && echo yes"
and press CTRL+C. Then the second command is called which is incorrect.

Error log:
zynq-uboot> tftpb 80000 uImage && echo yes
Gem.e000b000:7 is connected to Gem.e000b000.  Reconnecting to
Gem.e000b000
Gem.e000b000 Waiting for PHY auto negotiation to complete....... done
Using Gem.e000b000 device
TFTP from server 192.168.0.102; our IP address is 192.168.0.101
Filename 'uImage'.
Load address: 0x80000
Loading: ################
Abort
yes
zynq-uboot>

This patch adds -EINTR return value when CTRL+C is pressed.

Signed-off-by: Michal Simek 
Reviewed-by: Tom Rini 
Acked-by: Joe Hershberger

tftp: adjust settings to be suitable for 100Mbit ethernet

2015-08-21T21:31:00+00:00

Adjust timouts and retry counts to be suitable for loaded ethernet
network. With 5 seconds timeout, 10 retries maximum, tftp is
impossible even on local network with single full-speed TCP
connection.

100msec timeout should be suitable for most networks tftp is used on,
that is local ethernets. Timeout count really needs to be way higher,
as lost packets are normal when TCP is running over the same network.

Enforce 10msec minimum.

Signed-off-by: Pavel Machek 
Acked-by: Joe Hershberger

tftp.c: fix CONFIG_TFTP_TSIZE for small files

2015-08-12T19:15:28+00:00

CONFIG_TFTP_TSIZE should limit a tftp downloads progress to 50 '#'
chars. Make this work also for small files.

If the file size is small, i.e. smaller than 2 tftp block sizes the
number of '#' can get much larger. i.e. with a 1 byte file 65000
characters are printed, with a 512 byte file around 500.

When using CONFIG TFTP BLOCKSIZE together with CONFIG_IP_DEFRAG the
issue is more notable.

Signed-off-by: Max Krummenacher 
Signed-off-by: Marcel Ziswiler 
Reviewed-by: Marek Vasut 
Acked-by: Joe Hershberger

net: Allow drivers to return -ENOSYS with the write_hwaddr() method

2015-07-21T23:39:41+00:00

Some drivers may want to implement this method for some of their devices but
not for others. So it is not possible to just leave the operation out of
the table. Drivers could get around this by masquerading as two separate
drivers but that seems unpleasant.

Allow the driver to return an error when it does not want to process the
write_hwaddr() method.

Signed-off-by: Simon Glass