Searched hist:4 (Results 1 - 25 of 17513) sorted by relevance

1234567891011>>

/freebsd-10.3-release/sys/dev/vt/hw/vga/
H A Dvt_vga_reg.hdiff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
diff 268366 Mon Jul 07 14:30:40 MDT 2014 ray 267622 Log:
Rename vt(4) vga module to dismiss interference with syscons(4) vga module.
267623 Log:
Remove stale link to deleted vt(4) xboxfb driver.
267624 Log:
syscons(4) and vt(4) can be built together now.
267625 Log:
Allow to disable syscons(4) if "hw.syscons.disable" kenv is set.
267626 Log:
Suspend vt(4) initialization if "kern.vt.disable" kenv is set.
267965 by emaste@ Log:
Use a common tunable to choose between vt(4)/sc(4)
With this change and previous work from ray@ it will be possible to put
both in GENERIC, and have one enabled by default, but allow the other to
be selected via the loader.
(The previous implementation had separate kern.vt.disable and
hw.syscons.disable tunables, and would panic if both drivers were
compiled in and neither was explicitly disabled.)
268175 by emaste@ Log:
Fix vt(4) detection in kbdcontrol and vidcontrol
As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.
Reported by: Trond Endrestøl
268045 by emaste@ Log:
Add vt(4) to GENERIC and retire the separate VT config
vt(4) and sc(4) can now coexist in the same kernel. To choose the vt
driver, set the loader tunable kern.vty=vt .

Sponsored by: The FreeBSD Foundation
/freebsd-10.3-release/sys/dev/mii/
H A Dmii_bitbang.c226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
H A Dmii_bitbang.h226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
/freebsd-10.3-release/share/man/man4/
H A Dsnd_ad1816.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_als4000.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_cmi.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_cs4281.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_ds1.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_solo.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dmrsas.4diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
diff 265922 Mon May 12 18:07:33 MDT 2014 ambrisko MFC 265555

dd mrsas(4) driver from LSI official support of newer MegaRAID SAS
cards. LSI has been maintaining this driver outside of the FreeBSD
tree. It overlaps support of ThunderBolt and Invader cards that mfi(4)
supports. By default mfi(4) will attach to cards. If the tunable:
hw.mfi.mrsas_enable=1
is set then mfi(4) will not probe and attach to these newer cards and
allow mrsas(4) to attach. So by default this driver will not effect
a FreeBSD system unless mfi(4) is removed from the kernel or the
tunable is enabled.

mrsas(4) attaches disks to the CAM layer so it depends on CAM and devices
show up as /dev/daX. mfiutil(8) does not work with mrsas. The FreeBSD
version of MegaCli and StorCli from LSI do work with mrsas. It appears
that StorCli only works with mrsas. MegaCli appears to work with mfi(4)
and mrsas(4).

It would be good to add mfiutil(4) support to mrsas, emulations modes,
kernel logging, device aliases to ease the transition between mfi(4)
and mrsas(4).

Style issues should be resolved by LSI when they get committers approved.
The plan is get this driver in FreeBSD 9.3 to improve HW support.

Thanks to LSI for developing, testing and working with FreeBSD to
make this driver co-exist in FreeBSD. This improves the overall
support of MegaRAID SAS.

Submitted by: Kashyap Desai <Kashyap.Desai@lsi.com>
Sponsored by: LSI
H A Daltq.4diff 255736 Fri Sep 20 20:26:33 MDT 2013 davidch Substantial rewrite of bxe(4) to add support for the BCM57712 and
BCM578XX controllers.

Approved by: re
MFC after: 4 weeks
diff 255736 Fri Sep 20 20:26:33 MDT 2013 davidch Substantial rewrite of bxe(4) to add support for the BCM57712 and
BCM578XX controllers.

Approved by: re
MFC after: 4 weeks
diff 228370 Fri Dec 09 19:32:58 MST 2011 yongari After r228293, et(4) supports altq(4).
diff 228370 Fri Dec 09 19:32:58 MST 2011 yongari After r228293, et(4) supports altq(4).
diff 227348 Tue Nov 08 18:47:54 MST 2011 yongari ti(4) supports altq(4).
diff 227348 Tue Nov 08 18:47:54 MST 2011 yongari ti(4) supports altq(4).
diff 227276 Sun Nov 06 21:09:25 MST 2011 brueffer Add qlxgb(4).

MFC after: 3 days
diff 218792 Fri Feb 18 08:12:15 MST 2011 np cxgbe(4) - NIC driver for Chelsio T4 (Terminator 4) based 10Gb/1Gb adapters.

MFC after: 3 weeks
diff 218792 Fri Feb 18 08:12:15 MST 2011 np cxgbe(4) - NIC driver for Chelsio T4 (Terminator 4) based 10Gb/1Gb adapters.

MFC after: 3 weeks
diff 217974 Thu Jan 27 20:21:42 MST 2011 yongari ixgb(4) does not support altq(4) yet.
diff 217974 Thu Jan 27 20:21:42 MST 2011 yongari ixgb(4) does not support altq(4) yet.
H A Dsnd_uaudio.4diff 219004 Thu Feb 24 18:09:51 MST 2011 hselasky - Add missing xhci(4) manual page.
- Minor update in some USB manual pages.

MFC after: 3 days
Approved by: thompsa (mentor)
diff 204605 Tue Mar 02 22:14:14 MST 2010 joel The NetBSD Foundation has granted permission to remove clause 3 and 4 from
their software.

Obtained from: NetBSD
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_emu10k1.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_es137x.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dsnd_maestro3.4diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
diff 134938 Wed Sep 08 08:28:02 MDT 2004 ru Update sound-related manpages to account for the recent change in
device and module naming. The following files were repo-copied:

csa.4 -> snd_csa.4
gusc.4 -> snd_gusc.4
maestro3.4 -> snd_maestro3.4
sbc.4 -> snd_sbc.4
uaudio.4 -> snd_uaudio.4

The pcm(4) manpage wasn't renamed to sound(4) as there are nearby
plans to rename "device sound" to "device snd", to address the
ambiguity in naming, so pcm.4 is linked to sound.4 for the moment.
(We also mumble something about the future plans in the manpage.)

Removed links from pcm.4 to als4000.4 and emu10k1.4 -- they now
have their own snd_*.4 manpages.

Fixes for recent snd_*.4 manpages: added missing "device sound"
to the SYNOPSIS, fixed hints (they are still "hint.pcm.<unit>"
in most cases).

MT5 after: 3 days
H A Dlmc.4diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
/freebsd-10.3-release/release/doc/share/misc/
H A Ddev.archlist.txtdiff 265856 Sat May 10 20:57:20 MDT 2014 brueffer MFC: r265264, r265270

Add rsu(4) and urtwn(4) to the hardware notes.
diff 265856 Sat May 10 20:57:20 MDT 2014 brueffer MFC: r265264, r265270

Add rsu(4) and urtwn(4) to the hardware notes.
diff 262686 Sun Mar 02 12:20:23 MST 2014 brueffer MFC: r262574

Add tws(4) to the hardware notes.
diff 261739 Tue Feb 11 08:20:46 MST 2014 brueffer MFC: r261487

Add qlxgbe(4) and qlxge(4) to the hardware notes.
diff 261739 Tue Feb 11 08:20:46 MST 2014 brueffer MFC: r261487

Add qlxgbe(4) and qlxge(4) to the hardware notes.
diff 237700 Thu Jun 28 10:16:20 MDT 2012 brueffer Automatically generate hardware notes for bxe(4).
diff 232355 Thu Mar 01 19:57:42 MST 2012 brueffer Add snd_hdspe(4) to the hardware notes.
diff 232060 Thu Feb 23 19:04:31 MST 2012 brueffer Add isci(4) to the hardware notes.

MFC after: 3 days
diff 231943 Mon Feb 20 19:50:36 MST 2012 brueffer Add oce(4) to the hardware notes.

MFC after: 3 days
diff 227666 Fri Nov 18 17:05:03 MST 2011 brueffer Add sfxge(4) to the hardware notes.
/freebsd-10.3-release/share/man/man5/
H A Dportindex.5diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
diff 231244 Thu Feb 09 04:53:46 MST 2012 gjb Fix some Xr references:

- ada(4): ad(4) - removed, ada(4) would be a self-referencing entry
- cd(4): ad(4) -> ada(4)
- da(4): ad(4) -> ada(4)
- DEVICE_PROBE(9): ugen(5) -> ugen(4)
- ed(4): dhclinet(8) -> dhclient(8) (typo)
- lmc(4): Netgraph(4) -> netgraph(4)
- security(7): rc.conf(8) -> rc.conf(5)
- sfxge(4): cpuset(8) -> cpuset(1)
- sbp(4): sysctl(1) -> sysctl(8)
- portindex(5): build(1) -> build(7)
- u3g(4): usbconfig(5) -> usbconfig(8)
- usb_quirk(4): usbconfig(5) -> usbconfig(8)

Found with: textproc/igor
MFC after: 3 days
/freebsd-10.3-release/sys/pci/
H A Damdsmb.cdiff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
H A Dintpmreg.hdiff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
diff 165951 Thu Jan 11 19:56:24 MST 2007 jhb Various updates to most of the smbus(4) drivers:
- Use printf() and device_printf() instead of log() in ichsmb(4).
- Create the mutex sooner during ichsmb(4) attach.
- Attach the interrupt handler later during ichsmb(4) attach to avoid
races.
- Don't try to set PCIM_CMD_PORTEN in ichsmb(4) attach as the PCI bus
driver does this already.
- Add locking to alpm(4), amdpm(4), amdsmb(4), intsmb(4), nfsmb(4), and
viapm(4).
- Axe ALPM_SMBIO_BASE_ADDR, it's not really safe to write arbitrary values
into BARs, and the PCI bus layer will allocate resources now if needed.
- Merge intpm(4) and intsmb(4) into just intsmb(4). Previously, intpm(4)
attached to the PCI device and created an intsmb(4) child. Now,
intsmb(4) just attaches to PCI directly.
- Change several intsmb functions to take a softc instead of a device_t
to make things simpler.
/freebsd-10.3-release/sys/dev/bm/
H A Dif_bmreg.hdiff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
H A Dif_bmvar.hdiff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
diff 226995 Tue Nov 01 16:22:50 MDT 2011 marius - Import the common MII bitbang'ing code from NetBSD and convert drivers to
take advantage of it instead of duplicating it. This reduces the size of
the i386 GENERIC kernel by about 4k. The only potential in-tree user left
unconverted is xe(4), which generally should be changed to use miibus(4)
instead of implementing PHY handling on its own, as otherwise it makes not
much sense to add a dependency on miibus(4)/mii_bitbang(4) to xe(4) just
for the MII bitbang'ing code. The common MII bitbang'ing code also is
useful in the embedded space for using GPIO pins to implement MII access.
- Based on lessons learnt with dc(4) (see r185750), add bus barriers to the
MII bitbang read and write functions of the other drivers converted in
order to ensure the intended ordering. Given that register access via an
index register as well as register bank/window switching is subject to the
same problem, also add bus barriers to the respective functions of smc(4),
tl(4) and xl(4).
- Sprinkle some const.

Thanks to the following testers:
Andrew Bliznak (nge(4)), nwhitehorn@ (bm(4)), yongari@ (sis(4) and ste(4))
Thanks to Hans-Joerg Sirtl for supplying hardware to test stge(4).

Reviewed by: yongari (subset of drivers)
Obtained from: NetBSD (partially)
/freebsd-10.3-release/share/vt/
H A DMakefilediff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
266838 Thu May 29 13:57:38 MDT 2014 ray Add gallant vt(4) font as an example of font loading for vt(4).

MFC after: 7 days
Sponsored by: The FreeBSD Foundation
266838 Thu May 29 13:57:38 MDT 2014 ray Add gallant vt(4) font as an example of font loading for vt(4).

MFC after: 7 days
Sponsored by: The FreeBSD Foundation
/freebsd-10.3-release/share/vt/fonts/
H A Dgallant.fnt.uudiff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
266841 Thu May 29 14:55:59 MDT 2014 ray Add gallant vt(4) font as an example of font loading for vt(4).

MFC after: 7 days
Sponsored by: The FreeBSD Foundation
266841 Thu May 29 14:55:59 MDT 2014 ray Add gallant vt(4) font as an example of font loading for vt(4).

MFC after: 7 days
Sponsored by: The FreeBSD Foundation
H A DMakefilediff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 271333 Tue Sep 09 20:37:00 MDT 2014 emaste MFC improved vt(4) font generation

r266851: Add VGAROM 8x8, 8x14 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437 fonts.

r267306: Add vgarom font source

These are in 'GNU Unifont' format, and are converted from syscons(4)
cp437 fonts.

r267400: Add thin versions of VGAROM 8x8 and 8x16 fonts for vt(4)

These are converted from syscons(4) cp437-thin-8x* fonts.

r267423: Build vt(4) fonts during buildworld

vtfontcvt(8) is now built during buildworld, so can be used as a
bootstrap tool to create vt(4) fonts from source .hex or .bdf font
files, rather than having uuencoded binary fonts in the tree.

r267578: Add glyphs from converted syscons iso* fonts

This consists of the unique glyphs from the following font files in
/usr/share/syscons/fonts:

iso*.fnt ISO-8859-1 West European
iso02*.fnt ISO-8859-2 Central European
iso04*.fnt ISO-8859-4 Baltic
iso05*.fnt ISO-8859-5 Cyrillic
iso07*.fnt ISO-8859-7 Greek
iso08*.fnt ISO-8859-8 Hebrew
iso09*.fnt ISO-8859-9 Turkish
iso15*.fnt ISO-8859-15 West European

r268022: Rename the WITHOUT_VT_SUPPORT knob to WITHOUT_VT

The _SUPPORT knobs have a consistent meaning which differs from the
behaviour controlled by this knob. As the knob is opt-out and has not
appeared in a release the impact should be low.

Approved by: re
Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation
diff 267541 Mon Jun 16 12:44:36 MDT 2014 ray MFC: 266838 266841 267194
Add gallant vt(4) font as an example of font loading for vt(4).
Add Ukranian vt(4) keymaps as an example.

Sponsored by: The FreeBSD Foundation

Completed in 212 milliseconds

1234567891011>>