pccards are not detected

[Pavel Roskin]

On Wed, 2006-08-02 at 20:01 +0200, Daniel Ritz wrote:
> On Wednesday 02 August 2006 19.42, Pavel Roskin wrote:
> > It depends.  For some custom systems, BIOS may be a lifesaver.  Let's
> > not change the whole logic of the PCI detection because of one broken
> > BIOS.
> 
> errm. 2.6.16 automatically uses direct access. if first shows the PCI BIOS
> line, then the direct access line in dmesg. pci_raw_ops is first set to
> PCI_BIOS to be overwritten with direct access immediatley after that.
> 
> eg. from a 2.6.16.20 on a buggy box:
> 	PCI: PCI BIOS revision 2.10 entry at 0xfb9a0, last bus=0
> 	PCI: Using configuration type 1
> cardbus would be bus 1-4. 2.6.17 breaks here...

If it's a laptop and CardBus is integrated, it's a BIOS bug.  BIOS
should know about integrated hardware.  No excuses.

> > The standard solution for such problems is to add a "quirk" to
> > drivers/pci/quirks.c or arch/i386/kernel/quirks.c

> no. it is a clear regression and the patch in fact just restores the old
> behaviour with the exception that the ordering is more clear now than it
> was before...

My intention was just to remind you about the quirks.

> 2.6.16: pci bios comes first, is overriden by direct access
> 2.6.17: pci bios comes first. direct access is never used if pci bios probe "worked"
> 2.6.17+patch: pci direct access probed first, if it fails pci bios is used.

The way you put it above, it sounds like a major change.  But I missed
the actual patch.  Maybe it just reorders a few printk()s compared to
2.6.16, I don't know.

I still believe that adding quirk would be a good solution, in
particular because it would work even if direct PCI probing is disabled.
And then you can reorder the probing as much as you want.

-- 
Regards,
Pavel Roskin