summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Renumber clauses to reduce diffs to other versionsemaste2013-05-28100-100/+100
| | | | | NetBSD, OpenBSD, and Android's Bionic number the clauses 1 through 3, so follow suit to make comparison easier.
* Remove the advertising clause from the Regents of the University ofemaste2013-05-2810-50/+10
| | | | California's license, per the letter dated July 22, 1999.
* Fix warnings from newer clang versions about constexpr member functionsdim2013-05-281-4/+4
| | | | | | | | | | not being implicitly const in libc++'s <chrono> header. The warnings have been introduced because of new language rules recently adopted by the C++ WG. More info: <http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3598.html> MFC after: 3 days
* Revert r251023 until a more proper solution is foundhselasky2013-05-282-32/+0
| | | | | | for ATI based USB controllers. MFC after: 1 week
* Added missing SCSI quirks from r241784smh2013-05-282-45/+209
| | | | | | | | | | | | | | | | | Re-ordered SSD quirks alphabetically so they are easier to maintain. Removed my email and PR reference from comments on each quirk. Added quirks for more SSDs: * Crucial M4 * Corsair Force GT * Intel 520 Series * Kingston E100 Series * Samsung 830 Series Reviewed by: pjd (mentor) Approved by: pjd (mentor) MFC after: 1 week
* - Fix wording. [1]markj2013-05-281-4/+4
| | | | | | | | - Improve the descriptions in the FILES section. [2] Reported by: Jason McIntyre [1] Obtained from: NetBSD [2] MFC after: 3 days
* During buildkernel, print a banner before building modules.des2013-05-281-2/+9
|
* mdoc: silence a few mandoc lint warnings.joel2013-05-282-5/+4
|
* Remove redundant checks.tuexen2013-05-281-6/+6
| | | | MFC after: 2 weeks
* Fix cexp regression tests that have an infinite real part. The signs of thetijl2013-05-281-12/+26
| | | | | | | | result depend on the cosine and sine of the imaginary part. Small values are used in the new tests such that cosine and sine are well defined. Reviewed by: das
* The getcontext() from the __fillcontextx() call in thekib2013-05-2811-9/+78
| | | | | | | | | | | | | | | | | | | | | | | | | check_deferred_signal() returns twice, since handle_signal() emulates the return from the normal signal handler by sigreturn(2)ing the passed context. Second return is performed on the destroyed stack frame, because __fillcontextx() has already returned. This causes undefined and bad behaviour, usually the victim thread gets SIGSEGV. Avoid nested frame and the need to return from it by doing direct call to getcontext() in the check_deferred_signal() and using a new private libc helper __fillcontextx2() to complement the context with the extended CPU state if the deferred signal is still present. The __fillcontextx() is now unused, but is kept to allow older libthr.so to be used with the new libc. Mark __fillcontextx() as returning twice [1]. Reported by: pgj Pointy hat to: kib Discussed with: dim Tested by: pgj, dim Suggested by: jilles [1] MFC after: 1 week
* Style(9)kargl2013-05-271-1/+1
| | | | | Approved by: das (implicit) Reported by: jh
* Change the closeallfds() routine to use closefrom() when it isgad2013-05-272-8/+29
| | | | | | | | | | | | | | available (closefrom() was added to FreeBSD in 8.0-release). The selection is made at compile-time, as I still compile a FreeBSD-based version of lpr&friends on other platforms. While testing I out that (at least on my system) lpd has been closing 11095 fd's, when there are only 6 fd's open. The old code took 120 times more clocktime than calling closefrom(). (although that was still less than 2/1000-ths of a second!) Reviewed by: jilles MFC after: 2 weeks
* cap_rights_limit(2): CAP_ACCEPT also permits accept4(2).jilles2013-05-271-1/+3
|
* * Update polynomial coefficients.kargl2013-05-271-33/+30
| | | | | | | | * Use ENTERI/RETURNI to allow the use of FP_PE on i386 target. Reviewed by: das (and bde a long time ago) Approved by: das (mentor) Obtained from: bde (polynomial coefficients)
* Partially apply the capitalization of the heading word of the sequencekib2013-05-271-3/+3
| | | | | | | and fix typo. Sponsored by: The FreeBSD Foundation MFC after: 1 week
* Use slightly more idiomatic expression to get the address of array.kib2013-05-273-3/+3
| | | | | | Tested by: dim, pgj Sponsored by: The FreeBSD Foundation MFC after: 1 week
* The _MC_HASFPXSTATE and _MC_IA32_HASFPXSTATE flags have the same bitkib2013-05-271-1/+1
| | | | | | | | | value on purpose, but the ia32 context handling code is logically more correct to use the _MC_IA32_HASFPXSTATE name for the flag. Tested by: dim, pgj Sponsored by: The FreeBSD Foundation MFC after: 1 week
* The ia32_get_mcontext() does not need to set PCB_FULL_IRET. Thekib2013-05-271-1/+0
| | | | | | | | | usermode context state is not changed by the get operation, and get_mcontext() does not require full iret as well. Tested by: dim, pgj Sponsored by: The FreeBSD Foundation MFC after: 1 week
* When reporting the fault details, also print %rsp.kib2013-05-271-2/+2
| | | | | Sponsored by: The FreeBSD Foundation MFC after: 1 week
* When handling an exception from the attempt from loading the faultingkib2013-05-272-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | context on return from the trap handler, re-enable the interrupts on i386 and amd64. The trap return path have to disable interrupts since the sequence of loading the machine state is not atomic. The trap() function which transfers the control to the special handler would enable the interrupt, but an iret loads the previous eflags with PSL_I clear. Then, the special handler calls trap() on its own, which now sees the original eflags with PSL_I set and does not enable interrupts. The end result is that signal delivery and process exiting code could be executed with interrupts disabled, which is generally wrong and triggers several assertions. For amd64, the interrupts are enabled conditionally based on PSL_I in the eflags of the outer frame, as it is already done for doreti_iret_fault. For i386, the interrupts are enabled unconditionally, the ast loop could have opened a window with interrupts enabled just before the iret anyway. Reported and tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 1 week
* Fix some regressions caused by the switch from gcc to clang. The fixesdas2013-05-2721-59/+78
| | | | | | | | | | are workarounds for various symptoms of the problem described in clang bugs 3929, 8100, 8241, 10409, and 12958. The regression tests did their job: they failed, someone brought it up on the mailing lists, and then the issue got ignored for 6 months. Oops. There may still be some regressions for functions we don't have test coverage for yet.
* Workaround for for a problem seen with ATI Technologies EHCIhselasky2013-05-272-0/+32
| | | | | | | | | | | | | | | | controller hardware most likely present on UHCI chipsets aswell. The bug manifests itself when issuing isochronous transfers and bulk transfers towards the same device simultaneously. From time to time it happens that either the completion IRQ was missing or that the completion IRQ was happening before the ITD/SITD was completely written back to memory. The workaround assumes that double buffered isochronous transfers are used, and that a second interrupt is generated at the beginning of the next isochronous transfer to complete the previous one. Possibly skipping the interrupt at the last isochronous frame is possible, but will then break single buffered isochronous transfers. For now we can live with some extra interrupts. MFC after: 1 week
* Fix ONFI chip detection.gber2013-05-272-2/+2
| | | | Submitted by: Alexander Fedorov <alexander.fedorov@rtlservice.com>
* Add DTS for AM335x EVM with properly muxed PWM and LCD pins, andgonzo2013-05-271-0/+180
| | | | LCD panel description
* Add PWM and LCDC nodes to base DTS for AM335x-based devicesgonzo2013-05-271-0/+23
|
* AM335x LCD controller driver with syscons supportgonzo2013-05-274-0/+1518
| | | | | | Limitations: - Raster mode only - 24 and 32 bpp only
* Add PWM module driver for AM335x. Only eCAS subsystem is supportedgonzo2013-05-273-0/+319
| | | | | Export function to configure eCAS submodule from another drivers. It's used to control LCD panel backlight on AM335x EVM.
* Add SCM registers definitions for AM335x platformgonzo2013-05-271-0/+38
|
* Add clock definitions for LCD controller and PWM modulegonzo2013-05-272-3/+99
|
* Migrate ath(4) to now use if_transmit instead of the legacy if_startadrian2013-05-264-219/+243
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and if queue mechanism; also fix up (non-11n) TX fragment handling. This may result in a bit of a performance drop for now but I plan on debugging and resolving this at a later stage. Whilst here, fix the transmit path so fragment transmission works. The TX fragmentation handling is a bit more special. In order to correctly transmit TX fragments, there's a bunch of corner cases that need to be handled: * They must be transmitted back to back, in the same order.. * .. ie, you need to hold the TX lock whilst transmitting this set of fragments rather than interleaving it with other MSDUs destined to other nodes; * The length of the next fragment is required when transmitting, in order to correctly set the NAV field in the current frame to the length of the next frame; which requires .. * .. that we know the transmit duration of the next frame, which .. * .. requires us to set the rate of all fragments to the same length, or make the decision up-front, etc. To facilitate this, I've added a new ath_buf field to describe the length of the next fragment. This avoids having to keep the mbuf chain together. This used to work before my 11n TX path work because the ath_tx_start() routine would be handed a single mbuf with m_nextpkt pointing to the next frame, and that would be maintained all the way up to when the duration calculation was done. This doesn't hold true any longer - the actual queuing may occur at any point in the future (think ath_node TID software queuing) so this information needs to be maintained. Right now this does work for non-11n frames but it doesn't at all enforce the same rate control decision for all frames in the fragment. I plan on fixing this in a followup commit. RTS/CTS has the same issue, I'll look at fixing this in a subsequent commit. Finaly, 11n fragment support requires the driver to have fully decided what the rate scenario setup is - including 20/40MHz, short/long GI, STBC, LDPC, number of streams, etc. Right now that decision is (currently) made _after_ the NAV field value is updated. I'll fix all of this in subsequent commits. Tested: * AR5416, STA, transmitting 11abg fragments * AR5416, STA, 11n fragments work but the NAV field is incorrect for the reasons above. TODO: * It would be nice to be able to queue mbufs per-node and per-TID so we can only queue ath_buf entries when it's time to assemble frames to send to the hardware. But honestly, we should just do that level of software queue management in net80211 rather than ath(4), so I'm going to leave this alone for now. * More thorough AP, mesh and adhoc testing. * Ensure that net80211 doesn't hand us fragmented frames when A-MPDU has been negotiated, as we can't do software retransmission of fragments. * .. set CLRDMASK when transmitting fragments, just to ensure.
* Unbreak ia64 tinderbox: 64-bit support was made conditional uponmarcel2013-05-261-13/+4
| | | | | | | __amd64__, and thus limited. Eliminate 2 trivial conditionals by casting the 64-bit integral, holding an address, via (uintptr_t) to (void *) and replace the last remaining check for __amd64__ with a check for __LP64__ instead.
* s/recieve/receiveschweikh2013-05-261-1/+1
|
* Remove backwards compat layer which was added in r71419 (in 2001).eadler2013-05-261-11/+0
| | | | | | This change is not intended for MFC. Reviewed by: peter
* Pull in r182656 from upstream llvm trunk:dim2013-05-261-1/+4
| | | | | | | | | | | | | | | | | | LoopVectorize: LoopSimplify can't canonicalize loops with an indirectbr in it, don't assert on those cases. Fixes PR16139. This should fix clang assertion failures when optimizing at -O3, similar to: Assertion failed: (TheLoop->getLoopPreheader() && "No preheader!!"), function canVectorize, file contrib/llvm/lib/Transforms/Vectorize/LoopVectorize.cpp, line 2171. Reported by: O. Hartmann <ohartman@zedat.fu-berlin.de> PR: ports/178332, ports/178977 MFC after: 3 days
* Move libmd.so.5 to the proper place and add missing lib32 entry.antoine2013-05-261-1/+2
|
* Rework the comment I initially wrote when SHLIB_LDSCRIPT was introduced.jlh2013-05-251-9/+14
| | | | | | The build system is really intricate and I had a hard time to remind the whole picture even when reading my own words. This one will hopefully be better.
* Make the malloc(3) family of functions weak and make their non-weakmarcel2013-05-253-0/+64
| | | | | | | | | | | | | | implementations visible for use by applications. The functions $F that are now weak symbols are: allocm, calloc, dallocm, free, malloc, malloc_usable_size, nallocm, posix_memalign, rallocm, realloc, sallocm The non-weak implementations of $F are exported as __$F. Submitted by: stevek@juniper.net Reviewed by: jasone@, kib@ Approved by: jasone@ (jemalloc) Obtained from: juniper Networks, Inc
* Add C11 macros CMPLX(), CMPLXF() and CMPLXL().ed2013-05-251-0/+12
| | | | | | Clang allows us to initialize complex numbers using an array initializer, casted to a complex type. GCC has a builtin called __builtin_complex().
* Add missing #includes, to keep Clang silent.ed2013-05-253-0/+3
|
* Fix some statical clang analyzer warnings.hselasky2013-05-253-5/+1
|
* Fix <uchar.h> in for C++11.ed2013-05-252-3/+15
| | | | | | | | | | | It turns out that in C++11, char16_t and char32_t are built-in types; language keywords. Just fix this by putting traditional _*_T_DECLARED blocks around the definitions. We'll just predefine these in <sys/_types.h>. This also opens up the possibility to define char16_t in other header files, if ever needed (e.g. if we would gain a <ctype.h> for char16_t/char32_t).
* Prevent shadowing.ed2013-05-256-10/+10
| | | | | The name line_number seems to be used as a function parameter name for one of the Lex functions. Change the name to linenumber.
* sigreturn(2): Remove ancient compatibility warning about 4.2BSD.jilles2013-05-251-4/+0
| | | | The HISTORY subsection still says that sigreturn() was added in 4.3BSD.
* Make some tiny improvements to iconv_open().ed2013-05-251-21/+15
| | | | | | | | | - Remove an unneeded variable. - Fix whitespace bugs. - Fix typoes in comment. - Improve string handling a bit. Don't handroll strstr() and don't terminate a strdup()'ed string. Instead, simply strndup() the part we need.
* Only call free() on something we allocated.ed2013-05-251-2/+2
| | | | | | | If we were already provided a struct _citrus_iconv (e.g. through iconv_open_into()), we should not call free() in case io_init_context() fails. Instead, call it on the pointer of the allocated object, which will be NULL in case of iconv_open_into().
* Revert r250972 to fix build.gjb2013-05-252-4/+4
|
* Fix net80211 fragment creation.adrian2013-05-251-4/+15
| | | | | | | | | | | | | | | When creating fragment frames, the header length should honour the DATAPAD flag. This fixes the fragments that are queued to the ath(4) driver but it doesn't yet fix fragment transmission. That requires further changes to the ath(4) transmit path. Well, strictly speaking, it requires further changes to _all_ wifi driver transmit paths, but this is at least a start. Tested: * AR5416, STA mode, w/ fragthreshold set to 256.
* The error handling for writes to the target file could lead to the finalse2013-05-242-4/+4
| | | | | | | | | | fclose() being skipped. Fix this by using boolean "&" and "|" instead of short-cut operators "&&" and "||". While here, increment the last part of the version string. The reason is the fixed output file selection logic in pch.c, which was committed as r250943, yesterday. Reviewed by: pfg
* Fix building on slightly older -current and stable systems aftermarcel2013-05-241-0/+5
| | | | | | | | | | the switch to bmake. The rescue bits are built via crunchgen, which didn't respect the MAKE environment variable until r237574 (i.e. ~11 months ago). This resulted in a failure due to bmake's internal -J flag being passed around and not being understood by the standard (i.e. host's) make. Note that the failure is conditional upon having the jobServer feature enabled within bmake.
OpenPOWER on IntegriCloud