From: Andi Kleen <ak@suse.de>
To: Brian Hall <brihall@pcisys.net>
Cc: Greg KH <greg@kroah.com>,
shemminger@osdl.org, vsu@altlinux.ru, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: Help: DGE-560T not recognized by Linux
Date: Sun, 19 Feb 2006 18:13:58 +0100 [thread overview]
Message-ID: <200602191813.59928.ak@suse.de> (raw)
In-Reply-To: <20060219092007.e7eb6c1b.brihall@pcisys.net>
On Sunday 19 February 2006 17:20, Brian Hall wrote:
> On Sat, 18 Feb 2006 17:04:41 -0800
> Greg KH <greg@kroah.com> wrote:
> > On Sat, Feb 18, 2006 at 04:35:55PM -0800, Stephen Hemminger wrote:
> > > The problem can also be caused by buggy BIOS's that don't report
> > > proper values for mmconfig space. There is some code in mmconfig.c
> > > that tries to handle that. It might not handle what ever your
> > > system is reporting. Andi Kleen seems to be the last person
> > > involved and might be able to help.
> > >
> > > It would be useful to add some printk's to mmconfig to dump out the
> > > table after it discovers the table.
> >
> > Andi has a follow-on patch at:
> > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-03-pci/pci-give-pci-config-access-initialization-a-defined-ordering.patch
> > that should take care of these kinds of mmconfig issues by ordering
> > the pci config accessors properly.
> >
> > Can you test this patch out to see if it fixes this problem on your
> > machine?
>
> I applied this patch to 2.6.15-ck4 and 2.6.14-rc4, in both cases the
> compilation fails the same way:
The patch is for 2.6.16-rc3, not 2.6.15 or earlier prehistory. In general
we only care about the latest kernels on these lists.
-Andi
next prev parent reply other threads:[~2006-02-19 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 5:27 Help: DGE-560T not recognized by Linux 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 [this message]
2006-02-28 15:08 ` Brian Hall
2006-02-20 11:43 ` Willy Tarreau
2006-02-20 12:56 ` Sergey Vlasov
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=200602191813.59928.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=brihall@pcisys.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=vsu@altlinux.ru \
/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