|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2 |
|
| #
fb3c2c0c |
| 09-Mar-2019 |
Sascha Wildner <saw@online.de> |
Remove some trailing whitespace in manpage comments.
|
|
Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3 |
|
| #
b2a6f486 |
| 24-Jul-2013 |
Franco Fichtner <franco@lastsummer.de> |
man4: use .Mt for emails (2/2)
This concludes the efforts to consistently use .Mt for
email addresses. It also sneaks in a couple of subtle
changes to punctuation, grammar and conversion of
'.Nm xx
man4: use .Mt for emails (2/2)
This concludes the efforts to consistently use .Mt for
email addresses. It also sneaks in a couple of subtle
changes to punctuation, grammar and conversion of
'.Nm xxx' to '.Xr xxx 4' where appropriate.
show more ...
|
|
Revision tags: v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
| #
687c98c0 |
| 09-Jul-2008 |
Thomas Nikolajsen <thomas@dragonflybsd.org> |
Fix typos.
|
| #
991261ec |
| 09-Jul-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Update et(4) manpage after recent change
|
| #
542d5754 |
| 09-Jul-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Update et(4) manpage according to recent changes
|
| #
3effc1bf |
| 23-Oct-2007 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
- Add jumbo buffer support for et(4), which supports up to 15794(*) bytes
jumbo buffer size. Allow jumbo buffer pool allocation to fail, if this
happened, MTU still could be changed to a value l
- Add jumbo buffer support for et(4), which supports up to 15794(*) bytes
jumbo buffer size. Allow jumbo buffer pool allocation to fail, if this
happened, MTU still could be changed to a value less than 2026 bytes.
- Correct onboard memory configuration (*)
- Pack TX/RX enablement bool variable and newly added jumbo buffer supporting
bool variable into a flag field in softc
- Increase TX spare segement count to reduce the possibility of busdma(9)
operation failure
- Fix comment
- Replace magic number with macro in truephy, though the macros themselves
are still quite magical
- Configure TX FIFO depth in truephy to support jumbo buffer
# (*) are based on experiments; peer is an Intel 82540EM, which supports
# 16218 bytes jumbo buffer size.
show more ...
|
| #
d217d4d9 |
| 12-Oct-2007 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Add et(4), which supports Agere ET1310 based Ethernet chips (PCIe only)
This chips supports two RX rings, one is currently used for packets
whose size are smaller than 110 bytes, the other one i
Add et(4), which supports Agere ET1310 based Ethernet chips (PCIe only)
This chips supports two RX rings, one is currently used for packets
whose size are smaller than 110 bytes, the other one is used for the
rest packets sizes.
Its RX interrupt moderation is quite similar to what bge(4) does:
Two control variables, one is used to control how many packet should be
received the other is used to control RX interrupt delay, RX interrupt
moderation is achieved through the interaction of these two variables.
Its TX interrupt moderation is more straightforward than RX's ;), you
can tell hardware which TX segment should trigger interrupt. It also
has a hardware timer, which is set to 1Hz currently to prevent
if_watchdog() from (mis)firing.
I didn't figure out how to add polling(4) support for this chip, its
RX state ring simply stops working if interrupts are disabled. However,
its hardware timer may be used to mimic polling(4) support.
The missing features of the driver as of this commit:
- Hardware checksum
- Hardware vlan tagging
- Jumbo buffer support
Hopefully, they will be added later.
Add TruePHY (will any vendors name their PHY as FalsePHY one day?) support
into miibus(4) for Agere ET1011C PHY, which is used by et(4). The data
sheet says model is 1 for ET1011C, while my testing card's model is 4; it
may be just a variant.
show more ...
|