| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
I simply forgot that I'd already proven this to be a "really good idea that
unfortunately didn't work at all" the *last* time I tried it. Now
I remember. Hmmm. I WILL defeat this evil problem.
|
|
|
|
| |
out of the appropriate menus.
|
| |
|
| |
|
| |
|
|
|
|
| |
that went away in January.
|
|
|
|
|
|
| |
anything else to do.
PR: 10468, 11594
|
| |
|
|
|
|
| |
Submitted by: Steve Kargl
|
|
|
|
| |
PR: 6559
|
|
|
|
| |
Submitted by: Hiroki Sato <hrs@geocities.co.jp>
|
|
|
|
| |
Repository copied by: Peter
|
|
|
|
|
|
| |
'makeoptions KERNEL=kernelname'. Warn about any trailing stuff as it's
not handled here. This is a simple bandaid, hopefully to head off some
complaints from certain people.
|
|
|
|
| |
login if we're -direct on a tty device.
|
|
|
|
|
|
|
|
|
| |
header in fsm_Input() we often end up with a NULL mbuf.
Deal with a possible NULL mbuf being passed into
mbuf_Prepend().
Adjust some spacing to make things more consistent.
|
|
|
|
| |
"retire" some more stuff.
|
| |
|
|
|
|
| |
(I have no idea why cvs didn't take these changes before.)
|
|
|
|
| |
Requested by: bde
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the layering.
We now ``stack'' layers as soon as we open the device (when we figure
out what we're dealing with). A static set of `dispatch' routines are
also declared for dealing with incoming packets after they've been
`pulled' up through the stacked layers.
Physical devices are now assigned handlers based on the device type
when they're opened. For the moment there are three device types;
ttys, execs and tcps.
o Increment version number to 2.2
o Make an entry in [uw]tmp for non-tty -direct invocations (after
pap/chap authentication).
o Make throughput counters quad_t's
o Account for the absolute number of mbuf malloc()s and free()s in
``show mem''.
o ``show modem'' becomes ``show physical''.
|
| |
|
|
|
|
| |
Add some more safety belts to package foo.
|
| |
|
|
|
|
| |
situations).
|
|
|
|
| |
with wrapping the internal services, so do not wrap them for now.
|
|
|
|
|
|
| |
not really UFS.
PR: 10711
|
|
|
|
| |
of values more than once. User might want to override them.
|
|
|
|
| |
2. Deal with potential whitespace evil early (PR#7455).
|
|
|
|
|
|
|
| |
power management. This will only work on newer firmware revisions; older
firmware will silently ignore the attempts to turn power management on.
Patches supplied by: Brad Karp <karp@eecs.harvard.edu>
|
|
|
|
|
|
|
| |
WaveLAN's radio modem. The default is whatever the NIC uses since NICs
sold in different countries may default to different frequencies. (The
Lose95/LoseNT software doesn't let you select the channel so it's probably
not really meant to be changed.)
|
|
|
|
|
|
| |
and '1'.
Requested by: mckay
|
| |
|
|
|
|
| |
Disable the non-working dhcp client code I just committed by mistake.
|
|
|
|
|
|
| |
which is why I didn't see this. :)
Noted by: Maxim Sobolev <sobomax@altavista.net>
|
|
|
|
|
|
|
| |
which was causing wicontrol to crash when reading string parameters
from the WaveLAN.
Patches submitted by: Brad Karp <karp@eecs.harvard.edu>
|
|
|
|
|
| |
Submitted by: Rudolf Cejka <cejkar@dcse.fee.vutbr.cz>
Reviewed by: phk
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
adapter (and some workalikes). Also add man pages and a wicontrol
utility to manipulate some of the card parameters.
This driver was written using information gleaned from the Lucent HCF Light
library, though it does not use any of the HCF Light code itself, mainly
because it's contaminated by the GPL (but also because it's pretty gross).
The HCF Light lacks certain featurs from the full (but proprietary) HCF
library, including 802.11 frame encapsulation support, however it has
just enough register information about the Hermes chip to allow someone
with enough spare time and energy to implement a proper driver. (I would
have prefered getting my hands on the Hermes manual, but that's proprietary
too. For those who are wondering, the Linux driver uses the proprietary
HCF library, but it's provided in object code form only.)
Note that I do not have access to a WavePOINT access point, so I have
only been able to test ad-hoc mode. The wicontrol utility can turn on
BSS mode, but I don't know for certain that the NIC will associate with
an access point correctly. Testers are encouraged to send their results
to me so that I can find out if I screwed up or not.
|
|
|
|
|
|
| |
Added $Id$.
PR: docs/10494
|
|
|
|
|
| |
Submitted by: Rudolf Cejka <cejkar@dcse.fee.vutbr.cz>
Reviewed by: phk
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Obtained from: PAO (written in Japanese)
Reviewed by: bsd-nomads@clave.gr.jp
freebsd-mobile@freebsd.org
Randy Bush <randy@psg.com>
Bill Trost <trost@grey.cloud.rain.com>
Bruce Campbell <bc@apnic.net>
|
|
|
|
|
| |
during one negotiation session without REJecting
everything from the second REQuest.
|
|
|
|
|
| |
after we read a newline, or we have nothing to read from /dev/klog. Read
/dev/klog in non-blocking mode.
|
|
|
|
| |
Describe ACFComp correctly.
|
| |
|
| |
|