| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
o turn off a bunch of stuff that's unlikely to be used
o add flash support
o use mii instead of miibus to save space
o enable tdma support
o configure legacy usb as usb2 works only on 2348 w/ 64M configs
|
|
|
|
| |
o switch to a more common flash config
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
instead of boot0cfg to switch the active partition
|
| |
|
|
|
|
| |
Inspired by: simon@
|
| |
|
|
|
|
| |
stats obtained from the hal)
|
| |
|
| |
|
|
|
|
| |
nanobsd framework.
|
|
|
|
| |
o shrink some fields now that we don't have to worry about overflow
|
|
|
|
|
|
| |
unless it's not setup or zero's; this may not work as the bssid of
the ibss isn't certain to the "right mac address" but for many cases
it is
|
| |
|
| |
|
| |
|
|
|
|
|
| |
o split out code to get the bssid for use in the future
o include more information in error diags when unable to collect sta info/stats
|
|
|
|
|
| |
Sponsored by: Carlson Wireless
Reviewed by: imp, Chris Andreson
|
| |
|
| |
|
| |
|
|
|
|
| |
Spotted by: juli
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
quoth the README:
I have been running -current on my laptop since before FreeBSD 2.0 was
released and along the way developed this little trick to making the
task easier.
sysbuild.sh is a way to build a new FreeBSD system on a computer from
a specification, while leaving the current installation intact.
sysbuild.sh assume you have two partitions that can hold your rootfs
and can be booted, and roughly speaking, all it does is build a new
system into the one you don't use, from the one you do use.
A partition named /freebsd is assumed to be part of your layout, and
that is where the sources and ports will be found.
If you know how nanobsd works, you will find a lot of similarity.
|
|
|
|
| |
obsolete but commit now so it's available for anyone that's interested
|
| |
|
| |
|
|
|
|
| |
Submitted by: several
|
|
|
|
| |
Submitted by: Alexander Best <alexbestms@math.uni-muenster.de>
|
|
|
|
|
|
| |
probably needs cleanups to be less specific to my needs/uses
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o add net80211 support for a tdma vap that is built on top of the
existing adhoc-demo support
o add tdma scheduling of frame transmission to the ath driver; it's
conceivable other devices might be capable of this too in which case
they can make use of the 802.11 protocol additions etc.
o add minor bits to user tools that need to know: ifconfig to setup and
configure, new statistics in athstats, and new debug mask bits
While the architecture can support >2 slots in a TDMA BSS the current
design is intended (and tested) for only 2 slots.
Sponsored by: Intel
|
|
|
|
| |
devices and switches.
|
|
|
|
|
| |
in the explanation. Several of the flags were -i, since it was a copy/paste
operation.
|
| |
|
|
|
|
| |
left by e.g. legacy uucp or tip.
|
| |
|
| |
|
|
|
|
| |
o improve some labels
|
| |
|
| |
|
|
|
|
| |
to buildworld and/or buildkernel
|
|
|
|
| |
MFC after: 2 days
|
|
|
|
| |
also ignore .svn directories.
|
|
|
|
|
|
|
|
|
|
|
| |
possible to make NanoBSD output more quite or verbose. The default
output should remain mostly unchanged. [1]
- Add missing shift for -i.
- Clean up usage() so it's now (mostly) sorted alphabetically.
- Make command line argument handling more consistent in the code and
remove redundant semicolons.
Reviwed by: phk [1]
|
|
|
|
|
|
|
|
|
|
| |
* Allow the image name to be renamed via NANO_IMGNAME.
* Propagate TARGET_ARCH into src top level make targets
explicitly to support cross-building.
* Increase the default size of NanoBSD media from 488MB to
584MB to accomodate a -CURRENT world.
Reviewed by: phk
|
|
|
|
|
|
|
| |
This fixes USB boot (not yet merged to HEAD) with 3 flavours
of BIOS I've seen.
Approved by: phk
|
|
|
|
|
| |
building multiple NanoBSD images at once to keep track of what is
running and what isn't.
|