>Number:         27316
>Category:       kern
>Synopsis:       for CardBus, /dev/pciX device nodes don't properly configure.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 22 08:47:02 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Paul Shupak
>Release:        NetBSD 2.99.10
>Organization:
	
>Environment:
	
	
System: NetBSD cobalt 2.99.10 NetBSD 2.99.10 (COBALT-$Revision: 1.4 $) #742: Tue Oct 19 06:17:37 PDT 2004 root@svcs:/sys/arch/i386/compile/COBALT i386
Architecture: i386
Machine: i386
>Description:
	When PCI buses are attached behind CardBus bridges, the device nodes
corresponding to /dev/pciX do not work as arguments to "pcictl" in the first
argument position.  In fact they are "not configured" even if recognized at
boot by either the ACPI or PCI BIOSs.
	
>How-To-Repeat:
	Plug a card into a CardBus slot.  Notice that "lspci" can `see'
the device if enabled;  Also "pcictl pci0 list -d X" will `see' it, but
"pcictl pciX list" will not.

	Ex.:

	% pcictl pci4 list
	pcictl: /dev/pci4: Device not configured
	% pcictl pci0 list -b 4
	004:00:0: Atheros Communications, Inc. AR5211 Wireless LAN (ethernet network, revision 0x01)
	% lspci
	...
	04:00.0 Ethernet controller: Atheros Communications, Inc. AR5211 802.11ab NIC (rev 01)
	

>Fix:
	Work around is use the "-b" argument to "pcictl" or use "lspci" to
view CardBus attachments (which in this case, are reported by the ACPI BIOS
at boot time).
	Probably, the PCI bus nodes need to be attached when a CardBus device
is attached (r.e. inserted) and possibly detached when the dependent device
is removed.
	
>Release-Note:
>Audit-Trail:
>Unformatted: