vlan. Now, when I ping from a remote pc which also has vlan enabled interface,
I don't see vlan tags in the frames. Same issue if I ping the remote PC. Basically,
I don't see vlan tag in tx/rx directions.
/kmk
On 3/13/07, Muthu Kumar <km7kumar@xxxxxxxxx> wrote:
Ben,
Thanks for your response. The mac data sheet says, when 0x8100 is written to the
van1_tag register, the mac compares 13th & 14th bytes of incoming frame and, if it
finds a match, it sets vlan1 bit in rx status register. However, this particular status
bit is not actually exposed to driver access. The documentation could be wrong.
Other than the above, no behaviour changes. In this case, I just simply ensure
that the driver/chip can handle MTU + 4 bytes? No need to enable NETIF_VLAN_HW_TX/RX
and related callbacks?
By the way, I don't see my postings @ http://ns2.lanforge.com/pipermail/vlan/2007-March/thread.html .
Thanks
/kmkOn 3/13/07, Muthu Kumar < km7kumar@xxxxxxxxx> wrote:'m trying to enable VLAN in my eth driver. The eth mac supports
vlan processing and has a register (vlantag1) that should be written
with 0x8100 to enable VLAN processing. Other than this, the mac does
not have any other vlan related registers or anything else. It does not give
any indication during rx if VLAN pkts received.
How do I enable VLAN in my driver for such a MAC? I'm basically
confused with all the callbacks such as vlan_rx_register etc most
drivers support.
Currently, in my driver I've enabled the features NETIF_VLAN_HW_TX/RX
and providing the above callbacks. But I'm not sure whether these flags
are applicable to my driver.
what else I need to do? I'm kinda stuck here. Any help would be highly
appreciated.
thx
/kmk
_______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxxxxx http://www.candelatech.com/mailman/listinfo/vlan
