[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BFBA3A0B2A4B4E8B8798977086BFC4C9@realtek.com.tw>
Date: Mon, 31 Jan 2011 13:45:48 +0800
From: hayeswang <hayeswang@...ltek.com>
To: 'Francois Romieu' <romieu@...zoreil.com>,
'Anand Raj Manickam' <anandrm@...il.com>
CC: <netdev@...r.kernel.org>, 'Ivan Vecera' <ivecera@...hat.com>
Subject: RE: Realtek r8168C / r8169 driver VLAN TAG stripping
> Reading my rev1.0 8168c datasheet from may 2007, when there
> is no tx offload, no checksumming, the tx descriptor layout
> should be the same as the perennial 8169 tx descriptor layout.
>
> Either (1) the VLAN registers and descriptor layout is
> different for this chipset or (2) something prevents the
> register / descriptor write (read ?) to be completely
> effective or (3) there is something beyond the 8168 or
> (4) there is a 8168 hardware bug.
>
> 1 : Hayes may answer. You can give Realtek's own driver a try btw.
> 2 : Seen before. It could be a software or a (non-8168) hardware one.
> I have no idea if your hardware setup includes a single card with
> four ports or four independent cards with their own 8168 or worse.
> 3 : See the hardware setup part of (2).
> 4 : I don't hope so. Hayes may answer as well.
>
I find nothing wrong for the source code of kernel. I think it should work. Only
the tx descriptor need to be set for the tx. For the receiving, the register
0xe0 (CPlusCmd) bit 6 (RxVlan) should be set. That is all. And I don't get any
information about hardware bug, so I really don't know what's wrong. I will
check it after the vacation of Chinese New Year.
Best Regards,
Hayes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists