#
e9ac4169 |
| 15-Jul-2024 |
Warner Losh <imp@FreeBSD.org> |
Remove residual blank line at start of Makefile
This is a residual of the $FreeBSD$ removal.
MFC After: 3 days (though I'll just run the command on the branches) Sponsored by: Netflix
|
Revision tags: release/14.1.0, release/13.3.0, release/14.0.0 |
|
#
d0b2dbfa |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
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, 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 |
|
#
a5921bc3 |
| 10-May-2016 |
Glen Barber <gjb@FreeBSD.org> |
Update share/examples/* to properly install /usr/share/examples.
As result of this, a new examples package is now created.
Note, this is only effective with 'SHARED=copies' (the default), as the 'S
Update share/examples/* to properly install /usr/share/examples.
As result of this, a new examples package is now created.
Note, this is only effective with 'SHARED=copies' (the default), as the 'SHARED=symlinks' mechanism will create a symlink to the source tree version of the file(s).
Sponsored by: The FreeBSD Foundation
show more ...
|
Revision tags: 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 |
|
#
bedca8b1 |
| 02-Apr-2011 |
Ed Maste <emaste@FreeBSD.org> |
Uuencode the sample "binary" firmware image file (instead of explicitly adding \0 bytes). This is a technique that would be used in an actual driver and is more suitable as an example.
Reviewed by:
Uuencode the sample "binary" firmware image file (instead of explicitly adding \0 bytes). This is a technique that would be used in an actual driver and is more suitable as an example.
Reviewed by: mlaier
show more ...
|
#
ce5a491a |
| 31-Mar-2011 |
Ed Maste <emaste@FreeBSD.org> |
Avoid having a binary file in our source tree and instead create it at build time, to avoid possible grief maintaining FreeBSD source in alternative version control tools.
|
Revision tags: 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, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, 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 |
|
#
6aec1278 |
| 29-Jan-2006 |
Max Laier <mlaier@FreeBSD.org> |
firmware(9) is a subsystem to load binary data into the kernel via a specially crafted module. There are several handrolled sollutions to this problem in the tree already which will be replaced with
firmware(9) is a subsystem to load binary data into the kernel via a specially crafted module. There are several handrolled sollutions to this problem in the tree already which will be replaced with this. They include iwi(4), ipw(4), ispfw(4) and digi(4).
No objection from: arch MFC after: 2 weeks X-MFC after: some drivers have been converted
show more ...
|
Revision tags: 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, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, 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 |
|
#
6aec1278 |
| 29-Jan-2006 |
Max Laier <mlaier@FreeBSD.org> |
firmware(9) is a subsystem to load binary data into the kernel via a specially crafted module. There are several handrolled sollutions to this problem in the tree already which will be replaced with
firmware(9) is a subsystem to load binary data into the kernel via a specially crafted module. There are several handrolled sollutions to this problem in the tree already which will be replaced with this. They include iwi(4), ipw(4), ispfw(4) and digi(4).
No objection from: arch MFC after: 2 weeks X-MFC after: some drivers have been converted
show more ...
|