All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>,
	linux-pci@atrey.karlin.mff.cuni.cz,
	Yinghai Lu <yinghai.lu@amd.com>
Subject: Re: linux-2.6.19-rc2 PCI problem
Date: Sat, 28 Oct 2006 09:45:35 -0600	[thread overview]
Message-ID: <20061028154534.GR5591@parisc-linux.org> (raw)
In-Reply-To: <b6a2187b0610280324s66b06067od4691fa9f79420a7@mail.gmail.com>

On Sat, Oct 28, 2006 at 06:24:58PM +0800, Jeff Chua wrote:
> Up to 2.6.18, I was using "PCI access mode (Any)" and had no problem,
> but from  2.6.19-rc1 onwards, setting to "ANY" doesn't seem to work
> anymore.
> 
> I've just tested all 2.6.19-rc[123] and all are working with the
> "BIOS" setting, but not "ANY".

BIOS isn't a great option to choose ... how does Direct work out for
you?

I suspect you're having problems with the MMConfig method; confirming
that would be a good step towards debugging the problem.

  reply	other threads:[~2006-10-28 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23 15:24 linux-2.6.19-rc2 tg3 problem Jeff Chua
2006-10-23 21:19 ` David Miller
2006-10-25  1:30 ` Adrian Bunk
2006-10-26  0:54   ` Jeff Chua
2006-10-26 15:24     ` Adrian Bunk
2006-10-27 13:49       ` Jeff Chua
2006-10-27 20:31         ` Adrian Bunk
2006-10-28  1:05           ` Jeff Chua
2006-10-28  3:20             ` linux-2.6.19-rc2 PCI problem Adrian Bunk
2006-10-28 10:24               ` Jeff Chua
2006-10-28 15:45                 ` Matthew Wilcox [this message]
2006-10-29  1:20                   ` Jeff Chua
2006-10-28  8:23             ` linux-2.6.19-rc2 tg3 problem Yinghai Lu

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=20061028154534.GR5591@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=yinghai.lu@amd.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.