summaryrefslogtreecommitdiffstats
path: root/sys/i386
Commit message (Collapse)AuthorAgeFilesLines
...
* Repo copied to <sys/iicbus/iic.h>peter2002-09-191-47/+0
|
* move wl (isa wavelan card, not "wi") to i386-onlypeter2002-09-191-1/+6
|
* move "profile 2" to i386peter2002-09-191-0/+4
|
* move ncv, nsp, stg to i386-only section (there is no pc98-specific version)peter2002-09-191-0/+14
|
* Move dgb to the i386 sectionpeter2002-09-191-0/+11
|
* Restore status register A of RTC at resume time.iwasaki2002-09-182-0/+2
| | | | | | | This should fix the 'too many RTC interrupts and statclock seems broken after resume' problem. MFC after: 1 week
* Implement C99's va_copy() macro.mike2002-09-181-0/+3
|
* Add /dev/soekris-errled device to control the Error-LED on Soekris cards/boxes.phk2002-09-171-23/+136
| | | | | | | | | | | | | | | | | | | # turn LED off echo '0' > /dev/soekris-errled # turn LED on echo '1' > /dev/soekris-errled # flash LED (5 hz) echo 'f' > /dev/soekris-errled # flash LED (4/2 = 2 hz), syntax: "f[1-9]" -> .5 -> 4.5 Hz echo 'f4' > /dev/soekris-errled # flash digits 1,3 and 7, syntax: "d[1-9]*" echo 'd137' > /dev/soekris-errled Characters not understood are ignored.
* Don't reference cpu_fxsr unless CPU_ENABLE_SSE is defined. This fixes kernelsobomax2002-09-171-2/+8
| | | | in !CPU_ENABLE_SSE case.
* Initiate deorbit burn for the i386-only a.out related support. Moves arepeter2002-09-175-34/+0
| | | | | | | | | | | | | | | under way to move the remnants of the a.out toolchain to ports. As the comment in src/Makefile said, this stuff is deprecated and one should not expect this to remain beyond 4.0-REL. It has already lasted WAY beyond that. Notable exceptions: gcc - I have not touched the a.out generation stuff there. ldd/ldconfig - still have some code to interface with a.out rtld. old as/ld/etc - I have not removed these yet, pending their move to ports. some includes - necessary for ldd/ldconfig for now. Tested on: i386 (extensively), alpha
* Add kernel support needed for the KSE-aware libpthread:mini2002-09-161-35/+152
| | | | | | | | - Maintain fpu state across signals. - Save and restore FPU state properly in ucontext_t's. Reviewed by: bde, deischen, julian Approved by: -arch
* Add kernel support needed for the KSE-aware libpthread:mini2002-09-164-14/+35
| | | | | | | | - Maintain fpu state across signals. - Save and restore FPU state properly in ucontext_t's. Reviewed by: deischen, julian Approved by: -arch
* Add kernel support needed for the KSE-aware libpthread:mini2002-09-165-81/+220
| | | | | | | | | | | - Maintain fpu state across signals. - Use ucontext_t's to store KSE thread state. - Synthesize state for the UTS upon each upcall, rather than saving and copying a trapframe. - Save and restore FPU state properly in ucontext_t's. Reviewed by: deischen, julian Approved by: -arch
* Allocate KSEs and KSEGRPs separatly and remove them from the proc structure.julian2002-09-151-1/+1
| | | | | | | | | next step is to allow > 1 to be allocated per process. This would give multi-processor threads. (when the rest of the infrastructure is in place) While doing this I noticed libkvm and sys/kern/kern_proc.c:fill_kinfo_proc are diverging more than they should.. corrective action needed soon.
* makeLINT.sed replaced makeLINT.sh about 4 months ago.mike2002-09-151-19/+0
|
* Removed unused includes. Sorted includes. This is part of removingbde2002-09-151-5/+1
| | | | | includes of <sys/user.h> for its pollution only. <sys/user.h> wasn't even used for its pollution here.
* Some BIOSs are using MTRR values that are only documented under NDAdwmalone2002-09-152-1/+12
| | | | | | | | | | | | | | | | | | | to control the mapping of things like the ACPI and APM into memory. The problem is that starting X changes these values, so if something was using the bits of BIOS mapped into memory (say ACPI or APM), then next time they access this memory the machine would hang. This patch refuse to change MTRR values it doesn't understand, unless a new "force" option is given. This means X doesn't change them by accident but someone can override that if they really want to. PR: 28418 Tested by: Christopher Masto <chris@netmonger.net>, David Bushong <david@bushong.net>, Santos <casd@myrealbox.com> MFC after: 1 week
* Whitespace consistency fix from addition of IAHD_REG_PRETTY_PRINT: userwatson2002-09-111-1/+1
| | | | tabs not spaces.
* Completely redo thread states.julian2002-09-111-0/+1
| | | | Reviewed by: davidxu@freebsd.org
* Fix LINT build on alpha by completing move of cy and apm_saver tonjl2002-09-111-0/+10
| | | | | | i386/conf/NOTES rather than the global conf/NOTES. Suggested by: bde
* move some printfs under bootverbosesam2002-09-101-4/+5
| | | | Reviewed by: phk
* Make sure a $PIR table header has a valid length before accepting the tablejhb2002-09-092-2/+4
| | | | | | as valid. Submitted by: Michal Mertl <mime@traveller.cz>
* - Fix iBCS2 emulation of COFF files that have multiple librariesrobert2002-09-091-3/+7
| | | | | | | | | in their library (STYP_LIB) section. - Attempt to make the code which calculates the next entry and string offsets look clearer. PR: kern/42580 Tested by: Olaf Klein <ok@adimus.de> (on 4.7-PRERELEASE)
* #include "opt_bla.h" goes first says Bruce.phk2002-09-091-2/+2
|
* Use "options " rather than "options<tab>".kuriyama2002-09-092-4/+4
|
* Fix style(9) bugs.phk2002-09-082-3/+3
| | | | Brucified by: bde
* Note that 'device gzip' *requires* COMPAT_AOUT. Maybe this "device"peter2002-09-081-1/+1
| | | | should be renamed to COMPAT_GZIPAOUT or something like that.
* Tidy up some loose ends that bde pointed out. caddr_t bad, ok?peter2002-09-071-8/+7
| | | | | | | Move fill_kinfo_proc to before we copy the results instead of after the copy and too late. There is still more to do here.
* The true value of how the kernel was configured for KSTACK_PAGES was notpeter2002-09-071-6/+6
| | | | | | available at module compile time. Do not #include the bogus opt_kstack_pages.h at this point and instead refer to the variables that are also exported via sysctl.
* Fill out two fields (si_pid, si_uid) in the siginfo structure handed backjmallett2002-09-071-0/+2
| | | | | | | | | | | | | | | | to userland in the signal handler that were not being iflled out before, but should and can be. This part of sendsig could be slightly refactored to use an MI interface, or ideally, *sendsig*() would have an API change to accept a siginfo_t, which would be filled out by an MI function in the level above sendsig, and said MI function would make a small call into MD code to fill out the MD parts (some of which may be bogus, such as the si_addr stuff in some places). This would eventually make it possible for parts of the kernel sending signals to set up a siginfo with meaningful information. Reviewed by: mux MFC after: 2 weeks
* Diff reduction in comments for filling the siginfo structure - refer tojmallett2002-09-071-1/+1
| | | | | filling in the POSIX parts, when doing the same thing in every port of FreeBSD.
* Match the more modern ports and comment the filling of POSIX parts of siginfojmallett2002-09-071-1/+1
| | | | with 'Fill in POSIX parts'. (Diff reduction.)
* Include <machine/pcb.h> instead of depending on namespace pollution inbde2002-09-071-0/+1
| | | | <sys/user.h>.
* Automatically enable CPU_ENABLE_SSE (detect and enable SSE instructions)peter2002-09-075-2/+35
| | | | | | | | if compiling with I686_CPU as a target. CPU_DISABLE_SSE will prevent this from happening and will guarantee the code is not compiled in. I am still not happy with this, but gcc is now generating code that uses these instructions if you set CPUTYPE to p3/p4 or athlon-4/mp/xp or higher.
* Supposedly linux has added a 6th syscall arg register (%ebp). I am notpeter2002-09-071-0/+1
| | | | 100% sure if this is enough, but it will not harm anything.
* Add options COMPAT_AOUT to detect future bitrot.peter2002-09-071-0/+3
|
* Give this a self contained a.out coredump routine.peter2002-09-071-1/+60
| | | | XXX freebsd-aout coredumps for a linux-aout binary is a bit pointless.
* Zap the implementations of the i386-aout specific cpu_coredump function.peter2002-09-071-34/+0
| | | | Most of the non-i386 platforms had rather broken implementations anyway.
* Add a subclass of the PCI-PCI bridge driver that uses the PCIBIOS tojhb2002-09-061-2/+69
| | | | | | | | | | route interrupts if the child bus is described in the PCIBIOS interrupt routing table. For child busses that are in the routing table, they do not necessarily use a 'swizzle' on their pins on the parent bus to route interrupts for child devices. If the child bus is an embedded device then the pins on the child devices can be (and usually are) directly connected either to a PIC or to a Interrupt Router. This fixes PCIBIOS interrupt routing across PCI-PCI bridges for embedded devices.
* Add a function pci_probe_route_table() that returns true if our PCI BIOSjhb2002-09-063-0/+39
| | | | | supports interrupt routing and if the specified PCI bus is present in the routing table.
* Dump the $PIR table if booting verbose.jhb2002-09-062-0/+6
|
* - Add a pci_cfgintr_valid() function to see if a given IRQ is a validjhb2002-09-064-4/+69
| | | | | | | | | | | | IRQ for an entry in a PCIBIOS interrupt routing ($PIR) table. - Change pci_cfgintr() to except the current IRQ of a device as a fourth argument and to use that IRQ for the device if it is valid. - If an intpin entry in a $PIR entry has a link of 0, it means that that intpin isn't connected to anything that can trigger an interrupt. Thus, test the link against 0 to find invalid entries in the table instead of implicitly relying on the irqs field to be zero. In the machines I have looked at, intpin entries with a link of 0 often have the bits for all possible interrupts for PCI devices set.
* If we are using APIC_IO tell ACPI so it can route interrupts properly.jhb2002-09-061-0/+3
| | | | | This still doesn't work quite right because of other APIC_IO hacks in the i386 PCI code.
* Add support for printing out the contents of a PCI BIOS $PIR interruptjhb2002-09-062-4/+108
| | | | | routing table on the console. Eventually it will be printed during verbose boots.
* Prefer the physical bus number of the PCI bus as the unit of the pciXjhb2002-09-061-1/+1
| | | | device created.
* Test PCIbios.ventry against 0 to see if we found a PCIbios entry point,jhb2002-09-052-4/+4
| | | | | | | | | not the 'entry' member. The entry point is formed from both a base and a relative entry point. 'entry' is that relative offset. It is perfectly valid to have an entry point with a relative offset of 0. PCIbios.ventry is the virtual address of the entry point that takes both 'base' and 'entry' into account, thus it is the proper variable to test to see if we have an entry point or not.
* Move some variables to the BSS instead of explicitly zero'ing them. Thisjhb2002-09-051-3/+3
| | | | also makes all of the PCIbios variable be zero'd, not just the entry field.
* Statically compile pcn(4) into the install kernel vs. using as module.obrien2002-09-051-1/+1
| | | | | | | lnc(4) will attach to AMD PCnet/FAST NICs if pcn(4) does not attach. I.e. pcn(4) gets first chance. There is a problem however in that pcn(4) was moved out of the install kernel so that the module would be used. This however causes bad installs if one has an AMD PCnet/FAST NIC.
* Include <sys/systm.h> for the definition of offsetof() instead of dependingbde2002-09-051-0/+1
| | | | | on the definition being misplaced in <sys/types.h>. The definition probably belongs in <sys/stddef.h>.
* Include <sys/systm.h> for the definition of offsetof() instead of dependingbde2002-09-051-0/+1
| | | | | on the definition being misplaced in <sys/types.h>. The definition probably belongs in <sys/stddef.h>.
OpenPOWER on IntegriCloud