public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Abit F-190HD Onboard rlt8169 Ethernet Controller
Date: Mon, 29 Oct 2007 06:15:32 +0000	[thread overview]
Message-ID: <20071029061532.5d10dfc6@snowcone> (raw)

The Abit Fatal1ty F-190HD motherboard has a Realtek rlt8169 gigabit
ethernet controller onboard. It shows up in lspci as:

02:00.0 Ethernet controller: Unknown device 0001:8168 (rev 01)
        Subsystem: ABIT Computer Corp. Unknown device 2410
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at ee00 [size=256]
        Memory at fdeff000 (64-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at fdd00000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Vital Product Data
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queue=0/1 Enable-
        Capabilities: [60] Express Endpoint, MSI 00
        Capabilities: [84] Vendor Specific Information
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [12c] Virtual Channel
        Capabilities: [148] Device Serial Number 81-ec-10-00-00-00-4f-04
        Capabilities: [154] Power Budgeting

It is not recognised by 2.6.24-rc1. I'm guessing it's because the
vendor ID is 0001 rather than something sensible. I patched the kernel
as follows:

--- drivers/net/r8169.c.orig	2007-10-29 05:37:02.000000000 +0000
+++ drivers/net/r8169.c	2007-10-29 05:54:30.000000000 +0000
@@ -165,6 +165,7 @@
 	{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK,	0x8136), 0, 0, RTL_CFG_2 },
 	{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK,	0x8167), 0, 0, RTL_CFG_0 },
 	{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK,	0x8168), 0, 0, RTL_CFG_1 },
+	{ PCI_DEVICE(PCI_ANY_ID,		0x8168), 0, 0, RTL_CFG_2 },
 	{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK,	0x8169), 0, 0, RTL_CFG_0 },
 	{ PCI_DEVICE(PCI_VENDOR_ID_DLINK,	0x4300), 0, 0, RTL_CFG_0 },
 	{ PCI_DEVICE(PCI_VENDOR_ID_AT,		0xc107), 0, 0, RTL_CFG_0 },

This was enough to get the device recognised and operational. (Only
RTL_CFG_2 works, I have no idea why.) Is this the correct approach?

-- 
Ciaran McCreesh

             reply	other threads:[~2007-10-29  6:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29  6:15 Ciaran McCreesh [this message]
2007-10-29  8:33 ` Abit F-190HD Onboard rlt8169 Ethernet Controller Alan Cox
2007-10-29  8:42   ` Jeff Garzik
2007-10-29 12:00     ` Francois Romieu
2007-10-30  0:27       ` Ciaran McCreesh
2007-10-30 22:59         ` Francois Romieu
2007-10-30 23:49           ` Ciaran McCreesh
2007-10-29  8:49   ` Ciaran McCreesh
2007-11-01 16:17   ` Josh Logan
2007-11-01 21:53     ` Francois Romieu
2007-11-02  0:05       ` Ciaran McCreesh
2007-11-07  5:21       ` Josh Logan

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=20071029061532.5d10dfc6@snowcone \
    --to=ciaran.mccreesh@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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