> Hi, > > > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > > > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > > > Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach > returned 6 > > > Dec 23 15:17:03 kernel: sis0: <SiS 900 10/100BaseTX> port > 0x2000-0x20ff mem > > > 0xec005000-0xec005fff irq 11 at device 4.0 on pci0 > > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > > > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > > The linux driver tells me : > > /** > * sis96x_get_mac_addr: - Get MAC address for SiS962 or SiS963 model > * @pci_dev: the sis900 pci device > * @net_dev: the net device to get address for > * > * SiS962 or SiS963 model, use EEPROM to store MAC address. > And EEPROM > * is shared by > * LAN and 1394. When access EEPROM, send EEREQ signal to > hardware first > * and wait for EEGNT. If EEGNT is ON, EEPROM is permitted > to be access > * by LAN, otherwise is not. After MAC address is read from > EEPROM, send > * EEDONE signal to refuse EEPROM access by LAN. > * The EEPROM map of SiS962 or SiS963 is different to SiS900. > * The signature field in SiS962 or SiS963 spec is meaningless. > * MAC address is read into @net_dev->dev_addr. > */ > > So we definitly are missing the support for the SiS 962/963 southbridge. > > Martin > This is just one part of the problem. The other half is PHY couldn't be detected. It seems that sis no longer implementes the enhanced phy control register, and phy has to be directly accessed via mdio. I have a patch (-stable only) for this problem, http://www.freebsd.org/~luoqi/sis.diff . I've also notice some other quirks of the chip our driver should be dealing with. Among them, the multicast address filter and DMA burst size.
-lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message