Age | Commit message (Collapse) | Author |
|
|
|
ok miod@
|
|
ok deraadt@
|
|
ok mickey@
|
|
One is a kernel fix that changes the lockin and one is a userland fix that
prevents dereferencing a freed pointer.
From provos
deraadt@ ok
|
|
|
|
a machine with yds; reported by kurem at upcase dot inf dot upol dot cz
|
|
- add defines for compression
- add bit/structure defintions for the result structures
|
|
to trying to recover the hardware going nuts under the load.
Reported to work by various people including krw@and I.
|
|
|
|
|
|
between status update and clearing the suspend bit on machines which can't
write data smaller than 32bits at a time. Diff is the work of pefo, he
just has been slacking too much to commit =)
|
|
glitch.
|
|
|
|
|
|
ok mickey@
|
|
the great intial witch hunt, as prompted by tdeval@
os-aix-dso.c: ok henning@
ab.C: ok drahn@
|
|
memory, and use block move operations in putchar, rather than keeping a copy
of the prom font in memory and using memory to frame buffer transfers.
Recommended by the sti docs. No visible performance improvement though.
Tested on both kind of sti devices by mickey@ and myself.
|
|
Still a minor issue left for tomorrow.
|
|
|
|
|
|
Also, better probe for leds on keyboard.
|
|
Thankfully HP's ps/2 mouse have no specific behaviour.
|
|
prom; tested on type4 by me and miod on type1
|
|
|
|
|
|
Reduce the size of a GENERIC kernel by ~190k
Remove the nasty pointer/bus_space_handle_t casts
Adds debug bus_space code including the ability to trace
bus operations (it actually works now).
The following rules are now followed (and verfified by the debug
code):
1. A "bus_space_handle_t" may only be used with the
"bus_space_tag_t" that created it.
2. Only "bus_space_map()" may create "bus_space_handle_t"s.
3. A "bus_space_handle_t" may not be modified after it has
been created (other than being destroyed by "bus_space_unmap()").
Thanks to help from mcbride, marc, jason, drahn, to anyone that might
have slipped my mind at the moment.
ok jason@, deraadt@
|
|
of it in kbd(8) to work correctly with such a keyboard.
Reminded by maja some time ago.
|
|
devices.
The ID module only purpose is to provide a small, unique, bitstring, which
was used for some copy-protection or licensing scheme under HP-UX.
Right now this driver is useless, as it provides no way to communicate
this information to userland, and only displays it while attaching, as such:
hilid0 at hil0 code 2: ID module
hilid0: security code 10 04 b4 41 ac 77 14 0f 41 00 00 00 00 00 00 00
hilid1 at hil0 code 3: ID module
hilid1: security code 10 04 b4 41 e3 b8 13 0f 41 00 00 00 00 00 00 00
Too bad it's not even good enough to feed the kernel random generator...
|
|
kernels to attach hilkbd0 (console keyboard) or hilms0 (main mouse) to
a specific device in the loop, by using UKC or compiling a new kernel.
Using this and the previous console changes, it is now possible on a loop
with multiple keyboards, to choose which keyboard will be the console
keyboard.
|
|
- only attach a keyboard as a console if it matches the PDC keyboard path
- on hil, as there can be multiple keyboards on the loop, attach only the
first hilkbd device configured as console keyboard. Right now this means
the one with the lowest hil code, which was the existing behaviour so far.
- do not try to switch to the wscons consdev structure early at all in
wscons_machdep, but rather wait for the console to be completely
configured (i.e. both wskbd and wsdisplay are attached) to switch.
With feedback and help from mickey@
|
|
save for the copyright message).
|
|
do not stick to u_int8_t when native word size can do the job better.
- Allow send_hildev_cmd() to return the command response buffer to its
caller, rather than forcing it to look at the guts of its parent device
softc... this will be needed shortly.
|
|
stations such as the airport extreme to associate. Tested by
Ben Lovett.
|
|
|
|
pointed out by henric
|
|
ok jason@
|
|
(also nuke the last vtophys so it'll even work on sparc64)
|
|
devices which only support PIO mode 2 or less. Use
atap_oldpiotiming to obtain supported mode for such devices.
Also use SET FEATURES only for PIO mode > 2.
Work by Alec Skelly <alec@dtkco.com> with my little help.
ok costa@
|
|
Found by dhartmei@; I thought he committed the fix but appearently not.
Also make the debugging printf for IV mismatch more useful.
|
|
|
|
- registers definitions
- timing values setup
- cable detection
Partially from Linux, FreeBSD and AMD specs.
Many thanks to Johan Lindman <tybollt@solace.mh.se> for providing
access to the testing machine.
ok gluk@
|
|
Tested by todd@; ok gluk@
|
|
|
|
|
|
|
|
intended. (This fixes a gcc3 warning.)
ok jason, millert
|
|
requested the signal. This is coherent with what /dev/tty does and
the current implementation of fcntl(F_SETOWN). Ok deraadt@
|
|
ok jason@
|
|
|