On Wed, Apr 22, 2015 at 04:14:33PM +, Jan Kaisrlik wrote:
> 2015-04-21 17:51 GMT+00:00 Florian Fainelli :
> > On 21/04/15 10:39, Andrew Lunn wrote:
> I would however say that sysfs is the wrong API. The linux network
> stack uses netlink for most configuration activities. So i would
>
2015-04-21 17:51 GMT+00:00 Florian Fainelli :
> On 21/04/15 10:39, Andrew Lunn wrote:
I would however say that sysfs is the wrong API. The linux network
stack uses netlink for most configuration activities. So i would
suggest adding a netlink binding to DSA, and place the code in
>>>
On 21/04/15 10:39, Andrew Lunn wrote:
>>> I would however say that sysfs is the wrong API. The linux network
>>> stack uses netlink for most configuration activities. So i would
>>> suggest adding a netlink binding to DSA, and place the code in
>>> net/dsa/, not within an MDIO driver.
>>
>> I suppo
On 21/04/15 10:30, Andrew Lunn wrote:
>> My goal in reworking this weird DSA device/driver model is that you
>> could just register your switch devices as an enhanced
>> phy_driver/spi_driver/pci_driver etc..., such that libphy-ready drivers
>> could just take advantage of that when they scan/detec
> > I would however say that sysfs is the wrong API. The linux network
> > stack uses netlink for most configuration activities. So i would
> > suggest adding a netlink binding to DSA, and place the code in
> > net/dsa/, not within an MDIO driver.
>
> I suppose we could do that, but that sounds li
> My goal in reworking this weird DSA device/driver model is that you
> could just register your switch devices as an enhanced
> phy_driver/spi_driver/pci_driver etc..., such that libphy-ready drivers
> could just take advantage of that when they scan/detect their MDIO buses
> and find a switch. We
On 21/04/15 05:47, Andrew Lunn wrote:
> Hi Jan
>
> Interesting work, but i think the architecture is wrong.
>
> DSA needs an Ethernet device, an MDIO bus, and information about ports
> on the switch.
That requirement is completely artificial as it is today, and just comes
from arbitrary limitat
Hi Jan
Interesting work, but i think the architecture is wrong.
DSA needs an Ethernet device, an MDIO bus, and information about ports
on the switch. The MDIO bus and the Ethernet need no knowledge of
DSA. So putting your DSA configuration code in the MDIO driver is
wrong.
The problem you have i
From: Jan Kaisrlik
This RFC patch enables connecting a DSA-based switch to the USB RMII interface.
I use switch Marvell 88E6065 as the DSA-based switch
connected to USB RMII interface provides by Asix AX88772b.
I temporarily modified the mv88e6060 driver to work with 88E6065.
Jan Kaisrlik (3):
