From: Andrew Morton <akpm@osdl.org>
To: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
Cc: bzolnier@gmail.com, drab@kepler.fjfi.cvut.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: APIC/LAPIC hanging problems on nForce2 system.
Date: Thu, 6 Jan 2005 15:46:50 -0800 [thread overview]
Message-ID: <20050106154650.33c3b11c.akpm@osdl.org> (raw)
In-Reply-To: <41DD537B.9030304@gmx.de>
"Prakash K. Cheemplavam" <prakashkc@gmx.de> wrote:
>
> This patch applies the Nforce2 C1 halt disconnect fix, no matter if
> disconnect is enabled of not. I don't know whether checking the whole
> affected byte is necessary or the nibble would be enough (I am no Nvidia
> engineer).
The patch doesn't apply to the current tree. Here's what we currently have:
static void __init pci_fixup_nforce2(struct pci_dev *dev)
{
u32 val, fixed_val;
u8 rev;
pci_read_config_byte(dev, PCI_REVISION_ID, &rev);
/*
* Chip Old value New value
* C17 0x1F0FFF01 0x1F01FF01
* C18D 0x9F0FFF01 0x9F01FF01
*
* Northbridge chip version may be determined by
* reading the PCI revision ID (0xC1 or greater is C18D).
*/
fixed_val = rev < 0xC1 ? 0x1F01FF01 : 0x9F01FF01;
pci_read_config_dword(dev, 0x6c, &val);
/*
* Apply fixup only if C1 Halt Disconnect is enabled
* (bit28) because it is not supported on some boards.
*/
if ((val & (1 << 28)) && val != fixed_val) {
printk(KERN_WARNING "PCI: nForce2 C1 Halt Disconnect fixup\n");
pci_write_config_dword(dev, 0x6c, fixed_val);
}
}
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE2, pci_fixup_nforce2);
If you think this still needs fixing, please submit a new patch. I think
we'd need to see a better explanation of the rationale for the change as
well, please. What it does, why, how, etc.
next prev parent reply other threads:[~2005-01-06 23:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 15:28 Martin Drab
2005-01-05 16:05 ` Zwane Mwaikambo
2005-01-05 16:56 ` Martin Drab
2005-01-05 16:50 ` Prakash K. Cheemplavam
2005-01-05 17:06 ` Martin Drab
2005-01-05 17:17 ` Prakash K. Cheemplavam
2005-01-05 17:22 ` Martin Drab
2005-01-05 17:26 ` Prakash K. Cheemplavam
2005-01-05 17:30 ` Martin Drab
2005-01-06 0:14 ` Martin Drab
2005-01-06 9:03 ` Prakash K. Cheemplavam
2005-01-06 13:52 ` Bartlomiej Zolnierkiewicz
2005-01-06 15:04 ` [PATCH] " Prakash K. Cheemplavam
2005-01-06 23:46 ` Andrew Morton [this message]
2005-01-07 0:28 ` Prakash K. Cheemplavam
2005-01-07 0:49 ` Andrew Morton
2005-01-07 11:47 ` Martin Drab
2005-01-07 13:53 ` Prakash K. Cheemplavam
2005-01-07 15:34 ` Bartlomiej Zolnierkiewicz
2005-01-06 14:18 ` Martin Drab
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=20050106154650.33c3b11c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bzolnier@gmail.com \
--cc=drab@kepler.fjfi.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=prakashkc@gmx.de \
/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
all inboxes | Powered by JetHome®