Brian de Alwis wrote:
> Comparing the ASLs, my ACPI descriptions are an older revision,
> listed as Revision=0x2030 as compared to your Revision=0x2110.

I just upgraded my BIOS: I had 0x1070 earlier.

> Here's the diffs between my dmesg and your own.  Have you tried
> a kernel with PCI_ADDR_FIXUP and PCI_BUS_FIXUP?

With both I get:

ppb5 at pci0 dev 30 function 0: Intel 82801BAM Hub-PCI Bridge (rev. 0xe2)
pci6 at ppb5 bus 6
pci6: i/o space, memory space enabled
cbb0 at pci6 dev 0 function 0: Texas Instruments PCI1510 PCI-CardBus
Bridge (rev
. 0x00)
cbb0: interrupting at ioapic0 pin 16 (irq 11)
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 7
pcmcia0 at cardslot0

which looks much better. But I still have the same issues as before:

wi0 at pcmcia0 function 0: <Wireless, LAN Adapter, Version 01.02, >
wi0:wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: init failed
wi0: failed to attach controller

or, with a CF-to-PCMCIA adapter and a CF memory stick:

wdc2 at pcmcia0 function 0: <TRANSCEND, TS512MCF80, >
wdc2: i/o mapped mode
atabus2 at wdc2 channel 0
...but I never get my additional drive.


Now back to my dmesg, and inspired by http://ibm-acpi.sf.net/ I played a
bit with an ACPI driver, starting from sony_acpi.c:
ibm0 at acpi0 (IBM0068): IBM ACPI
(according to sony(4) the name is too generic)

the hotkeys are detected bluntly:
ibm0: hotkey pressed is 0x7000
etc (that's the wireless switch)

and I get these 2 sysctl:
hw.ibm0.wan = 4
hw.ibm0.bdc = 0
but the sysctl code from sony_acpi.c can apparently hardly fit here.

you can have a look at the code there:
http://people.defora.org/~khorben/projects/netbsd/kern/acpi/t60/ibm_acpi.c

Any suggestion welcome to help this become actually useful.

-- 
khorben