#
259065 |
|
07-Dec-2013 |
gjb |
- Copy stable/10 (r259064) to releng/10.0 as part of the 10.0-RELEASE cycle. - Update __FreeBSD_version [1] - Set branch name to -RC1
[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so start releng/10.0 at '100' so the branch is started with a value ending in zero.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
220256 |
|
01-Apr-2011 |
emaste |
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
|
#
220205 |
|
31-Mar-2011 |
emaste |
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.
|
#
154974 |
|
29-Jan-2006 |
mlaier |
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
|