| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
so it fits on a standard display.
|
|
list of supported chips.
|
|
|
|
|
|
- ICT interrupts for >=5000 series (avoids reading IWN_INT which is slow)
- support v2 firmware header (including build number)
- switch to v2 firmware api (requires a firmware package upgrade)
- initial support for 1000 series and initial bits for upcoming 6000
series (untested as hardware is not available to the general public)
- many bug fixes, including workarounds for hardware bugs
make sure to update your iwn-firmware package to iwn-firmware-5.2.
|
|
the list of supported cards
|
|
one pci bus can attach to an xbridge (if PIC) and both being `bus 0' would
make dmesg confusing.
While there, seize the opportunity of this new dmesg line to display the
bus mode (PCI or PCIX) and speed.
|
|
fix superfluous double space in manual page body; fix typo.
from Alan R. S. Bueno.
ok jmc@
|
|
few remaining ".Tn UNIX" macros with ".Ux" ones.
pointed out by ratchov@, thanks!
ok jmc@
|
|
|
|
Consequently, clean up the related instructions, this is now simpler.
While here, make the discussion of daily(8) more concise.
Thanks to Rene Maroufi <info at maroufi dot net> for reporting
the outdated documentation.
Wording tweaked by jmc@, OK jmc@ sobrado@
|
|
|
|
|
|
as well as how the mixer item names are derived.
|
|
|
|
should actually use the pass modifier.
ok henning jmc
|
|
|
|
|
|
|
|
ok jasper
|
|
tweaked by jmc@
ok jmc@
|
|
|
|
|
|
- queue packets from pf(4) to a userspace application
- reinject packets from the application into the kernel stack.
The divert socket can be bound to a special "divert port" and will
receive every packet diverted to that port by pf(4).
The pf syntax is pretty simple, e.g.:
pass on em0 inet proto tcp from any to any port 80 divert-packet port 1
A lot of discussion have happened since my last commit that resulted
in many changes and improvements.
I would *really* like to thank everyone who took part in the discussion
especially canacar@ who spotted out which are the limitations of this approach.
OpenBSD divert(4) is meant to be compatible with software running on
top of FreeBSD's divert sockets even though they are pretty different and will
become even more with time.
discusses with many, but mainly reyk@ canacar@ deraadt@ dlg@ claudio@ beck@
tested by reyk@ and myself
ok reyk@ claudio@ beck@
manpage help and ok by jmc@
|
|
|
|
|
|
|
|
|
|
are very close to the Tsunami systems (rpb family 34) and share the existing
Tsunami code; the tsc(4) Tsunami controller code is extended to handle the
Titan differences, except for the Titan AGP GART which is left unsupported
for now.
Tested to not cause regressions on DS20 (deraadt@) and ES40 (miod@).
Titan support tested by Sergey Prysiazhnyi on DS25, many thanks for your time!
|
|
on an expresscard SSD adaptor.
ok jsg
|
|
ok jsg@
|
|
ok miod
|
|
|
|
|
|
|
|
|
|
in multiple revisions and add the Realtek one as a supported urtw(4)
device after confirming with the windows driver that we match the id.
The revisions mentioned on the TRENDnet page fall out like so:
rev A ZD1211
V2 SiS163U
V2.1R SiS163U
V3.xR RTL8187B
We don't handle the SiS ones.
|
|
|
|
|
|
|
|
|
|
ok sthen@
|
|
|
|
|
|
Sorry.
|
|
- queue packets from pf(4) to a userspace application
- reinject packets from the application into the kernel stack.
The divert socket can be bound to a special "divert port" and will
receive every packet diverted to that port by pf(4).
The pf syntax is pretty simple, e.g.:
pass on em0 inet proto tcp from any to any port 80 divert-packet port 8000
test, bugfix and ok by reyk@
manpage help and ok by jmc@
no objections from many others.
|
|
|
|
|
