Roberto Jung Drebes <[EMAIL PROTECTED]> writes:
> But the problem is that the 'default' configuration of the port is 0x3e8,
> 0x100, IRQ 4, but 0x100 is used by motherboard resources (ACPI
> resources) and this mobo configuration cannot be changed. So, I think
> that when I outb at 0x100 I'm actually outbing at the mobo, not the SMC.
Findchip doesn't care about the current configuration of the chip, it only
tries to detect it. It doesn't try to detect it in the SIR or FIR I/O
space, but in the config space. If you cannot find the chip in config
space, then your lost (at least if you cannot hack findchip to detect your
chip). If you can detect the chip, but it uses the wrong values, then you
must reconfig it using isapnp or some other way (smc-tools). The new driver
will use the BIOS settings, so if they are wrong then you must solve it
some other way.
It would be possible to rename findchip to irdachip and make it possible to
change the config in addition to detect it. But most laptops follow the ISA
PnP spec, so there's really no need to duplicate this stuff in findchip.
I'm in dialog with SMsC to make them help us out with getting proper
support for their chipsets. Lets cross our fingers!
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
