--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> What I want to know now is, for those of=20
> you who have an SiS 900 Ethernet driven by sip(4) and are running a=20
> current kernel compiled any time since I made the change, have you=20
> had any trouble with that driver finding its PHYs?

I couldn't really test it because I get a panic during init currently.
The boot message however implies that the changes are OK WRT the SiS 900
here:

sip0 at pci0 dev 3 function 0: SiS 900 10/100 Ethernet, rev 0x90
sip0: interrupting at ioapic0 pin 22 (irq 10)
sip0: Ethernet address 00:07:95:a9:a5:7f
ukphy0 at sip0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000004, model 0x0020, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

This is same message as usual and I've compiled support for all PHYs
into the kernel.

--=20
Christian

--fUYQa+Pmc3FrFX/N
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAtEp90KQix3oyIMcRAqwTAKCl5tTqPZzIK17m4IYQhnV8Jye0FQCgrFuO
ct3oiuBB4ig604+/HffXbpQ=
=z/KJ
-----END PGP SIGNATURE-----

--fUYQa+Pmc3FrFX/N--