Roman Yeryomin wrote:
> > If you have a datasheet, is there a bit to maybe disable the vlan
> > support of the internal switch so it'll just pass on the packets
> > like a dumb switch? That should simplify things when the internal
> > switch isn't really used at all like in said WL-351.
>
> Datas
On 31 January 2012 13:21, Tobias Diedrich wrote:
>> I think that this is definitely a good thing.
>> But we must be careful to fully switch to it because, eg., belkin
>> board I have (and probably others with external switch) requires
>> double tagging control to enable external switch (will post
Tobias Diedrich wrote:
> + dev_info(&pdev->dev, "about to fill out switch_dev struct\n");
> + dev_info(&pdev->dev, "about to call register_switch\n");
Hmm, just noticed that I left those two debugging statements in the
code, they can be removed.
--
Tobias
Roman Yeryomin wrote:
> On 31 January 2012 01:17, Tobias Diedrich wrote:
> > This patch adds basic swconfig support for ramips_esw:
> >
> > root@OpenWrt:/# swconfig dev rt305x show
> > Global attributes:
> > Port 0:
> > led: 5
> > pvid: 1
> > Port 1:
> > led: 5
> > pvid
On 31 January 2012 01:17, Tobias Diedrich wrote:
> This patch adds basic swconfig support for ramips_esw:
>
> root@OpenWrt:/# swconfig dev rt305x show
> Global attributes:
> Port 0:
> led: 5
> pvid: 1
> Port 1:
> led: 5
> pvid: 1
> Port 2:
> led: 5
> pvid:
This patch adds basic swconfig support for ramips_esw:
root@OpenWrt:/# swconfig dev rt305x show
Global attributes:
Port 0:
led: 5
pvid: 1
Port 1:
led: 5
pvid: 1
Port 2:
led: 5
pvid: 1
Port 3:
led: 5
pvid: 1
Port 4:
led: 5
