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: Thu, 08 Feb 2007 09:18:45 +0800 [thread overview]
Message-ID: <45CA7A75.1060704@realtek.com.tw> (raw)
In-Reply-To: <20070207234943.GA4445@electric-eye.fr.zoreil.com>
Francois Romieu 提到:
>許恆嘉 <edward_hsu@realtek.com.tw> :
>
>
>>Dear Francois:
>>
>>I think I didn't make it clear about the programming manuals for PCI-E ICs.
>>
>>Due to several legal issues, Realtek won't put the programming guide on
>>its website. However, Realtek does offer the programming guide if the
>>customers need it. If you want to have a copy of it, please contact
>>Realtek FAE<ryankao@realtek.com.tw>.
>>
>>
>
>Does it mean that the documentation is NDAed ?
>
>
ANS:
No, you don't have to sign anything.
>On an unrelated topic, revision 8.001.00 of your 8168 driver includes
>a workaround for an rx fifo overflow issue. Is it an event which can
>happen at any time, repeteadly if some rare conditions are met or is
>it enough to whack the device once for all when the problem happens ?
>
>
ANS:
No, it seldom happens. It does happen in a few rare conditions. When
this event happens, the nic works improperly and I do the patch to
rescue the device.
next prev parent reply other threads:[~2007-02-08 1:18 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 ` 許恆嘉
2007-02-07 3:25 ` 許恆嘉
2007-02-07 23:49 ` Francois Romieu
2007-02-08 1:18 ` 許恆嘉 [this message]
-- 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=45CA7A75.1060704@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox