| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
managing levels. This can be enabled with the debug.cpufreq.verbose
tunable and sysctl.
|
|
|
|
|
| |
buffer. Also, reference the Intel document where the _PDC values were
found. This now supports ACPI-assisted SpeedStep on my borrowed T42.
|
|
|
|
|
| |
MFC after: 1 week
Approved by: simon (mentor)
|
|
|
|
|
|
| |
verbose mode. This is useful for profiling new adaptive algorithms
in performance (via time(1)) and total energy consumed for a given
workload.
|
|
|
|
|
|
| |
PR: 73111
Submitted by: Ville-Pertti Keinonen <will@iki.fi> (taken from NetBSD)
MFC after: 3 weeks
|
|
|
|
|
|
|
|
| |
a return instruction. (The latter is discouraged by the Opteron
optimization manual because it disables branch prediction for the return
instruction.)
Reviewed by: bde
|
|
|
|
|
|
| |
2005 copyright.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Affects to people WITH an AD1888 codec, the system will output to the port
labeled "speaker" instead of microphone. System will work the same in
multiple operating systems.
If people are currently using their systems with this codec they will need
to swap their output ports.
I have _not_ checked audio input or line input (basically, I have checked
nothing other than line-out).
I believe this is an appropriate change, it makes us consistent with
documentation, and other operating systems. Furthermore, this feature
(playing) is the vast majority of sound activities, so if this makes is
right for playback and wrong for recording... playback is more important,
and we can fix recoding in the future without worries of screwing people
again in the future (since we'll be "right" on the playback).
Submitted by: David Cross
|
|
|
|
| |
o s/DFD/DFB/g as DragonFly people did.
|
|
|
|
|
| |
Submitted by: Wojciech A. Koszek [dunstan freebsd czest pl]
PR: 79747
|
| |
|
|
|
|
| |
Add the older nVidia nForce2 SATA chip to supported HW.
|
|
|
|
|
|
|
|
|
|
| |
setting ts_recent to an arbitrary value, stopping further
communication between the two hosts.
- If the Echoed Timestamp is greater than the current time,
fall back to the non RFC 1323 RTT calculation.
Submitted by: Raja Mukerji (raja at moselle dot com)
Reviewed by: Noritoshi Demizu, Mohan Srinivasan
|
|
|
|
|
|
|
|
|
|
|
| |
a reassembly queue state structure, don't update (receiver) sack
report.
- Similarly, if tcp_drain() is called, freeing up all items on the
reassembly queue, clean the sack report.
Found, Submitted by: Noritoshi Demizu <demizu at dd dot iij4u dot or dot jp>
Reviewed by: Mohan Srinivasan (mohans at yahoo-inc dot com),
Raja Mukerji (raja at moselle dot com).
|
|
|
|
|
|
|
|
| |
(Fix for kern/78226).
Submitted by : Noritoshi Demizu <demizu at dd dot iij4u dot or dot jp>
Reviewed by : Mohan Srinivasan (mohans at yahoo-inc dot com),
Raja Mukerji (raja at moselle dot com).
|
|
|
|
| |
Submitted by : Noritoshi Demizu, Mohan Srinivasan.
|
|
|
|
|
|
| |
PR: 73111
Submitted by: Ville-Pertti Keinonen <will@iki.fi> (taken from NetBSD)
MFC after: 3 weeks
|
| |
|
|
|
|
|
|
| |
panic when trying to access a file on mounted smbfs.
Submitted by: takawata at jp freebsd org
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main reason for doing this is that the ELF dump handler expects
the thread list to be fixed while the dump header is generated, so an
upcall that occurs at the wrong time can lead to buffer overruns and
other Bad Things.
Another solution would be to grab sched_lock in the ELF dump handler,
but we might as well single-thread, since the process is about to die.
Furthermore, I think this should ensure that the register sets in the
core file are sequentially consistent.
|
|
|
|
|
|
| |
List possible tests in usage().
When running a test, print the test name.
|
|
|
|
|
|
| |
PR: 73111
Submitted by: Ville-Pertti Keinonen <will@iki.fi> (taken from NetBSD)
MFC after: 3 weeks
|
|
|
|
|
| |
OK'ed by: sam
MFC after: 2 weeks
|
|
|
|
| |
Reported by: tinderbox
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: Andrea Campi <andrea+freebsd_cvs_at_webcom.it>
|
| |
|
| |
|
|
|
|
|
|
|
| |
Hardcode this order to help track down reported LOR.
LOR reported by: Thierry Herbelot <thierry@herbelot.com>
LOR info: http://sources.zabbadoz.net/freebsd/lor.html#080
|
|
|
|
| |
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when vrele() acquires the directory lock in the wrong order. Fix this
via the following changes:
- Keep the directory locked after VOP_LOOKUP() until we've determined
what we're going to do with the child. This allows us to remove the
complicated post LOOKUP code which determins whether we should lock or
unlock the parent. This means we may have to vput() in the appropriate
cases later, rather than doing an unsafe vrele.
- in NDFREE() keep two flags to indicate whether we need to unlock vp or
dvp. This allows us to vput rather than vrele in the appropriate
cases without rechecking the flags. Move the code to handle dvp after
we handle vp.
- Remove some dead code from namei() that was the result of changes to
VFS_LOCK_GIANT().
Sponsored by: Isilon Systems, Inc.
|
|
|
|
| |
Confirmed by: rwatson
|
|
|
|
| |
Approved by: brueffer (mentor)
|
|
|
|
|
| |
Reviewed by: ru, silby
MFC after: 1 week
|
|
|
|
| |
Obtained from: The FreeBSD Simplified Chinese Project CVS
|
|
|
|
| |
Obtained from: The FreeBSD Simplified Chinese Project
|
|
|
|
| |
Submitted by: Michal Mertl
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This code is done blindfolded as I dont have such HW here, so reports
of success/failure are most welcome.
More SATA PHY cleanups.
|
| |
|