src/sys/dev/stge, branch releng/7.3FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F7.32008-04-11T04:03:36ZMFC if_stge.c rev 1.12 to RELENG_7.2008-04-11T04:03:36ZPyun YongHyeonyongari@FreeBSD.org2008-04-11T04:03:36Zurn:sha1:b4d1b784236634838fbefef2c54c134a952440b5
Use m_collapse(9) to collapse mbuf chains instead of relying on
shortest possible chain of mbufs of m_defrag(9). What we want is
chains of mbufs that can be safely stored to a Tx descriptor which
can have up to STGE_MAXTXSEGS mbufs. The ethernet controller does
not need to align Tx buffers on 32bit boundary. So the use of
m_defrag(9) was waste of time.
MFC if_stge.c rev 1.11, if_stgereg.h rev 1.4 to RELENG_7.2008-04-11T04:01:25ZPyun YongHyeonyongari@FreeBSD.org2008-04-11T04:01:25Zurn:sha1:be7fadd0770f85942a929dfa6a57c263b44f7dde
Implement WOL capability.
- Turn on WOL bits in suspend/shutdown method.
- WOL is disabled in resume routine as WOL can interfere normal
Rx operation.
- Move stge_reset() to stge_init_locked() as resetting hardware
clears configured Rx information which in turn results in
non-working Rx module after suspend/shutdown operation.
MFC: Fix function prototype for device_shutdown method.2008-03-13T07:50:48ZPyun YongHyeonyongari@FreeBSD.org2008-03-13T07:50:48Zurn:sha1:b9251501098ece76306aa0fd7417efc01883a316If we've got watchdog timeouts try to get more packets going after2007-05-01T03:40:57ZPyun YongHyeonyongari@FreeBSD.org2007-05-01T03:40:57Zurn:sha1:787b3ade61fa8b4a0a00da21340bd90bca4885e8
resetting the hardware.
Honor link up/down state in stge_start().2007-05-01T03:35:48ZPyun YongHyeonyongari@FreeBSD.org2007-05-01T03:35:48Zurn:sha1:7ef4ec5d3478bc43497b56416ff9b383a80a37a7
While I'm here move MAC control settings to stge_link_task, a task
queue which handles link state and duplex/flow controls.
Use our own timer for watchdog instead of if_watchdog/if_timer2007-05-01T03:15:04ZPyun YongHyeonyongari@FreeBSD.org2007-05-01T03:15:04Zurn:sha1:eb7a67da1a3edadfa6f7a064e952bf95856460f2
interface.
Catch up the rest of the drivers with the ether_vlan_mtap modifications.2007-03-04T03:38:08ZChristian S.J. Peroncsjp@FreeBSD.org2007-03-04T03:38:08Zurn:sha1:59a0d28bacbcc668a45c393f836f97cd8b536f8a
If these drivers are setting M_VLANTAG because they are stripping the
layer 2 802.1Q headers, then they need to be re-inserting them so any
bpf(4) peers can properly decode them.
It should be noted that this is compiled tested only.
MFC after: 3 weeks
o break newbus api: add a new argument of type driver_filter_t to2007-02-23T12:19:07ZPaolo Pisatipiso@FreeBSD.org2007-02-23T12:19:07Zurn:sha1:ef544f631226436ef590825881e7a28369df82f6
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@
Change the remainder of the drivers for DMA'ing devices enabled in the2007-01-21T19:32:51ZMarius Stroblmarius@FreeBSD.org2007-01-21T19:32:51Zurn:sha1:c2175ff5cadf1e22b3054180ba69548b00a4a0de
sparc64 GENERIC and the sound device drivers known working on sparc64
to use bus_get_dma_tag() to obtain the parent DMA tag so we can get rid
of the sparc64_root_dma_tag kludge eventually. Except for ath(4), sk(4),
stge(4) and ti(4) these changes are runtime tested (unless I booted up
the wrong kernels again...).
Move ethernet VLAN tags from mtags to its own mbuf packet header field2006-09-17T13:33:30ZAndre Oppermannandre@FreeBSD.org2006-09-17T13:33:30Zurn:sha1:78ba57b9e1fd08812b6f5a1b48a20d624a23b31d
m_pkthdr.ether_vlan. The presence of the M_VLANTAG flag on the mbuf
signifies the presence and validity of its content.
Drivers that support hardware VLAN tag stripping fill in the received
VLAN tag (containing both vlan and priority information) into the
ether_vtag mbuf packet header field:
m->m_pkthdr.ether_vtag = vlan_id; /* ntohs()? */
m->m_flags |= M_VLANTAG;
to mark the packet m with the specified VLAN tag.
On output the driver should check the mbuf for the M_VLANTAG flag to
see if a VLAN tag is present and valid:
if (m->m_flags & M_VLANTAG) {
... = m->m_pkthdr.ether_vtag; /* htons()? */
... pass tag to hardware ...
}
VLAN tags are stored in host byte order. Byte swapping may be necessary.
(Note: This driver conversion was mechanic and did not add or remove any
byte swapping in the drivers.)
Remove zone_mtag_vlan UMA zone and MTAG_VLAN definition. No more tag
memory allocation have to be done.
Reviewed by: thompsa, yar
Sponsored by: TCP/IP Optimization Fundraise 2005