Re: Further on P4R800-VM and 3c59x

Donald Becker <[email protected]> Wed, 7 Jan 2004 19:33:17 -0500 (EST)
Newsgroups gmane.linux.drivers.vortex.devel
Message-ID <Pine.LNX.4.44.0401071926020.8974-100000@beohost>
On Thu, 8 Jan 2004, Andrej Prsa wrote:

> > >  However,
> > > even after setting debug=31, I'm still getting nothing more than what
> > > I already posted. Any clue why? Could you perhaps suggest any action
> > > that should definitely produce some output to the log?
> > 
> > The system logger is likely throwing away the messages.
> > In /etc/syslog.conf add the line
> > kern.*						-/var/log/debug
> 
> I had the line "kern.*     -/var/log/kernel.log" before. I changed it now
> and indeed there is slight improvement; when ifconfig'ing the card, I get:
> 
> eth0: Initial media type Autonegotiate half-duplex.
> eth0: MII #1 status 786d, link partner capability 41e1, setting
> full-duplex.
> eth0: vortex_open() irq 3 media status 8080.

After this you should be getting messages about packets being queued.
Here are message levels -- you'll need "debug=16" to see all of these.
	NETIF_MSG_DRV           = 0x0001,
	NETIF_MSG_PROBE         = 0x0002,
	NETIF_MSG_LINK          = 0x0004,
	NETIF_MSG_TIMER         = 0x0008,
	NETIF_MSG_IFDOWN        = 0x0010,
	NETIF_MSG_IFUP          = 0x0020,
	NETIF_MSG_RX_ERR        = 0x0040,
	NETIF_MSG_TX_ERR        = 0x0080,
	NETIF_MSG_TX_QUEUED     = 0x0100,
	NETIF_MSG_INTR          = 0x0200,
	NETIF_MSG_TX_DONE       = 0x0400,
	NETIF_MSG_RX_STATUS     = 0x0800,
	NETIF_MSG_PKTDATA       = 0x1000,
	NETIF_MSG_WOL           = 0x4000,
	NETIF_MSG_MISC          = 0x8000,
	NETIF_MSG_RXFILTER      = 0x10000,

You should see messages such as
   "eth0: Queuing Tx packet, index 0.\n"


> > > While I was looking through the source, I noticed there were two
> > > entries for 3c920 card, on lines 321 and 323. Is that normal?
..
> > You may be seeing a wildcard match line, or a line that identifies a
> > specific card release by the subsystem ID and recognizes other cards
> > with that primary ID with the next line.
> 
> Lines 321 through 324:
> 
> 	{"3c920 Tornado",{ 0x920110B7, 0xffffffff },
> 	 PCI_IOTYPE, CYCLONE_SIZE, FEATURE_TORNADO, },
> 	{"3c920 series Tornado",{ 0x920010B7, 0xfff0ffff },
> 	 PCI_IOTYPE, CYCLONE_SIZE, FEATURE_TORNADO, },
> It's supposedly the same card, right? With different 0xfff_ffff?

Exactly.  The earlier line should match the 3c920 card we know about.
The second line will match future versions.

The "Zc" version of a mid-december added a line in the middle:
	{"3c920 Radeon Tornado",{ 0x920210B7, 0xffffffff },
	 PCI_IOTYPE, CYCLONE_SIZE, FEATURE_TORNADO, },
The only change is to specifically identify the NIC type -- the driver
does not change behavior.

If we find a need for a driver for this specific ID, the line might
change to something such as
	{"3c920 Radeon Tornado",{ 0x920210B7, 0xffffffff },
	 PCI_IOTYPE, CYCLONE_SIZE, FEATURE_TORNADO|WN0_XCVR_PWR, },


-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster systems
Annapolis MD 21403			410-990-9993

_______________________________________________
vortex mailing list
[email protected]
http://www.scyld.com/mailman/listinfo/vortex