| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
some others, like the 712, will run with a regular ps/2 keyboard from your
average computer shop, and the hardware will convert the scancodes so that
they match the braindead gsc usage.
Thus, it makes no point carrying a specific set of keyboard layouts for gsckbd,
when in fact it's (almost) the same as for pckbd, with scancodes shuffled.
So, add a simple scheme to build gsckbd tables from the pckbd tables. This
brings all the international layouts from pckbd, but jp and br have extra
keys for which I don't know the scancodes, so the generated gsckbd layouts
are incomplete.
|
|
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.
|
|
|
|
|
|
to proceed on the console keyboard, or it would not be in a good state
to handle boot -s prompt.
Found the hard way by mickey@
|
|
a kernel configured with "swap generic". This feature was relied upon
by Theo de Raadt, so that he would have to go downstairs to type "sd0a\n\n"
every time he would want to try a new kernel, effectively forcing his body
to take exercise trim the fat.
No more! This commit adds code to correctly detect the root device, currently
either a network interface or an scsi block device. This is slightly tricky,
as all the information the PDC gives up is the controller device and its
numeric subpath, and we need to match the real device from that...
Tested and found to be working on ie and sd only so far.
This commit is brought to you by the so-called friends of Theo de Raadt.
|
|
a fix is in the works.
|
|
pointed out by henric
|
|
|
|
|
|
ok jason@
|
|
which end on "odd" boundaries.
|
|
socket) would leak one MT_SONAME mbuf. ok deraadt@, henning@
|
|
(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@
|
|
|
|
|
|
|
|
|
|
the same size). ok drahn
|
|
|
|
|
|
sense inthe gsckbc world, the code currently requires this for proper
attachment. Oops.
|
|
|
|
|
|
intended. (This fixes a gcc3 warning.)
ok jason, millert
|
|
Change semantics of scrub option 'no-df' slightly: if the option is used,
it now also applies to _fragments_ with IP_DF set, not just to complete
packets. Hence, adding 'no-df' to 'scrub in all fragment reassemble'
allows to clear IP_DF from fragments, so they don't get dropped but
reassembled.
This affects several UDP protocols that used PMTU discovery, mostly
Linux' NFS implementation. In short, if you have 'scrub in all' now,
you probably want to change that to 'scrub in all no-df', unless you
want to drop fragments with IP_DF set (some people have good reasons
to do the latter, hence the non-default option).
ok frantzen@, henning@, cedric@
|
|
requested the signal. This is coherent with what /dev/tty does and
the current implementation of fcntl(F_SETOWN). Ok deraadt@
|
|
ok cedric, jason, theo
|
|
ok jason@
|
|
|
