| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Requested by: n_hibma
Obtained from: NetBSD (original version)
|
|
|
|
|
| |
dev.ste.%d.int_rx_mod.
While I'm here add .Xr vlan as ste(4) supports long frames.
|
| |
|
| |
|
|
|
|
|
|
| |
Comment only, no data changes.
MFC after: 1 week
|
|
|
|
| |
code returns EOPNOTSUPP, not EINVAL.
|
|
|
|
|
| |
- Fixed spelling of EINVAL.
- Sorted sections.
|
| |
|
|
|
|
|
|
|
|
| |
PR: docs/140986
Submitted by: Glen Barber (glen dot j dot barber at gmail dot com)
MFC after: 4 days
Reviewed by: sam
Approved by: sam, jkois (mentor)
|
|
|
|
|
|
|
|
| |
it mentioned only VT6122. While I'm here remove the mention of
VT3119 which seems to be VIA's internal model name and VT3119
wouldn't be available to end users.
Reviewed by: brueffer
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This tunable allows one to enable (1) or disable (0) gestures like tap
and tap-hold on Synaptics TouchPad when the Extended mode isn't enabled
(ie. "hw.psm.synaptics_support" not set).
By default, the value is -1 in order to keep the current behaviour of
not enabling/disabling gestures explicitly.
PR: kern/139272
Submitted by: David Horn <dhorn2000 AT gmail DOT com>
Reviewed by: David Horn <dhorn2000 AT gmail DOT com>
|
|
|
|
|
|
|
| |
o hw.vge.msi_disable
o dev.vge.%d.int_holdoff
o dev.vge.%d.rx_coal_pkt
o dev.vge.%d.tx_coal_pkt
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
UTC time for the date...
|
|
|
|
| |
documentation on KERNFAST meaning.
|
|
|
|
| |
Submitted by: ru
|
|
|
|
|
|
|
|
|
| |
exiting a pager, vi, etc.
Add some example xterm*-clear entries to the termcap files to make
it easier for people to enable that behavior.
Document the examples in the man page to make them easier to find.
|
|
|
|
|
| |
Requested and reviewed by: attilio
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sxlock, via the sx_{s, x}lock_sig() interface, or plain lockmgr), will
leave the waiters flag on forcing the owner to do a wakeup even when if
the waiter queue is empty.
That operation may lead to a deadlock in the case of doing a fake wakeup
on the "preferred" (based on the wakeup algorithm) queue while the other
queue has real waiters on it, because nobody is going to wakeup the 2nd
queue waiters and they will sleep indefinitively.
A similar bug, is present, for lockmgr in the case the waiters are
sleeping with LK_SLEEPFAIL on. In this case, even if the waiters queue
is not empty, the waiters won't progress after being awake but they will
just fail, still not taking care of the 2nd queue waiters (as instead the
lock owned doing the wakeup would expect).
In order to fix this bug in a cheap way (without adding too much locking
and complicating too much the semantic) add a sleepqueue interface which
does report the actual number of waiters on a specified queue of a
waitchannel (sleepq_sleepcnt()) and use it in order to determine if the
exclusive waiters (or shared waiters) are actually present on the lockmgr
(or sx) before to give them precedence in the wakeup algorithm.
This fix alone, however doesn't solve the LK_SLEEPFAIL bug. In order to
cope with it, add the tracking of how many exclusive LK_SLEEPFAIL waiters
a lockmgr has and if all the waiters on the exclusive waiters queue are
LK_SLEEPFAIL just wake both queues.
The sleepq_sleepcnt() introduction and ABI breakage require
__FreeBSD_version bumping.
Reported by: avg, kib, pho
Reviewed by: kib
Tested by: pho
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
PR: docs/140985
Submitted by: Glen Barber (glen dot j dot barber at gmail dot com)
MFC after: 7 days
Reviewed by: rpaulo
Approved by: rpaulo, jkois (mentor)
|
|
|
|
|
|
|
|
|
|
| |
It turns out these entries do make Terminal.app behave a little better.
According to Thomas Dickey, Terminal.app should use TERM=nsterm anyway,
but we don't support this yet. Already having an improved termcap entry
helps, so I am going to MFC this change after all.
Suggested by: Leonidas Tsampros <ltsampros upnet gr>
MFC after: 1 month
|
|
|
|
| |
No objections from: ed, pho
|
|
|
|
| |
Approved by: ed (mentor)
|
|
|
|
| |
It seems I forgot this when I became a committer last year.
|
|
|
|
|
|
|
|
| |
cleanilinks wasn't listed in <bsd.subdir.mk>. Instead of adding it to
/sys/modules/Makefile, we'd better just add it to <bsd.subdir.mk>
directly, so we don't need to change files like /sys/modules/sound/Makefile
as well. This means you can finally clean up all those dangling symlinks
created by individual module compilation at once.
|
|
|
|
|
|
| |
various drivers for Apple Desktop Bus controllers and peripherals.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One of the things I really want to do, is to get rid of the limitations
of our current utmp(5) mechanism:
- It only allows 8 byte TTY device names.
- The hostname only allows 16 bytes of storage.
I'm not a big fan of <utmpx.h>, but I think we should at least try to
add parts of it. Unfortunately we cannot implement <utmpx.h>, because we
miss various fields, such as ut_id, ut_pid, etc. The API provided by
libulog shares some similarities with <utmpx.h>, so it shouldn't be too
hard to port these applications eventually. In most simple cases, it
should just be a matter of removing the ulog_ prefix everywhere.
As a bonus, it also implements a function called ulog_login_pseudo(),
which allows unprivileged applications to write log entries, provided
they have a valid file descriptor to a pseudo-terminal master device.
libulog will allow a smoother transition to a new file format by adding
a library interface to deal with utmp/wtmp/lastlog files. I initially
thought about adding the functionality to libutil, but because I'm not
planning on keeping this library around forever, we'd better keep it
separated.
Next items on the todo list:
1. Port applications in the base system (and ports) to libulog, instead
of letting them use <utmp.h>.
2. Remove <utmp.h>, implement <utmpx.h> and reimplement this library on
top.
3. Port as many applications as possible back to <utmpx.h>.
|
| |
|
|
|
|
| |
Tested by: glebius
|
|
|
|
|
|
|
|
|
|
|
|
| |
The hardware is compliant with WDRT specification, so I originally
considered including generic WDRT watchdog support, but decided
against it, because I couldn't find anyone to the code for me.
WDRT seems to be not very popular.
Besides, generic WDRT porbably requires a slightly different driver
approach.
Reviewed by: des, gavin, rpaulo
MFC after: 3 weeks
|
|
|
|
|
| |
Reported by: gabor
MFC after: 5 days
|
|
|
|
|
| |
PR: kern/123587
MFC after: 5 days
|
|
|
|
|
|
| |
PR: 140938
Submitted by: Bruce Cran <bruce@cran.org.uk>
MFC after: 2 weeks
|
|
|
|
| |
Submitted by: Alex Kozlov
|
| |
|
|
|
|
|
| |
Submitted by: pluknet <pluknet@gmail.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Jason <jhelfman@e-e.com>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
This and previous commit have been...
Approved by: garga (mentor)
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
| |
to it.
MFC after: 1 week
|
|
|
|
|
| |
Otherwise the tzload() (when called by gmtload()) fails to locate the UTC
file and loads the posixrules.
|
|
|
|
|
|
| |
PR: 140615
Submitted by: Andrius Morkunas <hinokind@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
| |
- Fix (harmless) typo in the definitions of Antarctica/David
- Fiji will go into DST from 29 November 2009 to 25 April 2010.
MFC after: 3 days
|
| |
|
|
|
|
| |
Submitted by: Rohit Grover <rgrover1@gmail.com>
|