All of lore.kernel.org
 help / color / mirror / Atom feed
From: 許恆嘉 <edward_hsu@realtek.com.tw>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: jeff@garzik.org, linux-kernel@vger.kernel.org, hiwu@realtek.com.tw
Subject: Re: [PATCH 2.6.19.2] r8169: support RTL8169SC/8110SC
Date: Wed, 07 Feb 2007 10:56:12 +0800	[thread overview]
Message-ID: <45C93FCC.4080609@realtek.com.tw> (raw)
In-Reply-To: <20070206213827.GA25119@electric-eye.fr.zoreil.com>



Francois Romieu 提到:

>edward_hsu@realtek.com.tw :
>[...]
>  
>
>>ANS_2:
>>So, do you think that it is a good idea to keep other vendos's PID and
>>DID in the part?
>>    
>>
>
>Yes.
>  
>

ANS_3:

OK! I will do it.

>[...]
>  
>
>>ANS_2:
>>
>>Sure! You are right. RTL8110SC, RTL8111B and RTL8101E have modest
>>differences, now. However, RTL8101E is a PCI-E fast ethernet controller.
>>I don't think is a good idea to merge its Linux driver into r8168.c or
>>r8169.c. RTL8110SC is the final version of Realtek PCI gigabit ethernet
>>controller. Moreover, due to the increasing popularity of PCI-E, Realtek
>>is going to design several generations of PCI-E ethernet controllers to
>>satisfy customer requests. I have discussed this issue with my hardware
>>colleagues. They believe that both MAC register layout and tx/rx
>>descriptor layout will be changed a lot in new PCI-E ICs. Actually, they
>>already did. Therefore, the hardwares of RTL8111B(PCI-E gigabit
>>ethernet) and RTL8101E(PCI-E fast ethernet) will have frequent and
>>drastic changes. So, I think that it's a good moment to separate their
>>Linux drivers, and r8169.c can become stable.
>>    
>>
>
>Well, code and facts will tell. :o)
>
>Since you asked for questions:
>
>- will the ~7k limit for the jumbo frames be fixed ? One can hardly call
>  it a feature.
>  
>
ANS_3:

Realtek does implement 7k limit for jumbo frames. I think there is no standard to require how large a jumbo frame should be implemented.


>- out of curiosity, did you try the current in-kernel r8169 driver with
>  a 8111B or a 8101E ?
>  
>
ANS_3:
Yes I did! I tried Linux kernel 2.6.19. It seems that r8169.c supports 
RTL8111B and RTL8101E.

>- is there any plan to open the programming manuals of the PCI-E chipsets ?
>  
>
ANS_3:
Realtek does not have the plan to open  the programming manuals of the 
PCI-E chipsets.

  reply	other threads:[~2007-02-07  2:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02  8:17 [PATCH 2.6.19.2] r8169: support RTL8169SC/8110SC 許恆嘉
2007-02-03  0:39 ` Francois Romieu
2007-02-05  3:47   ` 許恆嘉
2007-02-06  0:31     ` Francois Romieu
2007-02-06  2:44       ` 許恆嘉
2007-02-06 21:38         ` Francois Romieu
2007-02-07  2:56           ` 許恆嘉 [this message]
2007-02-07  3:25           ` 許恆嘉
2007-02-07 23:49             ` Francois Romieu
2007-02-08  1:18               ` 許恆嘉
  -- strict thread matches above, loose matches on Subject: below --
2007-02-02  7:08 許恆嘉
2007-02-02  8:03 ` Andrey Panin
2007-02-02  8:06 ` Andrew Morton

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=45C93FCC.4080609@realtek.com.tw \
    --to=edward_hsu@realtek.com.tw \
    --cc=hiwu@realtek.com.tw \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@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.