Subject: Re: TCPA Driver for NetBSD
To: None <tech-kern@NetBSD.org>
From: Love <lha@stacken.kth.se>
List: tech-kern
Date: 12/11/2003 09:24:50
--=-=-=
Content-Transfer-Encoding: quoted-printable


Bill Studenmund <wrstuden@NetBSD.org> writes:

> On Wed, Dec 10, 2003 at 04:39:50PM -0500, Rick Wash wrote:
>> I've updated the patch slightly based on some comments I have received.
>> The new patch is available at:
>>=20
>>   http://www.citi.umich.edu/u/rwash/projects/trusted/tcpa-1210.patch
[..]
> So while the tcpa chip should look like an isa device with an ACPI attach=
=20
> descriptor, the LPC bridge will have to have been initialized before tcpa=
=20
> checks, as otherwise the probe will fail.
>
> Also, I don't know if the ACPI config for the LPC bus indicates what=20
> ranges it should map, or if the ACPI config for the tcpa has anything tha=
t=20
> indicages it is behind the LPC bus. ??

I looked at this some time ago, I found it on LPC/superio ioport range in
the ACPI (_CRS) info used by the driver, but never found if there was a
mapping where the TCPA chip was in the acpi, but I might have missed
something.

The ACPI contains a data-blob that tells that you that there is a ACPI
chip, but that also doesn't contain any info what ioports the tcpi chip is
at.

/*
TCPA: Length=3D50, Revision=3D1, Checksum=3D111,
        OEMID=3DIBM, OEM Table ID=3DTP-1I, OEM Revision=3D0x2022,
        Creator ID=3DPTL, Creator Revision=3D0x1
00 00 00 00 00 00 00 00 00 00 00 00 00 00=20
 */

Love


--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iQEVAwUAP9gp1HW+NPVfDpmCAQLb5Qf/Tx/0omqioIaH1ExKOuWL4l6f5/vuBWo/
XlsdO7dPf0XK4Cig6gSfpvgGg0Nfxz3B+IHPKogqT0egv5l80dLUBLAM3/HU2lmE
LfXuTsJanelI3G8R36vO7y4Hbp3NV07KgA0co28vjlbpxJs7mVSVmzGJXR2v1yYV
n042uM5ryfYi4GgGzSezI+SJaTLSMjG4hsGfDTSOrTPxAmNpG2NLRusbCQpwbMK2
KNEvU801+0bkcJR0VBD5Q1kUMnNeK5HJb8uQcUlvuUAQ07AbnvCcVOVXL2UbFGxQ
Zg46/aANO0GPubej2lX02GKXQt+xYaJELA/oDpfcwFJs1nmDhZRk4g==
=QiY5
-----END PGP SIGNATURE-----
--=-=-=--