From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: x86@kernel.org, linux-pci@vger.kernel.org, stable@kernel.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH v2] x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE
Date: Tue, 04 Oct 2011 16:37:27 +0200 [thread overview]
Message-ID: <1317739047.4892.24.camel@mattotaupa> (raw)
In-Reply-To: <CAErSpo6KopVRio-84uoUf1on+VQ6zuduypztXnUwcq_8iNtbjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]
Am Dienstag, den 27.09.2011, 08:09 -0600 schrieb Bjorn Helgaas:
> On Tue, Sep 27, 2011 at 3:39 AM, Paul Menzel wrote:
> > Am Dienstag, den 20.09.2011, 10:39 -0600 schrieb Bjorn Helgaas:
> >> On Tue, Sep 20, 2011 at 4:20 AM, Paul Menzel wrote:
> >> > ...
> >> >
> >> > Using coreboot [1] with this board the problem does not exist but this quirk also does not affect it either. To be safe though the check is tightened to only take effect when the BIOS from American Megatrends is used.
> >> >
> >> > 15:13 < ruik> but coreboot does not need that
> >> > 15:13 < ruik> because i have there only one root bus
> >> > 15:13 < ruik> the audio is behind a bridge
> >>
> >> I'd like to know more about this coreboot situation. Would it be
> >> possible to get a dmesg log from the system with coreboot? I'd like
> >> to see how coreboot configures this device differently.
> >
> > I had attached that to the Bugzilla report #30552 [2], but this is down
> > at the moment. I saw that you got the output from someone on #coreboot
> > though.
> >
> >> > CC: stable@kernel.org (≥ 2.6.34)
> >> > CC: Bjorn Helgaas <bhelgaas@google.com>
> >> > CC: Thomas Gleixner <tglx@linutronix.de>
> >> > CC: Ingo Molnar <mingo@redhat.com>
> >> > CC: H. Peter Anvin <hpa@zytor.com>
> >> > CC: x86@kernel.org
> >> > CC: Jesse Barnes <jbarnes@virtuousgeek.org>
> >> > Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
> >>
> >> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> >>
> >> This is fine with me. I don't think it's the final solution, but I
> >> think it's worth doing for now.
> >
> > Thank you. I could not see this in Linus’ tree [3] yet. Jesse, could you
> > pick that up as you have done for the other commit? (Where is your
> > (temporary) tree located?)
>
> Jesse's on vacation right now.
It looks like Jesse is back from vacation. Jesse, I hope you could enjoy
it and I am sorry for bothering you right after you have been back.
Is it possible to get this patch in for Linux 3.1?
> I'm in the middle of setting up a temporary tree for the interim.
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-04 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 10:20 Paul Menzel
2011-09-20 16:39 ` Bjorn Helgaas
2011-09-27 9:39 ` Paul Menzel
2011-09-27 14:09 ` Bjorn Helgaas
2011-10-04 14:37 ` Paul Menzel [this message]
2011-10-04 15:03 ` Bjorn Helgaas
2011-10-06 15:14 ` Jesse Barnes
2011-10-06 22:14 ` [PATCH v3] " Paul Menzel
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=1317739047.4892.24.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®