summaryrefslogtreecommitdiffstats
path: root/share/man/man4/man4.sgi (follow)
Commit message (Collapse)AuthorAgeFilesLines
* consistently spell "real-time clock";jmc2018-06-183-12/+12
| | | | ok deraadt bentley schwarze
* for some time now mandoc has not required MLINKS to functionjmc2016-03-301-4/+1
| | | | | | | | | | | | correctly - logically complete that now by removing MLINKS from base; authors need only to ensure there is an entry in NAME for any function/ util being added. MLINKS will still work, and remain for perl to ease upgrades; ok nicm (curses) bcook (ssl) ok schwarze, who provided a lot of feedback and assistance ok tb natano jung
* fix NAME; ok schwarzejmc2015-11-212-6/+8
|
* pci at macepcibr, not macepcbir;jmc2015-11-141-3/+3
|
* More IP26 bits.miod2015-09-201-8/+5
|
* Use .An in the AUTHORS section where appropriate;schwarze2015-01-153-10/+16
| | | | from Kaspars at Bankovskis dot net
* .An in AUTHORS;jmc2014-12-071-2/+2
|
* Colour support has been implemented a while ago.miod2014-12-071-4/+3
|
* use .Mt for email addresses; from Jan Stary <hans at stare dot cz>; ok jmc@schwarze2013-07-161-3/+3
|
* do not use Sx for sections outwith the man page;jmc2013-06-291-8/+5
|
* Switch mvme68k to MI wdsc(4) driver. Tested on MVME147.miod2013-05-192-71/+2
|
* Document a possibility to disable the Sync-on-Green signal by settingmikeb2012-05-291-2/+9
| | | | | the ARCBios environment variable OSLoadOptions to "nosog". Reminded by miod, corrections and ok from jsing.
* It turns out that, when the IRIX header files mention CTR/DCD/DTR/RTS wiringmiod2012-05-121-6/+7
| | | | | | | | | | | | | | | is inverted on Indigo, this just means that Indigo does not use the same values as the later models. It does not mean that the Indigo is using wrong values, which is how I first read this. In reality, Indigo systems use the expected values of these signals being active low, while later designs use active high signals. So yes, some systems have inverted values - but the ones which need compensating are not those I thought. Change the logic to do TRT, but keep the device flags check, to be able to force the other behaviour if the kernel guesses wrongly. Tested on Indigo, Indy and Indigo 2.
* punctuation needs to be space separated;jmc2012-04-291-2/+2
|
* I am not sure what the mess with the wiring of carrier lines on Indigo resolvesmiod2012-04-291-2/+19
| | | | | to, so make this controllable with device flags, and default to non-bogus wiring.
* tweak previous;jmc2012-04-192-6/+7
|
* Document recent workmiod2012-04-1810-43/+332
|
* Default DMA-reachable address constraints to the whole address space, andmiod2012-04-031-10/+2
| | | | | | | | | 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).
* tweak previous;jmc2012-03-292-12/+13
|
* Work in progress support for the SGI Indigo, Indigo 2 and Indy systemsmiod2012-03-2810-6/+563
| | | | | | | | | | | | | | | | | | | | | | | | | (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).
* make -column lists pretty again;jmc2011-09-031-6/+4
| | | | | | | | | | specifically, rewrite them to permit some markup in the column headers, and use "Ta" instead of literal tabs; mandoc does not currently match groff 100%, but a mandoc fix may be some time off, and we've gone enough releases with poorly formatting column lists. in some cases i have rewritten the lists as -tag, where -column made little sense.
* machdep.kbdreset enables a shutdown by Ctrl-Alt-Del on amd64 andnaddy2011-06-241-3/+3
| | | | | | | | | | | | | | | i386. Stop abusing it on other archs for controling a shutdown by pressing the soft power button: * Add a MI sysctl hw.allowpowerdown; if set to 1 (the default) it allows a power button shutdown. * Make acpi(4)/acpibtn(4) honor hw.allowpowerdown. * Switch the various power button intercepts on landisk, sgi, sparc64 and zaurus over to hw.allowpowerdown. * Garbage collect the machdep.kbdreset sysctl on all archs other than amd64 and i386. ok miod@
* bahderaadt2010-03-081-3/+3
|
* build a missing manual pagederaadt2010-03-081-3/+3
|
* Minimalistic driver for the ImpactSR (Mardigras) video option found on oldermiod2010-03-073-3/+58
| | | | | | | | Octane systems, as well as some Onyxes. With special permission to change a systemwide .h file and add a manpage from deraadt@ Magic numbers and operation sequencing borrowed from Linux; tested on Octane + ESI. ok deraadt@
* Add odyssey(4) to list of supported widgets.jsing2010-03-071-2/+4
| | | | Prompted by jmc@.
* Shorten .Nd.jsing2010-03-071-3/+3
|
* Introduce odyssey(4), a driver for the SGI VPro (aka Odyssey) graphicsjsing2010-03-042-2/+57
| | | | | | card, which can be found in Octane, Octane2, Fuel, Tezro and Onyx systems. ok miod@
* Add missing "wsdisplay* at gbe?". Also, list the hardware initialisationjsing2010-03-021-4/+5
| | | | requirements as a caveat rather than a bug.
* Neither .Pp nor unqualified text are allowed at the top level of .Bl;schwarze2010-01-031-3/+3
| | | | | | | | instead, .It is required. Thus, move .Pp and text before the .Bl, and remove the .Pp altogether where it is not needed. Syntax errors found by mandoc(1), also required to fix the mandoc build; feedback and ok jmc@, and sobrado@ also supports the direction.
* * always move the same amount of data (256 frames) in the interrupt handlerjakemsr2009-11-181-3/+2
| | | | | | | | | * round blocksizes to multiples of 256 frames * fix display of record.source.volume and add record.mic.preamp mixer controls * add recording support ok kettenis@. ok ratchov@ on a slightly different version.
* Add glue to attach iockbc(4) to iof(4) as well. Tested by deraadt@miod2009-11-182-13/+16
|
* Various missing configuration stanza and references.miod2009-11-164-13/+18
|
* tweak previous;jmc2009-11-101-2/+2
|
* Might as well roff iockbc.4miod2009-11-101-2/+2
|
* Add iockbc(4), a driver for the PS/2 keyboard and mouse interface found onjsing2009-11-102-6/+52
| | | | | | ioc(4) devices. Joint work with miod@. Committed from the glass console on an SGI Fuel.
* Don't mention ukphy(4) in SYNOPSIS, reminded by brad@; while there add nsphytermiod2009-11-032-6/+6
| | | | as a possible iec(4) phy.
* nicer tables like in other bus man pagesderaadt2009-11-032-32/+27
|
* More detailed model list, with a mention of the appropriate kernel.miod2009-11-021-21/+33
|
* List phy attachments, and add a few .Xrmiod2009-11-022-4/+18
|
* Driver for the sgi IOC3 onboard Ethernet interface. Tested on Octane only somiod2009-11-013-7/+58
| | | | | | | far, and needs help to figure out its Ethernet address on IP35 systems. Heavily derived from mec(4) written by Izumi Tsutsui and Christopher Sekiya, although it required many changes to fit the IOC3 chip.
* Sync with recent developments.miod2009-10-266-25/+26
|
* Introduce a logical xbpci(4) device between xbridge and pci, since more thanmiod2009-10-222-8/+14
| | | | | | | one pci bus can attach to an xbridge (if PIC) and both being `bus 0' would make dmesg confusing. While there, seize the opportunity of this new dmesg line to display the bus mode (PCI or PCIX) and speed.
* Update to match current hw support.miod2009-10-082-8/+12
|
* add missing .El;jmc2009-08-191-2/+3
|
* Document recent developments.miod2009-08-185-19/+91
|
* Comment out PIC-based systems until I get my hands on one and write the driver.miod2009-05-221-5/+5
|
* tweak previous;jmc2009-05-185-18/+20
|
* typoderaadt2009-05-181-2/+2
|
* Manpages r usmiod2009-05-179-9/+387
|