Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
encountered on the oldest hppa machines.
Currently compiled in, but disabled, in the kernel, until it is stable
enough - right now read access are fine, but writes eventually time out
and do not complete.
ok deraadt@
|
|
to other trolley busses around ...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
functional mudem now
|
|
|
|
|
|
kludge; miod@ testing
|
|
|
|
|
|
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
where required and modify existing ones to use a consistant delay(25).
From NetBSD with minor mods.
ok mickey@.
|
|
|
|
for hppa/osiop; krw@ ok
|
|
|
|
|
|
test the harmony id to filter out unsupported yet
audio types and detect the teleshare.
detect input overload and report to userland.
|
|
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.
|
|
- 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@
|
|
|
|
full scale outputs between 2.8Vpp and 2.0Vpp for line.
|
|
- interrupt is called when the block has been DMA'd... since LASI seems to
include a FIFO this is -not- the same as block completion which we have
to poll for. Luckily the FIFO is deep enough that polling in the
interrupt handler seems to work.
- This probably breaks capture, but I'll fix that when I get up tomorrow.
(committed to the tune of Fugazi's "Waiting Room")
|
|
hppa machines, and gsckbd, a driver for the ps/2-like keyboard.
Both are derived from pckbc and pckbd, but the differences in port wiring and
keyboard behaviour prevented the creation of a thin pckbc wrapper.
Currently, only us and uk keyboard layouts are provided.
The adventurous person can enable gsckb[cd], wsdisplay at sti and wskbd,
but this will only work correctly on machines featuring a modern-prom sti
graphics device, and a ps/2 keyboard port.
|
|
according to the doc, the "play next" bit and therefore the device
interrupt may get raised earlier than the "record next" is set,
thus we might not program the record dma and get another harmony
interrupt right after servicing this one. this little optimization
allows to deal w/ the situation more efficiently, should it occur.
jason@ ok
|
|
|
|
strangely =) the make ulinear (native) and slinear (emulated) available.
Also, while here, make ulinear_le:16 available via emulation.
(Btw, the LASI docs say that the format code for ulinear is a
reserved value... Probably just wasn't available in the early CS4215/AD1849's)
|
|
|