| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
PR: bin/72394
Submitted by: Dan Nelson
Reviewed by: deischen
MFC after: 2 weeks
|
|
|
|
|
|
| |
- Update comments to newer style (space after #)
- Bring across various comment updates.
- Add AHC_REG_PRETTY_PRINT, ADAPTIVE_GIANT, and rue(4).
|
|
|
|
|
|
|
| |
other comments. Clarify that the next two things needed for SMP are
two lines.
- Expand mii abbreviation to miibus for clarity in the USB ethernet
comment.
|
|
|
|
|
| |
PR: bin/75656
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
is the case for most other sysctls in the System V IPC message queue
implementation.
PR: 75541
Submitted by: Sergiy Vyshnevetskiy <serg at vostok dot net>
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
| |
Submitted by: Kurt Jaeger <pi at complx dot LF dot net>
Approved by: ru
MFC after: 3 days
|
|
|
|
| |
before the check.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
generic bridge support was biting us more than it helped, whenever a new chipset
came out from a vendor and misprogramming it caused strange hangs or corruption.
[2] Add a large number of PCI IDs based on what the linux drivers support.
Note that the new PCI IDs haven't been tested, they're just *likely* to work.
In particular the VIA AGP 8x chipsets are concerning, due to lack of testing,
possible issues (kern/69953), and not having a nice "does this bridge say it
would do 8x" function. However, this shouldn't make the situation worse, since
these chips would have probed in the past anyway.
|
|
|
|
|
|
|
| |
more general than previous. It also lets me implement cancelable point
in thread library. Also in theory, umtx_lock and umtx_unlock can
be implemented by using umtx_wait and umtx_wake, all atomic operations
can be done in userland without kernel's casuptr() function.
|
|
|
|
|
| |
PR: 75616
Submitted by: n-kogane@syd.odn.ne.jp
|
|
|
|
| |
Submitted by: bde
|
|
|
|
|
|
|
|
|
|
|
| |
the regular ustar entry. The old code sometimes created
a too-long name that overflowed the ustar fields and triggered
an internal assertion failure. This version should be more
robust.
Thanks to: Michal Listos
Fixes: bin/74385
MFC after: 15 days
|
| |
|
|
|
|
|
|
|
| |
which is the very next line.
Submitted by: stefanf
MFC after: 3 days
|
|
|
|
|
| |
o Sticky bit is actually defined as S_ISTXT not S_ISVTX.
o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.
|
|
|
|
|
| |
PR: docs/75615
Submitted by: n-kogane@syd.odn.ne.jp
|
|
|
|
|
| |
If someone isn't running with a 64-bit time_t by now, they don't
track -CURRENT and would probably go to RELENG_5 vs. 6-CURRENT.
|
|
|
|
|
|
|
|
|
|
| |
connected to the Internet or systems that do not have a correctly
configured email subsystem. Now that the send-pr web interface has
antispam protection, mention that it is ok to use it for submitting
problem reports.
Ok by: linimon
Submitted by: Rob <spamrefuse@yahoo.com> on freebsd-doc
|
|
|
|
|
|
|
|
|
|
| |
1.17 -> 1.21 early-adopter/article.sgml
1.261 -> 1.269 hardware/common/dev.sgml
1.6 -> 1.7 hardware/common/intro.sgml
1.13 -> 1.14 hardware/i386/proc-i386.sgml
1.7 -> 1.9 hardware/ia64/proc-ia64.sgml
1.4 -> 1.5 hardware/pc98/proc-pc98.sgml
1.7 -> 1.8 share/sgml/release.dsl
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- add a HARDWARE section
- add a more descriptive NAME section
- update for recently imported Pinnacle PCTV support
- add Branko Lankester, the original author of the PCTV patches,
to the AUTHORS section
- bump .Dd
Thanks to all multimedia@ readers who sent me information about
their supported hardware!
MFC after: 1 week
|
|
|
|
|
|
| |
forget to actually install it in the segment register.
This may fix some of the weird panics seen when kernel VM
is heavily used.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
in a section of its own, not arbitrarily grouped in the hawking section
just because hawking sells it...
|
|
|
|
| |
queues lock.
|
|
|
|
| |
an mdoc error.
|
|
|
|
|
| |
object's lock. Therefore, the assertion that the page queues lock is held
can be removed from vm_page_io_start().
|
|
|
|
| |
Add lines for interest in 'ps' and 'pkill', where I'm more active.
|
|
|
|
|
| |
PR: 75574
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp> (original version)
|
|
|
|
| |
Add a note where to find the offical USB assigned numbers.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to remove a transaction from the async schedule. The previous method didn't
work well and led to the hardware writing to free'd buffers etc, as
it didn't always know that the transaction had been aborted.
Written after consultation with David Brownell who wrote the Linux
EHCI driver.
As part of this give the sqh structure a "previous" pointer.
MFC after: 1 week
|
|
|
|
|
| |
PR: 75581
Submitted by: Nobuyuki Koganemaru n-kogane@syd.odn.ne.jp (original version)
|
|
|
|
|
|
| |
addresses and scope IDs.
MFC after: 3 weeks
|
|
|
|
|
|
|
|
| |
rather than a softc pointer (with the bus structure at the start).
This is a non-functional change. It just helps when reading the code to
know that the ehci, ohci and uhci drivers share the bus structure, not the
entire softc.
|
|
|
|
|
|
|
|
|
|
|
|
| |
than a colon, so don't allow whitespace in program names. To be
consistent with hostnames, don't allow whitespace in the program
name specifiers in syslog.conf either.
(The first change is by Markus from the PR, the second is mine.)
PR: 68691
Submitted by: Markus Oestreicher <m.oe@x-trader.de>
MFC after: 3 weeks
|
| |
|
|
|
|
|
|
|
|
|
| |
of lock types in the kernel. This results in an increase of witness
data usage from ~145k to ~280k on i386 for kernels with
'options WITNESS'.
- Remove the unused witness malloc bucket.
Submitted by: Michal Mertl mime at traveller dot cz (1)
|
|
|
|
|
|
|
|
|
| |
message, i.e.:
geom: usage: geom <class> <command> [options]
PR: bin/71537
Submitted by: bugghy <bugghy@phenix.rootshell.be>
MFC after: 5 days
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Initialize error to 0 in ng_netflow_flow_add() (a nop change).
- Update cache statistics holding workqueue mutex.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
This allows boot to proceed on a real system until the issue
of calling back into certain OpenFirmware calls (e.g. finddevice)
in thread context is understood.
(this commit only affects psim users, of which I think I am the
only one...)
|
| |
|