u-boot.git/net/eth.c, branch v2015.10

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: 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

dm: eth: Avoid blocking on packet reception

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

Some devices can take a long time to work out whether they have a new packet
or now. For example the ASIX USB Ethernet dongle can take 5 seconds to do
this, since it waits until it gets a new packet on the wire before allowing
the USB bulk read packet to be submitted.

At present with driver mode the Ethernet receive code reads 32 packets. This
can take a very long time if we must wait for all 32 packets. The old code
(before driver model) worked by reading a single set of packets from the USB
device, then processing all the packets with in. It would be nice to use
the same behaviour with driver model.

Add a flag to the receive method which indicates that the driver should try
to find a packet if available, by consulting the hardware. When the flag is
not set, it should just return any packet data it has already received. If
there is none, it should return -EAGAIN so that the loop will terminate.

Signed-off-by: Simon Glass

net: Handle ethaddr changes as an env callback

2015-05-21T13:16:16+00:00

When the ethaddr is changed in the env, update the device pdata at the
same time (only if it is probed for the DM case; only if registered for
the non-DM case). Again this gets us closer to completely non-polled
env needed to simplify the net_loop.

This requires that the NET feature select the REGEX feature.

Signed-off-by: Joe Hershberger

net: Remove duplicate bootfile syncing functionality

2015-05-21T13:13:20+00:00

The bootfile env var is already kept up to date by the callback in net.c
so there is no need to poll it too.

Signed-off-by: Joe Hershberger

net: Implement random ethaddr fallback in eth.c

2015-05-19T18:33:21+00:00

Implement the random ethaddr fallback in eth.c so it is in a common
place and not reimplemented in each board or driver that wants this
behavior.

Signed-off-by: Joe Hershberger 
Reviewed-by: Simon Glass

net: Update hardware MAC address if it changes in env

2015-05-19T18:33:21+00:00

When the ethaddr changes in the env, the hardware should also be updated
so that MAC filtering will work properly without resetting U-Boot.

Also remove the manual calls to set the hwaddr that was included in a
few drivers as a result of the framework not doing it.

Reported-by: Michal Simek 
Signed-off-by: Joe Hershberger 
Tested-by: Michal Simek

dm: net: Use existing Ethernet init for driver model

2015-04-18T17:11:36+00:00

At present even with driver model is used there is still much manual init
of related devices: PHY, environment and board init. Until these requirements
are dealt with in another way we need to keep them around.

Break out the init portion of the legacy eth_initialize() into a separate
function and call it from both the legacy and driver model eth_initialize()
functions.

Signed-off-by: Simon Glass 
Acked-by: Joe Hershberger