From: Jean Delvare <jdelvare@suse.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Vincent Steenhoute <vsteenhoute@novell.com>,
Martin Michlmayr <tbm@cyrius.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
Ivan Vecera <ivecera@redhat.com>,
Edward Hsu <edward_hsu@realtek.com.tw>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] r8169: allow true forced mode setting
Date: Sat, 16 May 2009 14:50:38 +0200 [thread overview]
Message-ID: <200905161450.38281.jdelvare@suse.de> (raw)
In-Reply-To: <20090514214605.GB6374@electric-eye.fr.zoreil.com>
Hi François,
Le jeudi 14 mai 2009, Francois Romieu a écrit :
> Due to mostly historic reasons, including a lack of reliability
> of the link handling (especially with the older 8169), the
> current r8169 driver emulates forced mode setting by limiting
> the advertised modes.
>
> With this change the driver allows real 10/100 forced mode
> settings on the 8169 and 8101/8102.
>
> Original idea by Vincent Steenhoute. The RTL_GIGA_MAC_VER_03
> tweak was extracted from Realtek's v6.009.00 driver.
If I read the code correctly, Realtek's driver (v6.010.00) only
applies the quirk for RTL8169S and RTL8110S chips (what I have) and
not the original RTL8169. Your code applies the quirk to all 3
chips. Is this on purpose? Or am I missing something?
> (...)
> + if (tp->mac_version <= RTL_GIGA_MAC_VER_03) {
> + if ((speed == SPEED_100) && (autoneg != AUTONEG_ENABLE)) {
> + mdio_write(ioaddr, 0x17, 0x2138);
> + mdio_write(ioaddr, 0x0e, 0x0260);
> + } else {
> + mdio_write(ioaddr, 0x17, 0x2108);
> + mdio_write(ioaddr, 0x0e, 0x0000);
> + }
> + }
> +
> return 0;
> }
Thanks,
--
Jean Delvare
Suse L3
next prev parent reply other threads:[~2009-05-16 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 21:46 [PATCH 2/2] r8169: allow true forced mode setting Francois Romieu
2009-05-16 12:50 ` Jean Delvare [this message]
2009-05-16 19:57 ` Xose Vazquez Perez
2009-05-17 10:34 ` Francois Romieu
2009-05-19 2:25 ` David Miller
2009-05-19 20:46 ` Francois Romieu
2009-05-19 21:32 ` David Miller
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=200905161450.38281.jdelvare@suse.de \
--to=jdelvare@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edward_hsu@realtek.com.tw \
--cc=ivecera@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=tbm@cyrius.com \
--cc=vsteenhoute@novell.com \
--cc=xose.vazquez@gmail.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;
as well as URLs for NNTP newsgroup(s).