| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
- When both SC_PIXEL_MODE and SC_NO_FONT_LOADING are defined,
quietly drop SC_NO_FONT_LOADING, because the pixel(raster)
console requires font.
- When SC_NO_FONT_LOADING is defined, force SC_ALT_MOUSE_IMAGE.
Without font, the arrow-shaped mouse cursor cannot be drawn.
- Fiddle and simplify some internal macros.
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Submitted by: Kaho Toshikazu <kaho@elam.kais.kyoto-u.ac.jp>
|
|
|
|
| |
pci interrupts for the bridge.
|
|
|
|
| |
INTR_TYPE_TTY (lowest priority).
|
|
|
|
|
|
| |
an ACPI_OPERAND_OBJECT. Fix this so that the power resource type
can be properly checked, and we can get the system level and
resource order.
|
|
|
|
|
|
|
| |
Also sanitize the TRACE* macros a bit so they syntactically behave like
single C statements (even inside in `if' statement).
Submitted by: des
|
| |
|
|
|
|
| |
till timeout.
|
|
|
|
|
|
| |
haven't been probed successfully. It's a known bug that ISA hints
processing instantiates those devices, and prematurely killing them
has other unwanted side-effects.
|
|
|
|
|
|
|
|
| |
where they will never succeed. Add a stop-gap measure that will at
least eventually timeout the operation instead of retrying it
indefinately.
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
This is useful if you want to dynamically move into a Fibre Channel
or Multi-initiator environment that happens to be particularly noisy
and ugly that requires a lot of retries (with shorter I/O timeouts)
for commands destried by LIPs or Bus Resets.
Reviewed by: deafening silence on audit && scsi on the retry counts
MFC after: 2 weeks
|
|
|
|
| |
"call discards qualifier" warning (in sys/compat/linux/linux_file.c).
|
|
|
|
| |
Reviewed by: Alfred Perlstein
|
| |
|
|
|
|
|
| |
pci_enable_io(). We need to use SYS_RES_IOPORT/SYS_RES_MEMORY instead
of PCIM_CMD_PORTEN/PCIM_CMD_MEMEN.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Despite of a few cosmetic things like adding ``irritating silly
parentheses'' around all return values, this mainly improves FDC reset
handling by no longer gratuitously resetting the FDC all the time
(which causes it to lose the notion of the current track) but only in
case of errors, and it sanitizes the block and offset calculations in
fdstrategy() and fdstate(). Some additional cleanup added by me, in
particular the large switch in fdstate() now always uses return to
break out, and no branch falls off the end of the switch statement
anymore. Per Bruce's suggestion, removed M_NOWAIT from the malloc()s
to simplify things.
Submitted by: bde (mostly)
|
|
|
|
|
|
|
|
| |
successful.
This part was lacked during merge.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
Previously, I had the MODE_1000 bit in the global config register set
unconditionally, which was wrong: we have to turn it off if we have
a 10/100 link. This is now handled in the nge_miibus_statchg() routine.
Discovered by: Nathan Binkert <binkertn@eecs.umich.edu>
(Note: this commit is being done from JFK airport. :P )
|
|
|
|
| |
BDE'd by: BDE
|
|
|
|
|
|
| |
takes from /usr/include. I cannot check them on alpha.. (will try beast)
Briefly looked at by: Warner Losh <imp@harmony.village.org>
|
|
|
|
| |
(I've been using it with vmware for over a year now.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generation scheme. Users may now select between the currently used
OpenBSD algorithm and the older random positive increment method.
While the OpenBSD algorithm is more secure, it also breaks TIME_WAIT
handling; this is causing trouble for an increasing number of folks.
To switch between generation schemes, one sets the sysctl
net.inet.tcp.tcp_seq_genscheme. 0 = random positive increments,
1 = the OpenBSD algorithm. 1 is still the default.
Once a secure _and_ compatible algorithm is implemented, this sysctl
will be removed.
Reviewed by: jlemon
Tested by: numerous subscribers of -net
|
| |
|
|
|
|
|
| |
is generated from NOTES. Also correct a bogus path;
<machine>/conf/options.<machine> doesn't exist.
|
|
|
|
| |
to reflect recent changes in the code.
|
|
|
|
|
| |
is gone, and it's not coming back, and the whole driver needed to be
rethrought to deal with a major chicken-and-egg consideration.
|
|
|
|
|
| |
is gone, and it's not coming back, and the whole driver needed to be
rethrought to deal with a major chicken-and-egg consideration.
|
|
|
|
|
|
|
|
| |
tries to free uninitialized mbuf.
This was my mistake during recent KAME merge. This part is for
*BSD other than FreeBSD.
Submitted by: Alexander N. Kabaev <ak03@gte.com>
|
|
|
|
| |
acpi_cpu_speed_sysctl().
|
|
|
|
|
| |
are not coming back any time soon. Implement a new 'acpi_cpu' driver
with support for CPU throttling and power policies.
|
| |
|
| |
|
|
|
|
| |
not mandatory.
|
|
|
|
| |
directly.
|
| |
|
|
|
|
|
|
|
|
| |
Monitor the system power profile, and use _SCP to adjust thermal zones
accordingly.
Simplify the behaviour of the timeout routine, and add some temporary
debugging.
|
|
|
|
| |
is available and "economy" when it is not.
|
| |
|
|
|
|
| |
"economy" and "performance".
|
|
|
|
| |
work. Now it's implemented and seems to work.
|
| |
|
|
|
|
|
| |
when the driver is attached.
MFC after: 2 weeks
|
| |
|
|
|
|
| |
that is in included vm headers.
|
| |
|
| |
|