summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Drop the -I/usr/include (or any of its variants) from CFLAGS.ru2005-11-291-14/+0
| | | | | | | The sys/sys/stddef.h is here for some time now to fulfil the kernel needs. It also was not reliable due to the exists(@) check: in an empty module directory, "make depend; mv .depend .depend~; make depend" ran mkdep(1) with different arguments.
* Garbage-collect now unused struct _ipfw_insn_pipe and flush_pipe_ptrs(),glebius2005-11-294-45/+6
| | | | | thus removing a few XXXes. Document the ABI breakage in UPDATING.
* New SiS support.brueffer2005-11-291-1/+3
|
* Add notes about ATI IXP audio controller.ariff2005-11-291-0/+2
|
* Add support for the i855GM, tested by an r300 user.anholt2005-11-292-2/+12
|
* Check value returned by g_read_data(9), otherwise we can end in panic(9)sobomax2005-11-291-0/+3
| | | | | | if read error happens. MFC after: 1 week
* Remove MNT_NODEV mount option. In RELENG_6, MNT_NODEV was a no-op.rodrigc2005-11-293-4/+0
| | | | | | The presence of MNT_NODEV was confusing the am-utils autoconf scripts. PR: conf/79715
* First step in removing welding between ipfw(4) and dummynet.glebius2005-11-292-288/+285
| | | | | | | | | | | | | | | | | | | | | o Do not use ipfw_insn_pipe->pipe_ptr in locate_flowset(). The _ipfw_insn_pipe isn't touched by this commit to preserve ABI compatibility. o To optimize the lookup of the pipe/flowset in locate_flowset() introduce hashes for pipes and queues: - To preserve ABI compatibility utilize the place of global list pointer for SLIST_ENTRY. - Introduce locate_flowset(queue nr) and locate_pipe(pipe nr). o Rework all the dummynet code to deal with the hashes, not global lists. Also did some style(9) changes in the code blocks that were touched by this sweep: - Be conservative about flowset and pipe variable names on stack, use "fs" and "pipe" everywhere. - Cleanup whitespaces. - Sort variables. - Give variables more meaningful names. - Uppercase and dots in comments. - ENOMEM when malloc(9) failed.
* Update DRM to CVS snapshot as of 2005-11-28. Notable changes:anholt2005-11-2879-1722/+3509
| | | | | | | | | | | | | - S3 Savage driver ported. - Added support for ATI_fragment_shader registers for r200. - Improved r300 support, needed for latest r300 DRI driver. - (possibly) r300 PCIE support, needs X.Org server from CVS. - Added support for PCI Matrox cards. - Software fallbacks fixed for Rage 128, which used to render badly or hang. - Some issues reported by WITNESS are fixed. - i915 module Makefile added, as the driver may now be working, but is untested. - Added scripts for copying and preprocessing DRM CVS for inclusion in the kernel. Thanks to Daniel Stone for getting me started on that.
* Fix SiS SATA support, the SATA registers was off.sos2005-11-283-44/+243
| | | | | | Add support for SiS metadata. HW donated by: obrien
* Move zero copy statistics structure before sosend_copyin().rwatson2005-11-281-15/+15
| | | | | MFC after: 1 month Reported by: tinderbox, sam
* If we get a stray interrupt, return after logging it. In the extremelyjhb2005-11-282-0/+2
| | | | | | | | | | rare case of a stray interrupt to an unregistered source (such as a stray interrupt from the 8259As when using APIC), this could result in a page fault when it tried to walk the list of interrupt handlers to execute INTR_FAST handlers. This bug was introduced with the intr_event changes, so it's not present in 5.x or 6.x. Submitted by: Mark Tinguely tinguely at casselton dot net
* When checking to see if a process has exceeded its time limit, flag thejhb2005-11-281-2/+2
| | | | | | | | | | | | | | | process as over the limit when its time is >= to the limit rather than > the limit. Technically, if p->p_rux.rux_runtime.sec == p->p_pcpulimit and p->p_rux.rux_runtime.frac == 0, the process hasn't exceeded the limit yet. However, having the fraction exactly equal to 0 is rather rare, and it is not worth the overhead to handle that edge case. With just the > comparison, the process would have to exceed its limit by almost a second before it was killed. PR: kern/83192 Submitted by: Maciej Zawadzinski mzawadzinski at gmail dot com Reviewed by: bde MFC after: 1 week
* s/Advance/Avance/joel2005-11-281-1/+1
|
* No one cares about when the manual page first appeared. Mention when thejoel2005-11-289-27/+27
| | | | driver appeared instead.
* Break out functionality in sosend() responsible for building mbufrwatson2005-11-281-141/+170
| | | | | | | | | | chains and copying in mbufs from the body of the send logic, creating a new function sosend_copyin(). This changes makes sosend() almost readable, and will allow the same logic to be used by tailored socket send routines. MFC after: 1 month Reviewed by: andre, glebius
* Remove two lines of debugging output that accidentally snuck into therwatson2005-11-281-2/+0
| | | | commit to fix up kvm support for netstat -m.
* Version 600004 is better than 700000 given other changes that are inimp2005-11-288-8/+8
| | | | | | | the pipeline. We had to bump the version for 600004 because the old parser got confused and generated bogus output. Approved by: ru@
* Add AUTHORS section.joel2005-11-287-7/+28
|
* 600004 is a better new version than 700000 based on some future commits toimp2005-11-281-1/+1
| | | | | | | | this file. With ru@'s approval, change it to this version. In this case we had to bump the version because the old parser would choke on | in the new 'or' syntax and consider that a device. Approved by: ru@
* Autogenerate hardware notes for snd_atiixp(4).brueffer2005-11-283-0/+5
|
* Xref snd_atiixp.4brueffer2005-11-281-1/+2
|
* Restore the previous state after a FILL operation in properties_read()jhb2005-11-281-8/+15
| | | | | | | | | | | rather than forcing the state to LOOK. If we are in the middle of parsing a line when we have to do a FILL we would have lost any token we were in the middle of parsing and would have treated the next character as being at the start of a new line instead. PR: kern/89181 Submitted by: Antony Mawer gnats at mawer dot org MFC after: 1 week
* Follow the rules for the .Dd macro use: use unabbreviated month names.jkoshy2005-11-281-1/+1
| | | | Submitted by: ru
* Fix two identical harmless typos in ata error messages:keramida2005-11-281-2/+2
| | | | | | | | | s/issueing/issuing/ PR: kern/89481 Submitted by: John Nielsen Approved by: sos MFC after: 1 week
* Take if_baudrate from the parent. This fixes problem with SNMPglebius2005-11-281-0/+1
| | | | daemons reporting zero speed for vlan(4) interfaces.
* Rearranged the polynomial evaluation some more to reduce dependencies.bde2005-11-281-8/+20
| | | | | | | | | | | | | | | | | | | | | Instead of echoing the code in a comment, try to describe why we split up the evaluation in a special way. The new optimization is mostly to move the evaluation of w = z*z later so that everything else (except z = x*x) doesn't have to wait for w. On Athlons, FP multiplication has a latency of 4 cycles so this optimization saves 4 cycles per call provided no new dependencies are introduced. Tweaking the other terms in to reduce dependencies saves a couple more cycles in some cases (more on AXP than on A64; up to 8 cycles out of 56 altogether in some cases). The previous version had a similar optimization for s = z*x. Special optimizations like these probably have a larger effect than the simple 2-way vectorization permitted (but not activated by gcc) in the old version, since 2-way vectorization is not enough and the polynomial's degree is so small in the float case that non-vectorizable dependencies dominate. On an AXP, tanf() on uniformly distributed args in [-2pi, 2pi] now takes 34-55 cycles (was 39-59 cycles).
* Fix a bug in previous revision: skip LINT if it exists, not NOTESru2005-11-281-1/+1
| | | | (the source for LINT), as I initially intended.
* universe: don't attempt to compile DEFAULTS and don't compile LINT twice.ru2005-11-281-1/+2
|
* Fixed about 50 million errors of infinity ulps and about 3 million errorsbde2005-11-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | of between 1.0 and 1.8509 ulps for lgammaf(x) with x between -2**-21 and -2**-70. As usual, the cutoff for tiny args was not correctly translated to float precision. It was 2**-70 but 2**-21 works. Not as usual, having a too-small threshold was worse than a pessimization. It was just a pessimization for (positive) args between 2**-70 and 2**-21, but for the first ~50 million (negative) args below -2**-70, the general code overflowed and gave a result of infinity instead of correct (finite) results near 70*log(2). For the remaining ~361 million negative args above -2**21, the general code gave almost-acceptable errors (lgamma[f]() is not very accurate in general) but the pessimization was larger than for misclassified tiny positive args. Now the max error for lgammaf(x) with |x| < 2**-21 is 0.7885 ulps, and speed and accuracy are almost the same for positive and negative args in this range. The maximum error overall is still infinity ulps. A cutoff of 2**-70 is probably wastefully small for the double precision case. Smaller cutoffs can be used to reduce the max error to nearly 0.5 ulps for tiny args, but this is useless since the general algrorithm for nearly-tiny args is not nearly that accurate -- it has a max error of about 1 ulp.
* Add manual page for snd_atiixp(4) and hook it up to the build.joel2005-11-282-0/+90
| | | | Reviewed by: ru
* Apply arch= selection to the qandatoc mode. This fixeshrs2005-11-281-0/+43
| | | | | | link generation with no actual target. Reported by: Tim Witthoeft (tim.witthoeft at gmail.com)
* Exploit skew-symmetry to avoid an operation: -sin(x-A) = sin(A-x). Thisbde2005-11-282-4/+4
| | | | | | | | gives a tiny but hopefully always free optimization in the 2 quadrants to which it applies. On Athlons, it reduces maximum latency by 4 cycles in these quadrants but has usually has a smaller effect on total time (typically ~2 cycles (~5%), but sometimes 8 cycles when the compiler generates poor code).
* Try to use the "proximity" (~) operator consistently in commentsbde2005-11-282-8/+10
| | | | | | | (x ~<= a, not x <= ~a). This got messed up in some places when the comments were moved from e_rem_pio2f.c. Added my (non-)copyright.
* Changed spelling of the request-to-inline macro name to match the changebde2005-11-282-4/+6
| | | | | | | | | of the function name. Added my (non-)copyright. In k_tanf.c, added the first set of redundant parentheses to control grouping which was claimed to be added in the previous commit.
* Use only double precision for "kernel" cosf and sinf (except forbde2005-11-286-71/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | returning float). The functions are renamed from __kernel_{cos,sin}f() to __kernel_{cos,sin}df() so that misuses of them will cause link errors and not crashes. This version is an almost-routine translation with no special optimizations for accuracy or efficiency. The not-quite-routine part is that in __kernel_cosf(), regenerating the minimax polynomial with double precision coefficients gives a coefficient for the x**2 term that is not quite -0.5, so the literal 0.5 in the code and the related `hz' variable need to be modified; also, the special code for reducing the error in 1.0-x**2*0.5 is no longer needed, so it is convenient to adjust all the logic for the x**2 term a little. Note that without extra precision, it would be very bad to use a coefficient of other than -0.5 for the x**2 term -- the old version depends on multiplication by -0.5 being infinitely precise so as not to need even more special code for reducing the error in 1-x**2*0.5. This gives an unimportant increase in accuracy, from ~0.8 to ~0.501 ulps. Almost all of the error is from the final rounding step, since the choice of the minimax polynomials so that their contribution to the error is a bit less than 0.5 ulps just happens to give contributions that are significantly less (~.001 ulps). An Athlons, for uniformly distributed args in [-2pi, 2pi], this gives overall speed increases in the 10-20% range, despite giving a speed decrease of typically 19% (from 31 cycles up to 37) for sinf() on args in [-pi/4, pi/4].
* Remove commented out reference to posix4/mqueue.h. It hasn't been installedrodrigc2005-11-281-2/+1
| | | | | for 3 years, and now we have another (working) implementation of POSIX message queues elsewhere in the source tree.
* mqueue.h has been superceded by sys/mqueue.h thanks to David Xu's work.scottl2005-11-281-77/+0
| | | | Submitted by: dolt
* Use a separate synopsis line for -u as devinfo will ignore otherjkoshy2005-11-281-3/+7
| | | | options when -u is specified. Xref device(9) and devclass(9).
* - Allow duplicate "machine" directives with the same arguments.ru2005-11-2723-62/+10
| | | | - Move existing "machine" directives to DEFAULTS.
* Fix a stupid compiler warining, remove a redundant line.davidxu2005-11-271-1/+1
|
* Reduction.ru2005-11-272-2/+0
|
* Make config(8) understand ORed dependecies in "files*" andru2005-11-2718-264/+139
| | | | improve tracking of known devices. Bump config(8) version.
* Document 82571 and 82572 support.brueffer2005-11-271-3/+3
| | | | MFC after: 3 days
* Add a CAVEATS section that mentions missing RAID5 support.brueffer2005-11-271-1/+4
| | | | MFC after: 3 days
* The ohci driver's processing of completed transfer descriptors (TDs)iedowse2005-11-272-31/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | appeared to rely on all kinds of non-guaranteed behaviours: the transfer abort code assumed that TDs with no interrupt timeout configured would end up on the done queue within 20ms, the done queue processing assumed that all TDs from a transfer would appear at the same time, and there were access-after-free bugs triggered on failed transfers. Attempt to fix these problems by the following changes: - Use a maximum (6-frame) interrupt delay instead of no interrupt delay to ensure that the 20ms wait in ohci_abort_xfer() is enough for the TDs to have been taken off the hardware done queue. - Defer cancellation of timeouts and freeing of TDs until we either hit an error or reach the final TD. - Remove TDs from the done queue before freeing them so that it is safe to continue traversing the done queue. This appears to fix a hang that was reproducable with revision 1.67 or 1.68 of ulpt.c (earlier revisions had a different transfer pattern). With certain HP printers, the command "true > /dev/ulpt0" would cause ohci_add_done() to spin because the done queue had a loop. The list corruption was caused by a 3-TD transfer where the first TD completed but remained on the internal host controller done queue because it had no interrupt timeout. When the transfer timed out, the TD got freed and reused, so it caused a loop in the done queue when it was inserted a second time from a different transfer. Reported by: Alex Pivovarov MFC after: 1 week
* Change filesystem name from mqueue to mqueuefs for style consitent,davidxu2005-11-271-2/+2
| | | | sort LINKS list.
* Change filesystem name from mqueue to mqueuefs for style consistent.davidxu2005-11-272-3/+3
| | | | Suggested by: rwatson
* Clarify a comment to make it clear that it is NO_NIS that "If it is set"keramida2005-11-271-2/+2
| | | | | | | | | | | refers to and add extra '#' comment characters at the beginning of two lines that started with TABs, to avoid warnings like: "/etc/make.conf", line 128: Unassociated shell command "# If set, you might need to adopt your" "/etc/make.conf", line 129: Unassociated shell command "# nsswitch.conf(5) and remove `nis' entries." PR: misc/89423 Submitted by: Scot W. Hetzel
* Support for ATI IXP 200 / 300 / 400 series audio controllers.ariff2005-11-276-1/+1221
|
OpenPOWER on IntegriCloud