From: Sergey Vlasov <vsu@altlinux.ru>
To: Willy Tarreau <willy@w.ods.org>
Cc: Greg KH <greg@kroah.com>, Stephen Hemminger <shemminger@osdl.org>,
Brian Hall <brihall@pcisys.net>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Help: DGE-560T not recognized by Linux
Date: Mon, 20 Feb 2006 15:56:38 +0300 [thread overview]
Message-ID: <20060220125638.GA26440@master.mivlgu.local> (raw)
In-Reply-To: <20060220114341.GA7710@w.ods.org>
[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]
On Mon, Feb 20, 2006 at 12:43:41PM +0100, Willy Tarreau wrote:
> Today, I had the *exact* same problem on one server equipped with the same
> card. I tried the patch above which did not change anything. However, I
> finally fixed it by simply enabling ACPI. Then it always works with and
> without the patch above. I could not test marvell's driver because it does
> not build on 2.6.16-rc4, but strangely my previous kernel on this machine
> was a 2.6.12-rc4-mm2 patched with marvell's driver and with ACPI disabled.
>
> So it seems that marvell's driver on 2.6.12 was able to access config space
> even without ACPI while sky2 on 2.6.16-rc4 cannot. I have no idea why,
> unfortunately.
Apparently Marvell's driver accesses PCIE configuration registers through
I/O ports specific to their hardware:
/*
* Macro PCI_C()
*
* Use this macro to access PCI config register from the I/O space.
*
* para:
* pAC Pointer to adapter context
* Addr PCI configuration register to access.
* Values: PCI_VENDOR_ID ... PCI_VPD_ADR_REG,
*
* usage SK_IN16(IoC, PCI_C(pAC, PCI_VENDOR_ID), pVal);
*/
#define PCI_C(p, Addr) \
(((CHIP_ID_YUKON_2(p)) ? Y2_CFG_SPC : B7_CFG_SPC) + (Addr))
...
/* clear any PEX errors */
SK_OUT32(IoC, PCI_C(pAC, PEX_UNC_ERR_STAT), 0xffffffffUL);
SK_IN16(IoC, PCI_C(pAC, PEX_LNK_STAT), &Word);
pAC->GIni.GIPexWidth = (SK_U8)((Word & PEX_LS_LINK_WI_MSK) >> 4);
...
SK_OUT8(IoC, B2_TST_CTRL1, TST_CFG_WRITE_ON);
SK_OUT16(IoC, PCI_C(pAC, PEX_DEV_CTRL), Word);
SK_OUT8(IoC, B2_TST_CTRL1, TST_CFG_WRITE_OFF);
...
/* clear the interrupt */
SK_OUT32(IoC, B2_TST_CTRL1, TST_CFG_WRITE_ON);
SK_OUT32(IoC, PCI_C(pAC, PEX_UNC_ERR_STAT), 0xffffffffUL);
SK_OUT32(IoC, B2_TST_CTRL1, TST_CFG_WRITE_OFF);
But sky2 uses standard pci_read_config_*, pci_write_config_* functions,
which require working MMCONFIG access. Maybe sky2 should be changed to
use I/O space for access to PCIE-specific configuration registers.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-20 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 5:27 Brian Hall
2006-02-18 5:40 ` Randy.Dunlap
2006-02-18 6:24 ` Andrew Morton
2006-02-18 7:36 ` Brian Hall
2006-02-18 7:48 ` Andrew Morton
2006-02-18 15:54 ` Edgar Hucek
2006-02-18 17:01 ` Brian Hall
2006-02-18 19:29 ` Sergey Vlasov
2006-02-19 0:35 ` Stephen Hemminger
2006-02-19 1:04 ` Greg KH
2006-02-19 16:20 ` Brian Hall
2006-02-19 17:13 ` Andi Kleen
2006-02-28 15:08 ` Brian Hall
2006-02-20 11:43 ` Willy Tarreau
2006-02-20 12:56 ` Sergey Vlasov [this message]
2006-02-22 3:51 ` Brian Hall
2006-02-22 19:51 ` Stephen Hemminger
2006-02-19 2:55 ` Brian Hall
2006-02-19 7:41 ` jerome lacoste
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=20060220125638.GA26440@master.mivlgu.local \
--to=vsu@altlinux.ru \
--cc=akpm@osdl.org \
--cc=brihall@pcisys.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=willy@w.ods.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
Powered by JetHome