Subject: Re: Adaptec 4 port ethernet not working
To: John Klos <john@ziaspace.com>
From: Jonathan A. Kollasch <jakllsch@kollasch.net>
List: port-macppc
Date: 07/07/2006 20:34:00
--XWOWbaMNXpFDWE00
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 05, 2006 at 04:30:00PM -0700, John Klos wrote:
> Hi,
>=20
> I'm trying to get a 4 port Adaptec AN-6944A/TX ethernet card working on a=
=20
> macppc machine (which is a Motorola Starmax). In dmesg I see:
>=20
> ppb0 at pci0 dev 13 function 0: Digital Equipment DC21152 PCI-PCI Bridge=
=20
> (rev. 0x03)
> pci1 at ppb0 bus 1
> pci1: i/o space, memory space enabled
> tlp0 at pci1 dev 4 function 0: DECchip 21140A Ethernet, pass 2.2
> tlp0: unable to map device registers

Hmm, interesting, perhaps OFW is not setting things behind bridges up for u=
s?
But in short, pci_mapreg_map(9) is failing somehow.

> tlp1 at pci1 dev 5 function 0: DECchip 21140A Ethernet, pass 2.2
> tlp1: broken MicroWire interface detected; setting SROM size to 1Kb
> tlp1: sorry, unable to handle your board
> tlp2 at pci1 dev 6 function 0: DECchip 21140A Ethernet, pass 2.2
> tlp2: broken MicroWire interface detected; setting SROM size to 1Kb
> tlp2: sorry, unable to handle your board
> tlp3 at pci1 dev 7 function 0: DECchip 21140A Ethernet, pass 2.2
> tlp3: broken MicroWire interface detected; setting SROM size to 1Kb
> tlp3: sorry, unable to handle your board

I'd like to see the output of the debugging code near here. tlp_srom_debug
needs to be non-zero. (short pause while I go off to find the email
that explained how) Backup your kernel, then:

gdb --write $TEST_KERNEL
set tlp_srom_debug=3D1
quit

and then boot $TEST_KERNEL.

>=20
> Apparently, this board works in other machines running NetBSD going back=
=20
> to some version of 1.5, but this is happening on both NetBSD-3 and=20
> NetBSD-current.
>=20
> Any ideas why this isn't working?

Something (hardware, firmware, kernel) is not handling the PCI bus
properly.

And why don't we see identical errors for all the tlp(4)s behind the
ppb(4)?

	Jonathan Kollasch

--XWOWbaMNXpFDWE00
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFErwuIOjx1ye3hmokRAhnjAJ9aEg+qbiTU27nfjEbZcyi1JHNDUACfejAk
fmWIjJUHPpW7iN5JckNor34=
=pPJZ
-----END PGP SIGNATURE-----

--XWOWbaMNXpFDWE00--