| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This should fix the 'too many RTC interrupts and statclock seems
broken after resume' problem.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
# 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.
|
|
|
|
| |
in !CPU_ENABLE_SSE case.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
- Maintain fpu state across signals.
- Save and restore FPU state properly in ucontext_t's.
Reviewed by: bde, deischen, julian
Approved by: -arch
|
|
|
|
|
|
|
|
| |
- Maintain fpu state across signals.
- Save and restore FPU state properly in ucontext_t's.
Reviewed by: deischen, julian
Approved by: -arch
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
includes of <sys/user.h> for its pollution only. <sys/user.h> wasn't
even used for its pollution here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
tabs not spaces.
|
|
|
|
| |
Reviewed by: davidxu@freebsd.org
|
|
|
|
|
|
| |
i386/conf/NOTES rather than the global conf/NOTES.
Suggested by: bde
|
|
|
|
| |
Reviewed by: phk
|
|
|
|
|
|
| |
as valid.
Submitted by: Michal Mertl <mime@traveller.cz>
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
|
|
|
| |
Brucified by: bde
|
|
|
|
| |
should be renamed to COMPAT_GZIPAOUT or something like that.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
filling in the POSIX parts, when doing the same thing in every port of
FreeBSD.
|
|
|
|
| |
with 'Fill in POSIX parts'. (Diff reduction.)
|
|
|
|
| |
<sys/user.h>.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
100% sure if this is enough, but it will not harm anything.
|
| |
|
|
|
|
| |
XXX freebsd-aout coredumps for a linux-aout binary is a bit pointless.
|
|
|
|
| |
Most of the non-i386 platforms had rather broken implementations anyway.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
supports interrupt routing and if the specified PCI bus is present in the
routing table.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
This still doesn't work quite right because of other APIC_IO hacks in
the i386 PCI code.
|
|
|
|
|
| |
routing table on the console. Eventually it will be printed during
verbose boots.
|
|
|
|
| |
device created.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
also makes all of the PCIbios variable be zero'd, not just the entry field.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
on the definition being misplaced in <sys/types.h>. The definition probably
belongs in <sys/stddef.h>.
|
|
|
|
|
| |
on the definition being misplaced in <sys/types.h>. The definition probably
belongs in <sys/stddef.h>.
|