| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Reported by: naddy
|
|
|
|
|
|
|
|
| |
for the 8169S, according to my sample board. The RealTek Linux driver
mentions 0x00800000. I'm assigning this to the 8110S until I get
more info on it. (The (preliminary) RealTek docs only say that 8169S/8110S
chips will have some combination of those two bits set, but doesn't say
exactly what bit combination goes with which chip variant.)
|
| |
|
|
|
|
|
|
| |
PR: 56021
Submitted by: Glen Gibb <grg@ridley.unimelb.edu.au>
MFC after: 1 month
|
|
|
|
| |
distribution to a MI header so it can be shared with other architectures.
|
|
|
|
|
|
|
|
|
|
| |
intpin register is expressed in hardware where 0 means none, 1 means INTA,
2 INTB, etc. The other way is commonly used in loops where 0 means INTA,
1 means INTB, etc. The matchpin argument to pci_cfgintr_search() is
supposed to be the first form, but we passsed in a loop index of the
second. This fix adds one to the loop index to convert to the first form.
Reported by: Pavlin Radoslavov <pavlin@icir.org>
|
|
|
|
|
| |
Add a acpi_SetDefaultIntrModel() method to allow drivers to set the
interrupt model prior to the acpi0 device being probed and attached.
|
|
|
|
|
|
|
|
| |
is not a size of 1. Since we already know there is a FIFO, we can
safely assume that it is at least 16 bytes. Note that all this is
mostly academic anyway. We don't use the size of the Rx FIFO
currently. If we add support for hardware flow control, we only
care about Rx FIFO sizes larger than 16.
|
|
|
|
| |
operation is interrupted (with ^C or ^Z) under CODA_VERBOSE.
|
|
|
|
| |
was added.
|
|
|
|
| |
interrupt model prior to the acpi0 device being probed and attached.
|
|
|
|
|
|
| |
benq awl100 (David Leemans)
ObTerminalRoomCommit: done!
|
| |
|
|
|
|
| |
timecounters.
|
| |
|
|
|
|
| |
numbers.
|
|
|
|
|
| |
PR: conf/56626
Submitted by: Oliver Eikemeier
|
|
|
|
|
| |
Submitted by: Stefan Farfeleder
PR: bin/56653
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a shared library or any other dyanmic allocated data block, once
pthread_once_t is initialized, a mutex is allocated, if we unload the
shared library or free those data block, then there is no way to deallocate
the mutex, result is memory leak.
To fix this problem, we don't use mutex field in pthread_once_t, instead,
we use its state field and an internal mutex and conditional variable in
libkse to do any synchronization, we introduce a third state IN_PROGRESS to
wait if another thread is already in invoking init_routine().
Also while I am here, make pthread_once() conformed to pthread cancellation
point specification.
Reviewed by: deischen
|
|
|
|
|
|
|
| |
is already passed in, instead of having the caller copy values from
that struct into additional parameters.
MFC after: 22 days
|
|
|
|
|
|
| |
gcc 3.3.x and -Wshadow. Just renames 'log' variables to be 'logname'.
MFC after: 22 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on data structures on the kernel stack which are guaranteed to be 16 byte
aligned by gcc, the amd64 ABI and __aligned(16).
Ensire the tss_rsp0 initial stack pointer is 16 byte aligned in case
sizeof(pcb) becomes odd at some point. This is convenient for the
interrupt handler case because the ring crossing pushes cause the
required odd alignment before the call to the C code.
Have fast_syscall add an additional 8 bytes to ensure that the trapframe
has the correct odd alignment for the call to C code. Note that there are
no checks to make sure that the trapframe size is appropriate for this.
This makes get/setfpcontext work properly (finally). You get a GPF in
kernel mode if any of this is botched without the alignment fixup code
that is apparently needed on i386.
|
| |
|
| |
|
| |
|
|
|
|
| |
the bge(4) driver as a template.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
written by Stuart Walsh and Duncan Barclay (with some kibbitzing by
me). I'm checking it in on Stuart's behalf.
The BCM4401 is built into several x86 laptop and desktop systems. For the
moment, I have only enabled it in the x86 kernel config because although
it's a PCI device, I haven't heard of any standalone NICs that use it. If
somebody knows of one, we can easily add it to the other arches.
This driver uses register/structure data gleaned from the Linux
driver released by Broadcom, but does not contain any of the code
from the Linux driver itself. It uses busdma.
|
|
|
|
|
|
| |
to the configuration state.
Noticed by: obrien
|
|
|
|
|
|
|
| |
to bring it into accord with the present getty(8) code.
PR: bin/56325
MFC after: 3 days
|
|
|
|
|
|
| |
PR: 51493
Submitted by: Walter Belgers
MFC after: 1 month
|
|
|
|
| |
Submitted by: marcel
|
|
|
|
|
|
|
| |
Update FADT for new fields including pm_profile, pstate_cnt, and cst_cnt.
Add acpi_print_gas() for printing various address formats.
Print FACS contents.
Remove unused code.
|
|
|
|
| |
linprocfs_init() a little and remove some gratuitous whitespace.
|
|
|
|
| |
Submitted by: grehan
|
|
|
|
| |
Reviewed by: deischen
|
| |
|
|
|
|
| |
category.
|
|
|
|
|
|
|
|
|
|
| |
latter is a kernel option for IA64_ID_PAGE_SHIFT, which in turn
determines IA64_ID_PAGE_MASK and IA64_ID_PAGE_SIZE.
The constants are used instead of the literal hardcoding (in its
various forms) of the size of the direct mappings created in region
6 and 7. The default and probably only workable size is still 256M,
but for kicks we use 128M for LINT.
|
|
|
|
| |
MFC after: 23 days
|
|
|
|
|
|
|
|
| |
debugging options. Initial option is '-D TN=<time>', which can be
used to see how newsyslog would work if run at the specified time.
(time format is ISO 8601, since that is already supported).
MFC after: 23 days
|
|
|
|
|
| |
Print a more informative message if a sleep state is not supported by BIOS.
Add comments.
|
|
|
|
|
|
|
| |
negative values. Mainly done to sync this routine with OpenBSD.
Obtained from: OpenBSD
MFC after: 23 days
|
|
|
|
| |
MFC after: 23 days
|
|
|
|
|
|
| |
for invalid times, and have the caller print the error message.
MFC after: 23 days
|
| |
|
|
|
|
|
|
| |
is changed. (that will come in later updates).
MFC after: 23 days
|