public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Kai Ruhnau <kai@tragetaschen.dyndns.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	Simon Arlott <simon@fire.lp0.eu>,
	Francois Romieu <romieu@fr.zoreil.com>,
	LKML <linux-kernel@vger.kernel.org>,
	gregkh@suse.de, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: Bogus PCI vendor ID
Date: Fri, 30 Nov 2007 21:14:14 -0500	[thread overview]
Message-ID: <20071201021414.GA4375@fattire.cabal.ca> (raw)
In-Reply-To: <474DD274.5060909@tragetaschen.dyndns.org>

On Wed, Nov 28, 2007 at 09:41:24PM +0100, Kai Ruhnau wrote:
> Kyle McMartin wrote:
> > On Sun, Nov 25, 2007 at 01:36:19PM +0100, Kai Ruhnau wrote:
> >   
> >> If this is the same like the kernel option 'pci=conf1', that fixes the
> >> vendor IDs.
> >>     
> >
> > Same effect. Ubuntu and many other distros are shipping kernels with
> > MMCONFIG off by default for reasons like this. Check to see if you have
> > an updated BIOS from your motherboard manufacturer?
> >   
> 
> No, nothing available there. (OEM board, running fine under Vista, I
> don't expect to get support there...)
> 

Ah, that's interesting, as Vista is supposed to require working MMCONFIG
support to be certified.

regards,
	Kyle

      reply	other threads:[~2007-12-01  2:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-17 15:59 Bogus PCI vendor ID Kai Ruhnau
2007-11-17 18:40 ` Francois Romieu
2007-11-19 12:22   ` Simon Arlott
2007-11-19 17:27     ` Stephen Hemminger
2007-11-25  4:28       ` Andrew Morton
2007-11-25 12:36         ` Kai Ruhnau
2007-11-26 16:53           ` Kyle McMartin
2007-11-28 20:41             ` Kai Ruhnau
2007-12-01  2:14               ` Kyle McMartin [this message]

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=20071201021414.GA4375@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=kai@tragetaschen.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=romieu@fr.zoreil.com \
    --cc=shemminger@linux-foundation.org \
    --cc=simon@fire.lp0.eu \
    /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