| Age | Commit message (Collapse) | Author |
|---|
|
|
|
flushing other data on the same cache lines
(such other local vars around the scsi_*_data
sturcts allocated on the satck) and that might
need to be flushed and not purged.
shows up on the cpu types that implement purge
as purge and not purge as flush.
no need for extra \n\t at the end of the asm (cosmetique).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to be enough for every case. dim off the disk led amongst the other lights
|
|
|
|
|
|
|
|
fddi. fix some debugging printfs
|
|
|
|
|
|
|
|
cooked
|
|
test the harmony id to filter out unsupported yet
audio types and detect the teleshare.
detect input overload and report to userland.
|
|
|
|
make RAMDISK not include sys/conf/GENERIC
|
|
|
|
might needed for panic() messages.
ok mickey@
|
|
|
|
|
|
|
|
For future intallation media.
|
|
these are all Regents of the University of California
|
|
netbooting from an rbootd server.
In this case, the pdc masquerades the boot device as a disk class device,
although keeping the device_path correct.
So, rather than trusting the device class the pdc reports, trust what the
kernel just configured - it must know better.
|
|
Thankfully HP's ps/2 mouse have no specific behaviour.
|
|
irq, but hppa has no generic shared interrupt code, we need to make sure
that gsckbc devices using the same irq know each other, and will pass
the interrupt notification to each other.
This allow a mouse and a keyboard to work together...
|
|
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@
|
|
|
|
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.
|
|
|
|
|
|
|
|
sense inthe gsckbc world, the code currently requires this for proper
attachment. Oops.
|
|
|
|
|
|
|
|
it will be emulated later or a trap generated appropriately.
this way we do not have to share the knowledge of the present
units all over the sources and keep it relatively easy.
this fixes the random sig4 seen before.
apparently it was caused by the xmpy instruction
triggering the fpu context switch and being of a
problem for the existing uid check to parse.
also force the fpu context reload after the exception
being taken for the fpu or other coprocessor.
reload r1 with iir after load/store emulation.
add a comment on r1 being shadowed on cpu context save before emulation.
|
|
|
