Well the first problem is to detect that this is an FC not an M.  This code
was written on the assumption (as I understand it) that it would only work
on the M, but I had a suspicion that it would also work on the FC but I 
could not get a kernel built to test it (my bad).  We obviously can not 
simply change the way registers are handled so that the FC works if that
stops the M working.  If we could tell the difference then we could set
up each properly.

Peter Lebbing asked me to compile his code with DEBUG turned on, (there
is a #DEFINE near the top of the code), and then to run the attached
program to see what it going on.  Could you try this code and then post
the results for Peter (and the rest of us) to see.

David


On Thursday 31 March 2011, Yeoh Chun Yeow wrote:
> It seems that ADM6996FC is different from ADM6996M. How to ensure the port
> get tagged? Is this by simply modifying Configuration register Bit 4?
> 
> On Thu, Mar 31, 2011 at 3:27 PM, Yeoh Chun Yeow 
<yeohchuny...@gmail.com>wrote:
> > On Wed, Mar 30, 2011 at 10:52 PM, Yeoh Chun Yeow 
<yeohchuny...@gmail.com>wrote:
> >> Dear all,
> >> 
> >> I am able to get the patch works by adding the following in mach-ubnt.c:
> >> 
> >> ar71xx_eth1_data.phy_mask = UBNT_RS_LAN_PHYMASK
> >> 
> >> However, there is two issues here:
> >> 1. RouterStation has two ports on ETH1. One port can only be activated
> >> after the other port is connected with cable. If this port is unplug,
> >> the port will not be activated even with cable connect.
> >> 2. VLAN separation is alright but VLAN tagging is not working. I am
> >> using the following:
> >> 
> >> config 'switch'
> >> 
> >>         option 'name' 'eth1'
> >>         option 'reset' '1'
> >>         option 'enable_vlan' '1'
> >>         option 'enable' '1'
> >> 
> >> config 'switch_vlan'
> >> 
> >>         option 'device' 'eth1'
> >>         option 'vlan' '1'
> >>         option 'vid' '1'
> >>         option 'ports' '0t 1t 5t'
> >> 
> >> Tag and No Tag on the port, I am still able to PING a host without VLAN
> >> tagging. It means that the VLAN tagging is not working.
> >> 
> >> Please advice. Thanks
> >> 
> >> Regards,
> >> Chun Yeow

Attachment: read-all-adm
Description: application/shellscript

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to