wireguard-openbsd/sys/arch/sgi/dev/dsrtc.c, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/sgi/dev/dsrtc.c?h=jd%2Fqueueboosts2020-05-21T01:48:43ZUse <dev/clock_subr.h> in dsrtc(4).2020-05-21T01:48:43Zvisavisa@openbsd.org2020-05-21T01:48:43Zurn:sha1:bab4978b10a572062b67ce08011e5b824faff008
Tested on IP30 with DS1687.
Looks good to miod@
Remove now uneeded bus_space_unmap calls in the DS1742W/Origin path that2016-01-21T06:28:56Zjsgjsg@openbsd.org2016-01-21T06:28:56Zurn:sha1:10ecf088b416ce980f0646e9f5bdf5b11d8003f6
have had uninitialised bus space handle arguments since the mapping became
conditional in rev 1.9
confirmed with miod
Work in progress support for the SGI Indigo, Indigo 2 and Indy systems2012-03-28T20:44:23Zmiodmiod@openbsd.org2012-03-28T20:44:23Zurn:sha1:89e78ff68dbb60985d19f72ea5384db19f165e9c
(IP20, IP22, IP24) in 64-bit mode, adapated from NetBSD. Currently limited
to headless operation, input and video drivers will get ported soon.
Should work on all R4000, R4440 and R5000 based systems. L2 cache on R5000SC
Indy not supported yet (coming soon), R4600 not supported yet either (coming
soon as well).
Tested to boot multiuser on: Indigo2 R4000SC, Indy R4000PC, Indy R4000SC,
Indy R5000SC, Indigo2 R4400SC. There are still glitches in the Ethernet driver
which are being looked at.
Expansion support is limited to the GIO E++ board; GIO boards with PCI-GIO
bridges not ported yet due to the lack of hardware, and this kind of driver
does not port blindly.
Most of this work comes from NetBSD, polishing and integration work, as well
as putting as many ``R4x00 in 64-bit mode'' erratas as necessary, by yours
truly.
More work is coming, as well as trying to get some easy way to boot install
kernels (as older PROM can only boot ECOFF binaries, which won't do for the
kernel).
Change sgi system identification from a single system type list, to a smaller2009-11-07T14:49:00Zmiodmiod@openbsd.org2009-11-07T14:49:00Zurn:sha1:aab70d445dad86f06d947bf7b3d086170d4f008c
system type list (which really is the system family) and a subsystem type.
No functional change yet.
Rename struct confargs to struct mainbus_attach_args for consistency and also2009-10-26T20:14:40Zmiodmiod@openbsd.org2009-10-26T20:14:40Zurn:sha1:a69e38b2415054b31b7a507da8e2da1738211d95
to prevent further abuse of it.
Remove DS1687 vs DS742 runtime detection code; we only attach dsrtc on the2009-10-26T18:34:53Zmiodmiod@openbsd.org2009-10-26T18:34:53Zurn:sha1:9044761a103d4e5c202d3026264c68187cf41b79
onboard ioc(4) devices, and on Octane this is always a DS1687 wired to
IOC3 bytebus #1 and #2, while on Origin this is always a DS1742 wired to
IOC3 bytebus #0.
Better crime/mace interrupt handling; interrupt information is no longer2009-10-26T18:00:04Zmiodmiod@openbsd.org2009-10-26T18:00:04Zurn:sha1:ed8baf6720d6283035f69809c73921c44aa0ddf6
specified in the kernel configuration file, but is provided by macebus(4)
as part of the child device attachment args, and provide both crime and
mace interrupt bitmasks; this allows us to only really enable interrupt
sources we care about, and to avoid invoking interrupt handler we don't need
to for the few mace interrupts multiplexed at the crime level.
Attach DS1742 style dsrtc to iof (IOC4) too.2009-10-07T20:39:43Zmiodmiod@openbsd.org2009-10-07T20:39:43Zurn:sha1:ac3d9f22cf176014c05e1875c10edcd1cec9d816Rework ioc children attachment: instead of having ioc build a semi-bogus2009-07-26T19:58:49Zmiodmiod@openbsd.org2009-07-26T19:58:49Zurn:sha1:16c1a671c93ae13adddbe8d6eadddd34e644df5d
bus_space_handle_t, pass them ioc's own bus_space_handle and bus_space_tag,
and have the children use bus_space_subregion() on it.
TOD clock support for IOC3 flavours with DS174x chips (which are rebadged2009-05-15T23:02:23Zmiodmiod@openbsd.org2009-05-15T23:02:23Zurn:sha1:7ae2547e9c4fafce13182cc118195df432cd627f
MK48Txx). Entangled with preliminary changes which will hopefully eventually
lead to power(4) attaching on IP30 (but not finished yet).