Re: [PATCH 0/2] P2020RDB eTSEC2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Renaud,

On Thu, Sep 13, 2012 at 06:41:49PM +0100, Renaud Barbier wrote:
> This patch set updates the gianfar driver and enables the port eTSEC2
> of the P2020RDB. Both eTSEC2 and eTSEC3 can be used.
> Also it has been noticed that dev_request_mem_region returns NULL when
> a region is already mapped. Some of the registers set may be the same between
> or within driver instances. This patch sorts out the conflict in region
> request.

That's not nice to have conflicting resources. The best solution would
be to register the phy independently of the network device and just use
the phy in the driver instead of registering it.
I see that with the current (generic network, mii) code this does not
work. Jean-Christophe currently works on phylib support which could
improve the situation somewhat. It may still not be possible to do what
you have to, but your patches will need adjustments to phylib anyway.

Could have have a look at it? I asked Jean-Christophe for sending the
phylib support again, and I think it can be merged then.

Thanks
 Sascha



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

_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox


[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux