wireguard-openbsd/sys/arch/sgi/include/autoconf.h, branch jd/queueboosts

Make interrupt masking MP-aware. Linux IP27 and IP35 ports served as a

2015-12-25T08:34:50Z

substitute for hardware documentation.

Add cache operation functions pointers to struct cpu_info; the various

2012-06-24T16:26:02Z

cache lines and sizes are already there, after all. The ConfigCache cache routine is responsible for filling these function pointers; cache routine invocation macros are updated to use the cpu_info fields, but may still be overriden in on platforms where only one set of cache routines is used.

Make it possible to disable the Sync-on-Green signal by setting the

2012-05-29T17:37:09Z

ARCBios environment variable OSLoadOptions to "nosog". Now everyone can enjoy running O2 without an SGI monitor and don't turn vegetarian afterwards. All the essential bits come from NetBSD's crmfb driver except they've chosen to use a "SyncOnGreen" variable not saved by the ARCS. Pointers and corrections from and ok miod, jsing

Proper support for the so-called `fast mode' of the Indigo2 ECC memory

2012-05-27T14:27:08Z

controller. In this mode, access to physical memory are not allowed to bypass the cache, and this allows the memory subsystem to run faster. Of course, some device drivers will require uncached memory access (e.g. for proper HPC DMA descriptor operation). New ip22-specific functions to switch between `fast mode' and `slow mode' are introduced. hpc(4) now provides read and write routines to fetch a dma descriptor from uncached memory into a local copy, and update it from said modified copy. On systems without the ECC MC, these will do nothing and operation will continue to access the uncached memory directly. On systems with the ECC MC, they will perform a copy, and the writeback will be done in slow mode. bus_dmamem_map() requests for DMA memory with BUS_DMA_COHERENT set in flags, which would return uncached memory, will now always fail on systems with the ECC memory controller. Drivers which really need uncached memory, and are aware of this particular setup, will now pass BUS_DMA_COHERENT | BUS_DMA_BUS1, which will let the request succeed. sq(4) will use all of the above to work mostly unmodified on ECC MC systems in fast mode. Finally, fast mode is enabled after autoconf. Tested on IP22 and IP28.

Rework the signature of the cache handling routines again. It makes more sense

2012-04-21T12:20:30Z

to pass both the virtual and physical addresses of the page to clean to SyncDCachePage, which is the only routine using `Index' operations on the data cache, which might be virtually indexed at some levels but physically indexed at others. On the other hand, it does not make any sense to pass a physical address to routines using `Hit' operations (and they were discarding them anyway). In addition to making things cleaner, this fixes sporadic userland misbehaviour (read: SIGSGEV) on RM7000 O2 systems.

Default DMA-reachable address constraints to the whole address space, and

2012-04-03T21:17:34Z

narrow these in the various ipXX_machdep.c. On IP22-like systems, narrow them to 28 bit physical addresses, but unpessimize this by extending this to 32 bit after autoconf, if no 28-bit limited hpc(4) device has been found. Since physical memory on these systems start at 128MB, this means that Indigo systems with more than 128MB memory will behave correctly (and so will Indy systems with E++ boards and more than 128MB memory).

Work in progress support for the SGI Indigo, Indigo 2 and Indy systems

2012-03-28T20:44:23Z

(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).

Move cache handling routines related definitions to a dedicated header file,

2012-03-25T13:52:52Z

rather than abusing .

Split the device_register() code responsible for boot path recognition into

2010-04-06T19:15:26Z

two distinct sets of routines: one for the ARCBios-compatible path used on non-KL systems (such as O2 and Octane), and one for the KL system using dksc() paths. When trying to match a dksc() path, walk the KL configuration of the whole system until the dksc controller is found; since the controller numbers are not assigned sequentially and contiguously, the old code would not work on complex systems (such as when booting from controller #6 when #3 to #5 are unaffected).

Introduce struct sgi_device_location to carry enough information to uniquely

2010-04-06T19:06:04Z

identify a given device by its physical connection, and add a lazy compare routine. This will be used shortly.