On Tuesday 09 September 2014 07:44 AM, Jamal Hadi Salim wrote: > On 09/08/14 10:41, Santosh Shilimkar wrote: > >>> The NetCP plugin module infrastructure use all the standard kernel >>> infrastructure and its very tiny. > > So i found this manual here: > http://www.silica.com/fileadmin/02_Products/Productdetails/Texas_Instruments/SILICA_TI_66AK2E05-ds.pdf > > Glad there is an open document! > There are a couple of ethernet switch chips I can spot there. > All the documentation is open including packet accelerator offload in ti.com. > Can i control those with "bridge" or say "brctl" utilities? > > I can see the bridge ports are exposed and i should be able to > control them via ifconfig or ip link. Thats what "standard > kernel infrastructure" means. Magic hidden in a driver is > not. > There is nothing magic hidden in the driver. The bridge ports are exposed as standard network interfaces. Currently the drivers don't support bridge offload functionality and the bridging is disabled in the switch by default. > Take a look at recent netconf discussion (as well as earlier > referenced discussions): > http://vger.kernel.org/netconf-nf-offload.pdf > > Maybe we can help providing you some direction? > The problem is it doesnt seem that the offload specs for > those other pieces are open? e.g how do i add an entry > to the L2 switch? > We got such requests from customers but couldn't support it for Linux. We are also looking for such support and any direction are welcome. Your slide deck seems to capture the key topics like L2/IPSEC offload which we are also interested to hear. Just to be clear, your point was about L2 switch offload which the driver don't support at the moment. It might confuse others. The driver doesn't implements anything non-standard. Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
