public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Daniel Ritz <daniel.ritz-ml@swissonline.ch>
Cc: Pavel Roskin <proski@gnu.org>, Marcus Better <marcus@better.se>,
	linux-pcmcia <linux-pcmcia@lists.infradead.org>,
	Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: pccards are not detected
Date: Thu, 3 Aug 2006 01:23:54 +0200	[thread overview]
Message-ID: <200608030123.54692.ak@suse.de> (raw)
In-Reply-To: <200608030102.48045.daniel.ritz-ml@swissonline.ch>


> ok, in other words:
> 2.6.16: end result: direct access; if direct doesn't work: pcibios
> 2.6.17: end result: pci bios (only direct if pcibios fails! )
> 2.6.17+patch: end result: direct access; if direct doesn't work: pcibios
> => net result is the same, but less code is executed, order is clear always.

Makes sense. PCI BIOS access is totally obsolete and should only be used
when everything else fails.


> btw. it's commit 92c05fc1a32e5ccef5e0e8201f32dcdab041524c
> ([PATCH] PCI: Give PCI config access initialization a defined ordering)
> that broke things on those laptops. cc'ing Andi...

It could have broken before where the order was essentially random.

-Andi

      reply	other threads:[~2006-08-02 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608021931.46058.daniel.ritz-ml@swissonline.ch>
     [not found] ` <200608022001.45140.daniel.ritz-ml@swissonline.ch>
     [not found]   ` <1154551499.7714.13.camel@dv>
2006-08-02 23:02     ` pccards are not detected Daniel Ritz
2006-08-02 23:23       ` Andi Kleen [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=200608030123.54692.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=daniel.ritz-ml@swissonline.ch \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=marcus@better.se \
    --cc=proski@gnu.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