| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed by: ru
|
|
|
|
| |
Submitted by: ru
|
|
|
|
| |
to change to size_t in a couple of other places too.
|
| |
|
|
|
|
| |
if the VI_LOCK() is held.
|
| |
|
|
|
|
| |
Submitted by: johan
|
|
|
|
| |
should be Byte (as the numerous casts to Byte in the function calls show).
|
|
|
|
| |
Tripped up: marks
|
|
|
|
| |
Informed by: nyan
|
|
|
|
| |
Checked with: diff on object file.
|
|
|
|
|
|
| |
for now, only include the headers for i386, amd64, or ia64.
Pointed out by: grehan
|
|
|
|
| |
Reviewed by: ru
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of the .SHELL target. Formerly it used to select the shell with the
longest common trailing substring, so that bash would select sh, but pocsh
would select csh. Now an exact match is required so that specifying bash
without also giving a path and the other keywords will give an error.
PR:
Submitted by:
Reviewed by: ru
Approved by:
Obtained from:
MFC after:
|
|
|
|
|
|
|
|
|
| |
non-standard BIOSen. We used to implement this in local patches but
now that ACPI-CA has merged/re-implemented most of our fixes, they were
no longer needed and we just needed to turn this knob on. Also, remove
an unnecessary cast.
Tested by: phk
|
|
|
|
| |
Reviewed by: mux
|
| |
|
|
|
|
| |
Obtained from: OpenBSD style.9 1.38
|
|
|
|
| |
Obtained from: ftp://elsie.nci.nih.gov/pub/tzdata2004g.tar.gz
|
|
|
|
|
|
|
|
|
|
|
|
| |
that you create one of the object directories make knows (see make(1)).
This uses the -C flag, so add a test that checks that make actually accepts
-C. Also fix the test that selects csh via the .SHELL target to work for
tcsh users too.
This commit renames shell_test to shell_test.sh. There is no history
to preserve so go without a repo-copy.
Reviewed by: ru
|
|
|
|
|
|
|
| |
it do what I had in mind.
Noticed by: glebius
Pointyhat to: me, myself and mlaier
|
|
|
|
|
|
|
|
|
| |
PR: bin/69977
o Remove unused ddates_in.
Obtained from: NetBSD
MFC after: 3 weeks
|
|
|
|
|
| |
Reviewed by: ru
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
XXX from Tor: "The shell can also go into a similar loop if the child was
killed by signal 127, since the shell would believe the child to have
only stopped (WIFSTOPPED() macro returns nonzero value). Disallowing
signals 127 and 128 will fix that problem." See kern/19402 for details.
PR: bin/66242
Submitted by: tegge
Analysis and testcase by: demon
MFC after: 3 weeks
|
| |
|
|
|
|
|
| |
Use grepable functions
Other minor nitpickings.
|
| |
|
|
|
|
|
|
|
| |
we really want vs. the size changing 'long' (i386 vs. AMD64).
This fixes the problem with DRM with Radeon's on AMD64.
Submitted by: Jung-uk Kim <jkim@niksun.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
back on again in resume. Override the default of D3 with the value the
BIOS specifies in _SxD, if present. Skip serial devices (PNP05xx) since
they seem to hang when set to D3 and may require special driver support.
Also, skip non-type 0 PCI devices (i.e., bridges) since our we don't yet
save/restore their config space and that seems to be necessary.
If this gives you trouble with suspend/resume, you can disable the new
ACPI and PCI power behavior separately with these tunables & sysctls:
debug.acpi.do_powerstate
hw.pci.do_powerstate
Approved by: imp (pci)
Tested by: acpi@ (numerous)
|
|
|
|
|
|
| |
appropriate power (Dx) state, if the BIOS suggests one.
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
pmap_remove()'s inner loop. Instead, call pmap_pde_to_pte(), a new
function, prior to the inner loop.
Reviewed by: peter@, tegge@
|
|
|
|
|
|
| |
and pmap_remove()'s inner loop.
Reviewed by: peter@, tegge@
|
|
|
|
|
|
|
|
| |
Catch up with some #define's renaming.
Implement AcpiOsGetTimer() as per ACPI 3.0.
Approved by: njl
MFC after: 1 week
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| | |
This was a debug leftover.
MFC after: 1 week
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
instead for the time being. Intel should fix this.
Note that if this commit is correct, it is made on the vendor branch.
We expect the Intel folks to fix it, and we don't want to unnecessarily
take files off the vendor branch.
Approved by: njl
MFC after: 1 week
|
| |
| |
| |
| |
| | |
Approved by: njl
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| | |
for WAK_STS to be set. Some BIOSs never set it.
Approved by: njl
MFC after: 1 week
|
| |
| |
| |
| |
| | |
Approved by: njl
MFC after: 1 week
|
| |
| |
| |
| |
| | |
Approved by: njl
MFC after: 1 week
|
| |
| |
| |
| |
| | |
usr.bin/lex/lib for the 32 bit libraries on amd64. Add an explicit
obj for these two directories that are built in for the "libraries" target.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
initializations but we did have lofty goals and big ideals.
Adjust to more contemporary circumstances and gain type checking.
Replace the entire vop_t frobbing thing with properly typed
structures. The only casualty is that we can not add a new
VOP_ method with a loadable module. History has not given
us reason to belive this would ever be feasible in the the
first place.
Eliminate in toto VOCALL(), vop_t, VNODEOP_SET() etc.
Give coda correct prototypes and function definitions for
all vop_()s.
Generate a bit more data from the vnode_if.src file: a
struct vop_vector and protype typedefs for all vop methods.
Add a new vop_bypass() and make vop_default be a pointer
to another struct vop_vector.
Remove a lot of vfs_init since vop_vector is ready to use
from the compiler.
Cast various vop_mumble() to void * with uppercase name,
for instance VOP_PANIC, VOP_NULL etc.
Implement VCALL() by making vdesc_offset the offsetof() the
relevant function pointer in vop_vector. This is disgusting
but since the code is generated by a script comparatively
safe. The alternative for nullfs etc. would be much worse.
Fix up all vnode method vectors to remove casts so they
become typesafe. (The bulk of this is generated by scripts)
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| | |
Approved by: alfred
|
| |
| |
| |
| | |
Approved by: alfred
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
in the _PRS or _CRS of link devices. If faced with multiple DPFs in a
_PRS, we just use the first one. We assume that if _CRS has DPF tags they
only contain a single set since multiple DPFs wouldn't make any sense. In
practice, the only DPFs I've seen so far for link devices are that the one
IRQ resource is surrounded by a DPF tag pair for no apparent reason, and
this should handle that case fine now.
- Only allocate link structures for IRQ resources for link devices rather
than allocating a link structure for every resource.
Reviewed by: njl
Tested by: phk
|
| |
| |
| |
| | |
argument.
|