> Vaio users: Please make sure that this doesn't oops.
> Others: Try using setpnp to change the current configuration.
> Unload and reload the parport drivers to check that they
> reinitialize with the updated resource information provided
> by the PnP BIOS driver.
Works here on the inspiron 5k. Parport detects its config correctly, even
after multiple loads/unloads, lspnp and setpnp seem to be doing the right
thing, parport detects the new parameters after changing them with setpnp.
Relevant dmesg output:
PnPBIOS: Found PnP BIOS installation structure at 0xc00f7230.
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xa610, dseg 0x400.
PnPBIOS: 17 nodes reported by PnP BIOS; 17 recorded by driver.
PnPBIOS: PNP0c02: 0xfff80000-0xffffffff was already reserved
PnPBIOS: PNP0c01: 0xe8000-0xfffff was already reserved
PnPBIOS: PNP0c01: 0x100000-0xbffffff was already reserved
PnPBIOS: PNP0c02: 0x4d0-0x4d1 has been reserved
PnPBIOS: PNP0c02: 0x1000-0x103f has been reserved
PnPBIOS: PNP0c02: 0x1040-0x104f has been reserved
SBF: ACPI BOOT descriptor is wrong length (39)
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
parport: PnP BIOS reports device PNPBIOS PNP0401 (node number 0x16) is
configured to use io 0x0378, io 0x0778, irq 7, dma 3
[and then after 'setpnp 16 dma 1']
parport: PnP BIOS reports device PNPBIOS PNP0401 (node number 0x16) is
configured to use io 0x0378, io 0x0778, irq 7, dma 1
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/