| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
to archive_read_open and archive_write_open.
Thanks to: Antony Dovgal
|
|
|
|
|
|
|
| |
to archive_read_next_header so the
next error doesn't just get appended.
MFC after: 7 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Submitted by: Ken Smith <kensmith@cse.Buffalo.EDU>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fdcontrol/fdcontrol.c:
- Add const constraint to an intermediate value
which is not supposed to be changed elsewhere.
fdread/fdread.c:
- Use _devname in favor of devname to avoid name
conflicit.
- -1 is less than any positive number so in order
to get the block to function, we should get the
block a little earlier.
- Cast to remove signed when we are sure that a
return value is positive, or is compared with
an positive number (tracknumber of a floppy
disk is not likely to have UINT_MAX/2 anyway)
fdread/fdutil.c:
- Use more specific initializer
fdwrite/fdwrite.c:
- Use static on format_track since it's not
referenced in other places.
- Use const char* to represent string constant.
Bump WARNS accordingly.
|
|
|
|
|
|
| |
WARNS comes before CFLAGS
This reduces diff against my local branch.
|
|
|
|
|
|
|
|
|
|
| |
- Introduce another ng_ether(4) callback ng_ether_link_state_p, which
is called from if_link_state_change(), every time link is changed.
- In ng_ether_link_state() send netgraph control message notifying
of link state change to a node connected to "lower" hook.
Reviewed by: sam
MFC after: 2 weeks
|
|
|
|
| |
pthread_rwlock_timedwrlock.
|
|
|
|
| |
Bump doc date.
|
|
|
|
|
|
|
|
|
| |
place device objects in \ (in this case, PCI links.) Work around this by
starting our probe from \. To avoid attaching system scope objects,
explicitly skip them. (I think it's an ACPI-CA bug that \_SB and \_TZ have
device and thermal object types.) Thanks to pjd@ for testing.
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
| |
This example caused me to incorrectly believe that you must use the
generic device nodes when you can in fact use either. It's often better
to use the driver specific node.
|
|
|
|
| |
kbd1 might be something else.
|
|
|
|
|
| |
every process exist, even if procfs isn't mounted. And one of those
mutexes is Giant. No immediate thoughts on fixing this.
|
|
|
|
|
|
|
|
| |
before deciding to do more expensive locking to account for process
exit. This acceptable minor race avoids two mutex operations in
that highly common case of accounting not being enabled.
MFC after: 2 weeks
|
|
|
|
|
| |
we loop through all the list of NICs (struct ifnet), holding the lock on
it and then do a name lookup with ifunit() whilst holding it.
|
|
|
|
| |
an explicit bcopy() -- it probably does a better job.
|
|
|
|
|
|
|
| |
device.
Submitted by: Martin Nilsson <martin@gneto.com>
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to: Charles Smeijer for getting me my AS600.
|
|
|
|
|
|
|
|
|
| |
descriptions of items from each other and have related things appear
in the same nesting 'level'.
The .Fn function/macro, and bump document date.
Reviewed by: jkoshy
|
|
|
|
|
|
| |
Remove outdated info on install media.
Submitted by: "William H. Magill" <magill@mcgillsociety.org>
|
|
|
|
|
| |
PR: kern/75923
Submitted by: Matthew D. Fuller <fullermd@over-yonder.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Fix the MP Table pci bridge drivers to not probe the configuration table
unless we actually have one. Machines using a default configuration do
not have such a table.
- Only allow default configuration types of 5 (ISA + PCI) and 6 (EISA +
PCI) as the others are not likely to work. Types 1 through 4 use an
external APIC (probably with 80486 processors) which we certainly do not
support, and type 7 uses an MCA bus which has not been tested with the
new MP Table code.
- Correct the fact that the single I/O APIC in a default configuration has
an ID of 2, not 0.
- Fix off by one errors in setting the bus types from the default_data[]
arrays for default configurations.
- Explicitly configure each of the 16 interrupt pins on the sole I/O APIC
when using a default configuration. This is especially helpful for type
6 (EISA + PCI) since the EISA interrupts need to have their polarity
programmed based on the values in the ELCR.
Much thanks to the submitter and tester who endured several rounds of
testing to get this fixed.
MFC after: 1 week
Tested by: Georg Schwarz georg dot schwarz at freenet dot de
|
| |
|
|
|
|
|
|
|
| |
Make sure we don't confuse the reader by claiming it is.
PR: docs/75615
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
|
| |
|
|
|
|
| |
argument description list.
|
|
|
|
|
|
| |
- List of struct statfs fields that are related to file systems, much
like the list in stat.2 for the userlevel `struct stat'.
- Bump document date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
complementing the existing special case of a not existing /dev prefix
with the recognition of an already existing /dev prefix.
This implicitly solves the following two issues related to working on
GEOM devices /dev/foo/bar (which have the GEOM provider name "foo/bar")
with the expected commands like "bsdlabel /dev/foo/bar":
1. the error "Geom not found" when trying to write or edit the BSD
label (because previously the incorrect GEOM name "bar" instead of
"foo/bar" was derived from "/dev/foo/bar").
2. the multiple times reported "magically introduced" partition offset
of 63 blocks and the resulting errors like "partition extends past
end of unit" and "partition c doesn't start at 0!".
This implicitly resulted because bsdlabel(8) determines the "MBR
offset" via GEOM and (intentionally) silently falls back to an offset
of 0 if it could not be queried (which is the case if the name was
incorrectly derived).
Usually (at least on PCs) the offset for the first slice is 63 blocks
and bsdlabel(8) automatically subtracts them from the absolute
offsets in the read on-disk BSD label, resulting in the display of an
effective offset of 0. If the GEOM query fails, the assumed offset of
0 is subtracted and an incorrect effective offset of 63 is displayed
and tried to be worked upon.
Reviewed by: pjd
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
- Apply __unused on unused parameters
- Use const where suitable
- Use PRIu64 instead of the deprecated %q
- Bump WARNS to 6
|
| |
|
| |
|
|
|
|
|
|
| |
list for the valid flag values. This way, if VFS_UNMOUNT(9) supports
more flags in the future, adding a single list item is going to be
easy and all the flags are going to be in one place.
|
| |
|
|
|
|
| |
Approved by: phk
|
|
|
|
|
|
| |
(since revision 1.173 of src/sys/sys/mount.h).
Update its prototype, the argument list description and bump the date.
|
|
|
|
|
| |
Submitted by: Hideyuki KURASHINA <rushani@FreeBSD.org>
MFC after: 1 week
|
|
|
|
|
|
| |
macro arguments expected by SYSCALL_MODULE().
MFC after: 3 days
|
|
|
|
| |
Noticed by: krion
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
note that these versions numbers refer to moddepend, not the current
module.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
cuts to the chase and fills in a provided s/g list. This is meant to optimize
out the cost of the callback since the callback doesn't serve much purpose for
mbufs since mbuf loads will never be deferred. This is just for amd64 and
i386 at the moment, other arches will be coming shortly.
|
| |
|
|
|
|
|
| |
Submitted by: Peter Jeremy <PeterJeremy@optushome.com.au>
MFC after: 5 days
|
|
|
|
|
| |
PERC 3 controllers. This is needed to keep the PM code from powering them
down.
|