Hi Simon,
On Sun, Mar 1, 2015 at 10:33 AM, Simon Glass sjg@chromium.org wrote:
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.
That's a good idea for dealing with this for now. I have a series I started where I replace all of this (hence I didn't include it in the eth_initialize() of my dm/eth series). This will allow dm/eth to be used on hardware with fairly low churn in the mean time.
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 sjg@chromium.org
Acked-by: Joe Hershberger joe.hershberger@ni.com