--8/pVXlBMPtxfSuJG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, May 26, 2004 at 09:42:53AM +0200, Christian Biere wrote:
> > 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?
>=20
> 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:
>=20
> 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
>=20
> This is same message as usual and I've compiled support for all PHYs
> into the kernel.

I agree that that's how the phy used to work. However I have an SiS 900=20
too, and it reports the same values. The problem is that this OUI is=20
Xerox's, and I doubt they made the PHY in use. :-|

Is your interface stable under load? Mine always falls over if I do=20
serious NFS.

Take care,

Bill

--8/pVXlBMPtxfSuJG
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAtU7zWz+3JHUci9cRApF0AJ97/5GYhQDQDQ3Wq59VrIy9NNbadQCcCqmV
qxRA2gsNa+FafonfpUMTaVQ=
=WYmM
-----END PGP SIGNATURE-----

--8/pVXlBMPtxfSuJG--