| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Off by default, build behaves normally.
WITH_META_MODE we get auto objdir creation, the ability to
start build from anywhere in the tree.
Still need to add real targets under targets/ to build packages.
Differential Revision: D2796
Reviewed by: brooks imp
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
| |
| |
| |
| | |
Requested by: Simon Gerraty <sjg@juniper.net>
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also change one case of blatant __progname abuse (several more remain)
This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
|
| |
Submitted by: Maxime Henrion <mux@qualys.com>
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
|
| |
o For the -i switch, only show the device if more than one is given on
the command line.
|
| |
|
|
|
|
| |
Remove special -I flags that are no longer needed.
|
|
|
|
| |
Reminded by: ru
|
| |
|
|
This driver supports PCI Xr-based and ISA Xem Digiboard cards.
dgm will go away soon if there are no problems reported. For now,
configuring dgm into your kernel warns that you should be using
digi. This driver is probably close to supporting Xi, Xe and Xeve
cards, but I wouldn't expect them to work properly (hardware
donations welcome).
The digi_* pseudo-drivers are not drivers themselves but contain
the BIOS and FEP/OS binaries for various digiboard cards and are
auto-loaded and auto-unloaded by the digi driver at initialisation
time. They *may* be configured into the kernel, but waste a lot
of space if they are. They're intended to be left as modules.
The digictl program is (mainly) used to re-initialise cards that
have external port modules attached such as the PC/Xem.
|