I can confirm the same story is valid for my Compaq Armada M700.
just by two bits,
Alexander
Roberto Jung Drebes <[EMAIL PROTECTED]> writes:
> On Tue, 8 Feb 2000, Alexy V. Khrabrov wrote:
>
> >
> >
> > Dag, even with irda-utils-0.9.10 and 2.2.15pre5,
> > findchip cannot see anything on my Dell Inspiron
> > 7000. Windows, however, sees the SMC_IRCC in FIR
> > BIOS mode.
> >
> > I wonder whether findchip's behavior should depend
> > on the BIOS setting, SIR v. FIR? For instance,
> > Windows doesn't try to install SMC_IRCC in SIR
> > BIOS mode, only installing a genetic IRPnP0510
> > device.
> >
> > On LInux, findchip can't see anything in SIR
> > mode. Does it mean I'll be unable to use
> > all other irda-utils for the SIR mode?
>
> Let me share my experience with the SMC in my notebook. I'm not very sure
> about what I'm saying here, but this are my discoveries so far :)
>
> My notebook has a fdc37c95x Ultra IO chip, which seems to be a customized
> version of the fdc37n958 chip, according to a guy at SMC.
>
> This chip reports through a PnP BIOS (using the biosdump.exe utility for
> instance) that it has a generic IrDA SIR port. By the other side, if I
> use a ACPI compliant version of windows, it reports a SMC IrCC. This is
> due to the fact that ACPI has device enumeration and configuration, and
> when enabled it reports a *SMCF010 PnP ID instead of the *PNP0510 ID.
>
> 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.
>
> When I boot windows, it detects this conflict, and then assigns 0x110 for
> the SMC, and everything works fine. But linux has not a simple way to
> configure ACPI devices yet, something like isapnptools. So I'm not sure
> how to configure the SMC in linux yet, before modprobing smc-ircc with the
> correct addresses.
>
> So what am I doing? Waiting to more ACPI support from the ACPI guys. ACPI
> support is very new, and they have many questions on how to implement it.
> ACPI is very confusing. But I'm quite sure that using ACPI we would be
> able to 'see' much more IrDA hardware on the machines. For instance, when
> I run biosdump.exe, I get exactly the same output than the Armada 1592
> listed in the old HOWTO, and according to Compaq, this machines (1592 and
> others) also have FIR ports. That possibly means that they also have chips
> which can be correctly identified through ACPI.
>
> This is what I think. Of course, I may be completely wrong :)
>
> --
> Roberto Jung Drebes <[EMAIL PROTECTED]>
> Porto Alegre, RS - Brasil
> http://www.inf.ufrgs.br/~drebes/
>
>
> _______________________________________________
> Linux-IrDA mailing list - [EMAIL PROTECTED]
> http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
--
--
Alexander Hoogerhuis | #include <stddisc.h>
Glasgow - Graham Technology |
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda