Revision tags: release/14.0.0 |
|
#
031beb4e |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0 |
|
#
23e124c7 |
| 07-Jan-2021 |
Warner Losh <imp@FreeBSD.org> |
pccard: Remove bt3c(4) driver
pccard is being removed, so remove bt3c driver since it only has PC Card attachment. Also remove bt3cfw(8) since it's the firmware for this driver.
Relnotes: Yes
|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
200d80cd |
| 03-Aug-2008 |
Ed Schouten <ed@FreeBSD.org> |
Disconnect drivers that haven't been ported to MPSAFE TTY yet.
As clearly mentioned on the mailing lists, there is a list of drivers that have not been ported to the MPSAFE TTY layer yet. Remove the
Disconnect drivers that haven't been ported to MPSAFE TTY yet.
As clearly mentioned on the mailing lists, there is a list of drivers that have not been ported to the MPSAFE TTY layer yet. Remove them from the kernel configuration files. This means people can now still use these drivers if they explicitly put them in their kernel configuration file, which is good.
People should keep in mind that after August 10, these drivers will not work anymore. Even though owners of the hardware are capable of getting these drivers working again, I will see if I can at least get them to a compilable state (if time permits).
show more ...
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
51713b2a |
| 13-Aug-2007 |
Maksim Yevmenkin <emax@FreeBSD.org> |
Make ng_h4(4) MPSAFE. Use similar to ng_tty(4) locking strategy. Reconnect ng_h(4) back to the build.
Reviewed by: kensmith Approved by: re (kensmith) MFC after: 1 month
|
#
08b75560 |
| 10-Jul-2007 |
Maksim Yevmenkin <emax@FreeBSD.org> |
Mark ng_h4(4) as not MPSAFE and disconnect it from the build for now.
Approved by: re (rwatson)
|
Revision tags: release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0 |
|
#
9be0cda6 |
| 19-Feb-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Style: Remove blank lines before EOF.
Tested by: cvs diff -B
|
Revision tags: release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0 |
|
#
f2bb1cae |
| 10-May-2003 |
Julian Elischer <julian@FreeBSD.org> |
Part one of undating the bluetooth code to the newest version
Submitted by: Maksim Yevmenkin <m_evmenkin@yahoo.com> Approved by: re@
|
Revision tags: release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0 |
|
#
878ed226 |
| 21-Nov-2002 |
Julian Elischer <julian@FreeBSD.org> |
The second try a committing the bluetooth code Has been seen to work on several cards and communicating with several mobile phones to use them as modems etc.
We are still talking with 3com to try ge
The second try a committing the bluetooth code Has been seen to work on several cards and communicating with several mobile phones to use them as modems etc.
We are still talking with 3com to try get them to allow us to include the firmware for their pccard in the driver but the driver is here.. In the mean time it can be downloaded from the 3com website and loaded using the utility bt3cfw(8) (supplied) (instructions in the man page)
Not yet linked to the build
Submitted by: Maksim Yevmenkin <myevmenk@exodus.net> Approved by: re
show more ...
|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
200d80cd |
| 03-Aug-2008 |
Ed Schouten <ed@FreeBSD.org> |
Disconnect drivers that haven't been ported to MPSAFE TTY yet.
As clearly mentioned on the mailing lists, there is a list of drivers that have not been ported to the MPSAFE TTY layer yet. Remove the
Disconnect drivers that haven't been ported to MPSAFE TTY yet.
As clearly mentioned on the mailing lists, there is a list of drivers that have not been ported to the MPSAFE TTY layer yet. Remove them from the kernel configuration files. This means people can now still use these drivers if they explicitly put them in their kernel configuration file, which is good.
People should keep in mind that after August 10, these drivers will not work anymore. Even though owners of the hardware are capable of getting these drivers working again, I will see if I can at least get them to a compilable state (if time permits).
show more ...
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
51713b2a |
| 13-Aug-2007 |
Maksim Yevmenkin <emax@FreeBSD.org> |
Make ng_h4(4) MPSAFE. Use similar to ng_tty(4) locking strategy. Reconnect ng_h(4) back to the build.
Reviewed by: kensmith Approved by: re (kensmith) MFC after: 1 month
|
#
08b75560 |
| 10-Jul-2007 |
Maksim Yevmenkin <emax@FreeBSD.org> |
Mark ng_h4(4) as not MPSAFE and disconnect it from the build for now.
Approved by: re (rwatson)
|
Revision tags: release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0 |
|
#
9be0cda6 |
| 19-Feb-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Style: Remove blank lines before EOF.
Tested by: cvs diff -B
|
Revision tags: release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0 |
|
#
f2bb1cae |
| 10-May-2003 |
Julian Elischer <julian@FreeBSD.org> |
Part one of undating the bluetooth code to the newest version
Submitted by: Maksim Yevmenkin <m_evmenkin@yahoo.com> Approved by: re@
|
Revision tags: release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0 |
|
#
878ed226 |
| 21-Nov-2002 |
Julian Elischer <julian@FreeBSD.org> |
The second try a committing the bluetooth code Has been seen to work on several cards and communicating with several mobile phones to use them as modems etc.
We are still talking with 3com to try ge
The second try a committing the bluetooth code Has been seen to work on several cards and communicating with several mobile phones to use them as modems etc.
We are still talking with 3com to try get them to allow us to include the firmware for their pccard in the driver but the driver is here.. In the mean time it can be downloaded from the 3com website and loaded using the utility bt3cfw(8) (supplied) (instructions in the man page)
Not yet linked to the build
Submitted by: Maksim Yevmenkin <myevmenk@exodus.net> Approved by: re
show more ...
|