| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
was clearing part of wrong thread structure..
|
|
|
|
|
|
|
| |
new -e option for that).
Feature requested by: Alex V. Belinsky <fozzy@kievweb.net.ua>
MFC after: 1 month
|
|
|
|
| |
Submitted by: bde
|
|
|
|
|
|
| |
world.
Submitted by: Brooks Davis <brooks@one-eyed-alien.net>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
of pointers to strings. These two arrays were fixed to the same size, but one
had an implicit zeroed trailer element, which was unused because the size was
used up by the ones before said zeroed trailer element. So the unused limb was
chopped off the over-sized-but-not-over-sized array, and everyone lived happily
ever after.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
ones with a default property of SA_IGNORE, and that it acquires and
releases the processes lock.
|
|
|
|
| |
100% sure if this is enough, but it will not harm anything.
|
| |
|
|
|
|
| |
restrict qualifiers on their prototypes in <wchar.h>.
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: davidxu@freebsd.org
|
|
|
|
| |
compile it statically.
|
| |
|
| |
|
| |
|
|
|
|
| |
XXX freebsd-aout coredumps for a linux-aout binary is a bit pointless.
|
|
|
|
| |
Most of the non-i386 platforms had rather broken implementations anyway.
|
| |
|
|
|
|
| |
XXX why does pecoff dump in a.out format?
|
|
|
|
| |
Submitted by: kris
|
|
|
|
| |
Reviewed by: kris
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
bridge driver.
|
|
|
|
|
|
|
|
| |
includes if_gre.h at all, but it does, without including ip.h before
that.
Poked by: peter
Pointy hat to: kdump(1)
|
|
|
|
| |
bpf support these days.
|
|
|
|
|
|
|
|
|
|
|
|
| |
in /etc/fstab. This isn't a real fix though and I'm still not sure
why it started failing. mount(8) breaks up the nfs args into seperate
repeated '-o option=value' arguments. But, the altflags variable that
we use to track things is incrementally built up each time we see the
next option and shows us the cumulative set of flags, not just the
flag that we are currently looking at. As a result, the strstr hack
for looking up flags in a giant -o opt=val,opt=val, etc string was failing
and causing a segfault. I do not know what changed recently that caused
this to suddenly break, but the code has been rather bogus for some time.
|
|
|
|
|
|
| |
error, due to an uninitialized variable.
Reviewed by: phk, archie
|
| |
|
|
|
|
| |
by atexit().
|
|
|
|
|
|
| |
page correctly and it wasn't doing what I thought it was.
Noticed by: Brooks Davis <brooks@one-eyed-alien.net>
|
|
|
|
|
| |
to grab Giant in isp_kthread so that msleep is *happy* that there's
no lock being passed to it (as tsleep turns out to be...)
|
|
|
|
|
| |
Approved by: ken
MFC after: 4 weeks
|
|
|
|
| |
be visible from outside of the module.
|
|
|
|
|
|
|
| |
PR: conf/42481
Submitted by: NINOMIYA Hideyuki <nin@jp.FreeBSD.org>
Approved by: imp
MFC after: 1 week
|
|
|
|
|
|
|
| |
regular expression instead of an obsolete regular expression.
Also, cross-reference re_format(7) instead of regex(3).
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
and MOBILE (RFC2004) IP tunnels.
Obrained from: NetBSD
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Obtained from: NetBSD (syssrc/sys/net/ethertypes.h, rev.1.13)
|
|
|
|
|
| |
This still doesn't work quite right because of other APIC_IO hacks in
the i386 PCI code.
|