src-test2/sys/dev/de, branch release/8.1.0_cvs

Copy releng/8.1 to release/8.1.0 for 8.1-RELEASE.

2010-07-17T05:41:01Z

Approved by: re (implicit) This commit was manufactured to restore the state of the 8.1-RELEASE image.

MFC a number of changes from head for ISP (203478,203463,203444,202418,201758,

2010-02-11T18:34:06Z

201408,201325,200089,198822,197373,197372,197214,196162). Since one of those changes was a semicolon cleanup from somebody else, this touches a lot more.

MFC r197461:

2009-10-05T19:29:25Z

Use __NO_STRICT_ALIGNMENT to determine whether de(4) have to apply alignment fixup code for received frames on strict alignment architectures. MFC r197463: Consistently use bus_addr_t. MFC r197464: Destroy dmamap in dma cleanup. MFC r197465: Align Tx/Rx descriptors on 32 bytes boundary instead of PAGE_SIZE. Also align setup descriptor on 32 bytes boundary. Tx buffer have no alignment limitation so create dmamap without alignment restriction[1]. Rx buffer still seems to require 4 bytes alignment limitation but we can simply use MCLBYTES for size to map the buffer instead of TULIP_DATA_PER_DESC as the buffer is allocated with m_getcl(9). de(4) supports up to TULIP_MAX_TXSEG segments for Tx buffers, increase maximum dma segment size to TULIP_MAX_TXSEG * MCLBYTES. While I'm here remove TULIP_DATA_PER_DESC as it is not used anymore. This should fix de(4) breakage introduced after r176206. Submitted by: jhb [1] Reported by: WATANABE Kazuhiro < CQG00620 <> nifty dot ne dot jp > Tested by: WATANABE Kazuhiro < CQG00620 <> nifty dot ne dot jp >, Takahashi Yoshihiro < nyan <> jp dot freebsd dot org > Approved by: re (kib)

Use if_maddr_rlock()/if_maddr_runlock() rather than IF_ADDR_LOCK()/

2009-06-26T11:45:06Z

IF_ADDR_UNLOCK() across network device drivers when accessing the per-interface multicast address list, if_multiaddrs. This will allow us to change the locking strategy without affecting our driver programming interface or binary interface. For two wireless drivers, remove unnecessary locking, since they don't actually access the multicast address list. Approved by: re (kib) MFC after: 6 weeks

tulip_busdma_cleanup: pass correct vaddr (2nd arg) to bus_dmamem_free()

2009-02-09T17:07:29Z

Found with: Coverity Prevent(tm) CID: 1998

During attach on some de(4) adapters the driver sends out a test packet as

2008-04-05T17:24:44Z

part of detecting the media. Explicitly ensure that we don't send it to bpf(4) as bpf(4) isn't setup yet. This worked by accident before the bpf interface stuff was reworked to avoid other races (bpf_peers_present, etc.) but now it needs an explicit check to avoid a panic. MFC after: 3 days PR: kern/120915

The maxsegsz of a dma tag created in de(4) is TULIP_DATA_PER_DESC bytes.

2007-06-07T00:28:47Z

In Rx path it allocates a new mbuf with m_getcl(9) so the length of the mbuf is MCLBYTES which is greater than a segment size specified by the dma tag. This segment size mismatch caused a voluntary panic. Fix the panic by settting the mbuf length to TULIP_DATA_PER_DESC. Reported by: Arne H Juul Tested by: Arne H Juul

Increase size of timer counter bitfield to accomodate the actual size of the

2007-05-20T16:43:35Z

default timer value. Discovered By: gcc 4.2 MFC after: 3 days

o break newbus api: add a new argument of type driver_filter_t to

2007-02-23T12:19:07Z

bus_setup_intr() o add an int return code to all fast handlers o retire INTR_FAST/IH_FAST For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current Reviewed by: many Approved by: re@

- Consistently use if_printf() only in interface methods: if_start(),

2006-09-15T15:16:12Z

if_watchdog, etc., or in functions used only in these methods. In all other functions in the driver use device_printf(). - Use __func__ instead of typing function name. Submitted by: Alex Lyashkov