From: Yinghai Lu <yinghai@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Venkatesh Pallipadi <venki@google.com>,
Prarit Bhargava <prarit@redhat.com>,
fredlwm@gmail.com, Simon Arlott <simon@fire.lp0.eu>,
x86@kernel.org, Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, Marc Jones <marcj303@gmail.com>,
Jordan Crouse <jcrouse@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86, HPET: mark HPET PCI BARs as IORESOURCE_PCI_FIXED
Date: Fri, 24 Sep 2010 17:12:59 -0700 [thread overview]
Message-ID: <4C9D3E8B.7090000@kernel.org> (raw)
In-Reply-To: <4C9D3D79.9060908@zytor.com>
On 09/24/2010 05:08 PM, H. Peter Anvin wrote:
> On 09/24/2010 04:59 PM, Yinghai Lu wrote:
>> On Fri, Sep 24, 2010 at 4:06 PM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>>> Sorry Yinghai, I forgot to copy you on the initial post. Any
>>> comments on this? If not, we should try to get it into linux-next
>>> soon.
>>
>> should be good.
>>
>> only one thing, that will punish all other vendors... and run that
>> quirk for every pci device.
>>
>> please check if you can have
>> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATI, PCI_ANY_ID, mark_pci_hpet_fixed);
>>
>> AND _AMD maybe, if AMD dump _ATI brand later.
>>
>
> No, because the problem is known to happen on multiple vendors.
>
Do you have URL to them?
INTEL ?
ServerWorks?
Via?
Yinghai
next prev parent reply other threads:[~2010-09-25 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 23:30 [PATCH] x86, HPET: mark HPET PCI BARs as IORESOURCE_PCI_FIXED Bjorn Helgaas
2010-09-23 23:32 ` Bjorn Helgaas
2010-09-24 23:06 ` Bjorn Helgaas
2010-09-24 23:59 ` Yinghai Lu
2010-09-25 0:08 ` H. Peter Anvin
2010-09-25 0:12 ` Yinghai Lu [this message]
2010-09-25 0:25 ` H. Peter Anvin
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=4C9D3E8B.7090000@kernel.org \
--to=yinghai@kernel.org \
--cc=bjorn.helgaas@hp.com \
--cc=clemens@ladisch.de \
--cc=fredlwm@gmail.com \
--cc=hpa@zytor.com \
--cc=jcrouse@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcj303@gmail.com \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=simon@fire.lp0.eu \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
--cc=x86@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