All of lore.kernel.org
 help / color / mirror / Atom feed
From: hayeswang <hayeswang@realtek.com>
To: 'Francois Romieu' <romieu@fr.zoreil.com>,
	'Anand Raj Manickam' <anandrm@gmail.com>
Cc: <netdev@vger.kernel.org>, 'Ivan Vecera' <ivecera@redhat.com>
Subject: RE: Realtek r8168C / r8169 driver VLAN TAG stripping
Date: Mon, 31 Jan 2011 13:45:48 +0800	[thread overview]
Message-ID: <BFBA3A0B2A4B4E8B8798977086BFC4C9@realtek.com.tw> (raw)
In-Reply-To: <20110128120624.GA8100@electric-eye.fr.zoreil.com>


> 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


  parent reply	other threads:[~2011-01-31  5:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 14:40 Realtek r8168C / r8169 driver VLAN TAG stripping Anand Raj Manickam
2011-01-13 15:09 ` Anand Raj Manickam
2011-01-16 19:20   ` Francois Romieu
     [not found]     ` <AANLkTi=uNKMj_gs_bKRQ1tQa0TMwdnyrtVcR5JPNpmJv@mail.gmail.com>
2011-01-17  7:34       ` Anand Raj Manickam
2011-01-18  1:21         ` Francois Romieu
2011-01-27 10:35           ` Anand Raj Manickam
2011-01-27 15:07             ` Francois Romieu
2011-01-27 15:31               ` Anand Raj Manickam
2011-01-27 16:50                 ` Francois Romieu
2011-01-28  1:40                   ` Anand Raj Manickam
2011-01-28 12:06                     ` Francois Romieu
2011-01-28 12:16                       ` Anand Raj Manickam
2011-01-31  5:45                       ` hayeswang [this message]
2011-01-31 13:14                       ` Ivan Vecera
2011-02-01 10:12                         ` Francois Romieu
2011-02-01 10:38                           ` Anand Raj Manickam
2011-02-09  9:51                             ` hayeswang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BFBA3A0B2A4B4E8B8798977086BFC4C9@realtek.com.tw \
    --to=hayeswang@realtek.com \
    --cc=anandrm@gmail.com \
    --cc=ivecera@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.