| Age | Commit message (Collapse) | Author |
|---|
|
'done' label for the job finish.
major register missallocation for copyonfault, fix it.
clean the space regs after use.
|
|
|
|
|
|
the KS_BackSpace (use KS_Delete instead) we can restore
an ability to map any key into BackSpace symbol:
wsconsctl -w keyboard.map+="keycode 14 = Cmd_ResetEmul BackSpace"
xfree is not using the key symbols, but raw key codes and therefore
is not affected (as discussed w/ matthieu@).
in fact, nothing in the whole tree is using the KS_BackSpace right now.
existing KS_BackSpace definition is wrong and breaks the wsconsctl.
|
|
at the moment; drahn ok@
|
|
at the moment; jason ok@
|
|
Bug report from Alistair Kerr, tested miod@, inspected art@, ok provos@
|
|
|
|
to allow access to VGA card's memory by mmapping /dev/xf86.
The macdep.allowaperture does also control /dev/pci access.
Ok miod@, deraadt@
|
|
with not refing it.
Eyeballed by lurene@daemonkitty.net, fries@, nordin@ and fries@
Some additional cleanups by nordin@
|
|
on the returned file, do the FREF inside getvnode so that people can't
get away with avoiding FREF and FRELE.
Eyeballed by various people.
|
|
|
|
deraadt@ ok.
|
|
|
|
|
|
|
|
brad
|
|
the time.
This could lead to problems when a process wants to do an exec on the same
vnode it's being run from and needs to copy in arguments from an uncached
page in the data segment. When that happens uvm detects a vnode deadlock
and returns an error causing execve() return EFAULT.
This fixes the regress test in regress/sys/kern/exec_self
Also, initialize scriptvp early in exec_script because it could be
used uninitialized in a failure case.
|
|
|
|
|
|
fields in hostname.bm0 will work correctly. This does not fix the 100MB
receive problem, but allows media 10baseT in hostname.bm0 to set the
speed to a working speed.
|
|
of them.
|
|
|
|
|
|
instead of zero, if the kernel configuration file does not override
this setting.
This enables X11 to work on multihead sparc{,64} configurations
without the need for an explicit wsconscfg invocation first.
If a non-default emulation is requested, the user can still delete this
automatic resources and recreate it with wsconscfg.
ok mickey@ jason@
|
|
|
|
|
|
|
|
- Use paddr_t for avail_start and avail_end so we can handle machines with
RAM above the 2GB mark.
- Do not truncate the kernel pmap physical address to an `int' before
sticking it in the context lookup table. Fixes a booting issue on
Netra T1125s.
|
|
|
|
|
|
copyout could underflow by one byte and write a \0 where is doesn't
belong.
Don't try to micro-optimize the failure case of copyin and copyout.
It's not worth the bugs.
miod@ ok
|
|
and to allow UKC to work properly. ok miod@
|
|
|
|
|
|
|
|
-Fix some corner cases in bus_dmamap_load_mbuf().
From Takeshi Nakayama <tn@catvmics.ne.jp>
-Fix off-by-one error in iommu_dvmamap_load_raw() where if a DMA segment
has just one byte on a page the page is never mapped into the IOMMU.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for sparc, even when SMALL_KERNEL is defined. That way we get a
reasonable font on the sparcbook for the install.
|
|
Don't whine if the name server returns "no such registered type"
when we ask it for all FC-SCSI objects.
Fix a few typos.
If we get a f/w crash, if ISP_FW_CRASH_DUMP is *not* defined, do
the isp_reinit inline, otherwise, let the platform isp_async
drive things. This is because, typically, the platform isp_async
will freeze things and wake up a thread to do the actual f/w
crash dump (really *can't* be done on the interrupt stack- the
23XX has one move on the order of 500KBytes of crash dump data).
Set up to handle default framsize && exec_throttle and iid/loopid
overrides.
If we're using ancient (pre 1.17.0) 2100 f/w (for the cards that cannot
load f/w images > 0x7fff words), set ISP_FW_ATTR_SCCLUN. We explicitly
don't believe we can find attributes if f/w is < 1.17.0, so we have to
set SCCLUN for the 1.15.37 f/w we're using manually- otherwise every
target will replicate itself across all 16 supported luns for non-SCCLUN
f/w.
Correctly set things up for 23XX and either fast posting or ZIO. The
23XX, it turns out, does not support RIO. If you put a non-zero value
in xfwoptions, this will disable fast posting. If you put ICBXOPT_ZIO
in xfwoptions, then the 23XX will do interrupt delays but post to the
response queue- apparently QLogic *now* believes that reading multiple
handles from registers is less of a win than writing (and delaying)
multiple 64 byte responses to the response queue.
At the end of taking a a good f/w crash dump, send the ISPASYNC_FW_DUMPED
event to the outer layers (who can then do things like wake a user
daemon to *fetch* the crash image, etc.).
|
|
|
|
|
