Remove $FreeBSD$: one-line bare tagRemove /^\s*\$FreeBSD\$$\n/
Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Remove $FreeBSD$: one-line .c patternRemove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
spdx: The BSD-2-Clause-NetBSD identifier is obsolete, drop -NetBSDThe SPDX folks have obsoleted the BSD-2-Clause-NetBSD identifier. Catchup to that fact and revert to their recommended match of BS
spdx: The BSD-2-Clause-NetBSD identifier is obsolete, drop -NetBSDThe SPDX folks have obsoleted the BSD-2-Clause-NetBSD identifier. Catchup to that fact and revert to their recommended match of BSD-2-Clause.Discussed with: pfgMFC After: 3 daysSponsored by: Netflix
show more ...
share and pc-sysinstall: adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual
share and pc-sysinstall: adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - errorprone - task.The Software Package Data Exchange (SPDX) group provides a specificationto make it easier for automated tools to detect and summarize well knownopensource licenses. We are gradually adopting the specification, notingthat the tags are considered only advisory and do not, in any way,superceed or replace the license texts.Commit these apart because compile testing doesn't guarantee I didn't madesome nasty mistake. No functional change intended.
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 thesource tree version of the file(s).Sponsored by: The FreeBSD Foundation
Revert previous commit...Pointyhat to: kevlo (myself)
Prefer NULL over 0 for pointers
Uuencode the sample "binary" firmware image file (instead of explicitlyadding \0 bytes). This is a technique that would be used in an actualdriver and is more suitable as an example.Reviewed by:
Uuencode the sample "binary" firmware image file (instead of explicitlyadding \0 bytes). This is a technique that would be used in an actualdriver and is more suitable as an example.Reviewed by: mlaier
Avoid having a binary file in our source tree and instead create it atbuild time, to avoid possible grief maintaining FreeBSD source inalternative version control tools.
Small fix for making this KLD to compile.
firmware(9) is a subsystem to load binary data into the kernel via aspecially crafted module. There are several handrolled sollutions to thisproblem in the tree already which will be replaced with
firmware(9) is a subsystem to load binary data into the kernel via aspecially crafted module. There are several handrolled sollutions to thisproblem in the tree already which will be replaced with this. They includeiwi(4), ipw(4), ispfw(4) and digi(4).No objection from: archMFC after: 2 weeksX-MFC after: some drivers have been converted