summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Use ANSI function definition.kib2016-06-051-1/+1
| | | | Sponsored by: The FreeBSD Foundation
* INTRNG - change the way how an interrupt mapping data are providedskra2016-06-0515-48/+189
| | | | | | | | to the framework in OFW (FDT) case. This is a follow-up to r301451. Differential Revision: https://reviews.freebsd.org/D6634
* sh: Improve descriptions in 'ulimit -a' output.jilles2016-06-051-2/+2
| | | | | The format limits descriptions to 18 characters and is not changed, so the descriptions do not describe the limits exactly.
* (1) Add a new bus method to get a mapping data for an interrupt.skra2016-06-055-17/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BUS_MAP_INTR() is used to get an interrupt mapping data according to provided hints. The hints could be modified afterwards, but only if mapping data was allocated. This method is intended to be called before BUS_ALLOC_RESOURCE(). An interrupt mapping data describes an interrupt - hardware number, type, configuration, cpu binding, and whatever is needed to setup it. (2) Introduce a method which allows storing of an additional data in struct resource to be available for bus drivers. This method is convenient in two ways: - there is no need to rework existing bus drivers as they can simply be extended to provide an additional data, - there is no need to modify any existing bus methods as struct resource is already passed to them as argument and thus stored data is simply accessible by other bus drivers. For now, implement this method only for INTRNG. This is motivated by needs of modern SOCs where hardware initialization is not straightforward and resources descriptions are complex, opaque for everyone but provider, and may vary from SOC to SOC. Typical situation is that one bus driver can fetch a resource description for its child device, but it's opaque for this driver. Another bus driver knows a provider for this kind of resource and can pass this resource description to it. In fact, something like device IVARS would be perfect for that if implemented generally enough. Unfortunatelly, IVARS are usable only by their owners now. Only owner knows its IVARS layout, thus other bus drivers are not able to use them. Differential Revision: https://reviews.freebsd.org/D6632
* Reflect error indication according to POSIX and what those functionsache2016-06-051-2/+2
| | | | currently do.
* Fix build with external gccbapt2016-06-051-0/+2
| | | | | Completly disable some extra optimisation for very recent gcc. They would require some updated in the runtime which we do not have yet
* Fix 4-byte overflow in ipv6_writemask.melifaro2016-06-051-1/+2
| | | | | | This bug could cause some IPv6 table prefix delete requests to fail. Obtained from: Yandex LLC
* Ensure old gcc does not accidently get the attributes it does not know aboutbapt2016-06-051-1/+1
|
* Remove duplicated semicolons.trasz2016-06-051-4/+4
| | | | MFC after: 1 month
* Report negotiated MaxBurstLength and FirstBurstLength in "iscsictl -v"trasz2016-06-059-5/+27
| | | | | | and "ctladm islist -v" outputs. MFC after: 1 month
* [bwn] Add missing firmware release calls.adrian2016-06-051-0/+3
| | | | | | | This trips me up whenever I'm fooling around with partially supported NICs that fail to fully attach or initialise - the firmware gets loaded and references, but something fails - and the firmware references aren't cleaned up.
* [bwn] Enable PHY-LP 5GHz support for the one NIC I have tested it on so far.adrian2016-06-051-11/+15
| | | | | | | | | | | | | | | After perusing the PHY-LP code (don't ask why; honest) I discovered that it /has/ 5GHz support - but it's not ever used. I found one NIC - a BCM4312 w/ pci id 0x4315 - which advertised dual-band PHY-LP support. Turns out it works. Whilst here, move up the support bit logging code so I can use it to debug this. Tested: * BCM4312 (pci id 0x4315); 5GHz STA operation
* [bwn] complain usefully if a PHY-N PHY is detected with no support is ↵adrian2016-06-051-0/+3
| | | | | | | compiled in. Log something other than "error 6" if the attach fails because the GPL PHY-N code isn't included.
* sfxge(4): allow firmware to auto-configure event queues on Medfordarybchik2016-06-053-13/+158
| | | | | | | | | | | | | | | | On Medford, licenses are required to enable RX and event cut through and to disable RX batching. To avoid the need for the driver to make decisions based on the licensing state, the MC_CMD_INIT_EVQ has been extended to allow us to leave the decision to the firmware. If the adapter is licensed for low-latency use, the firmware will choose the optimal settings for latency, otherwise it will use the best settings for throughput. For Huntington we still need to choose the settings ourselves. Submitted by: Mark Spender <mspender at solarflare.com> Sponsored by: Solarflare Communications, Inc. MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D6717
* [ath_hal] add AR9462 (jupiter) RX gain / XLNA programming.adrian2016-06-053-0/+60
| | | | | | | | | | | | | | This seems to make 5G work better. It doesn't fix powersave handling though, that still sees the PHY get stuck during initial calibration and everything goes pear shaped. I'll look into that later. Tested: * QCAFN222 NIC, STA mode, 5GHz Obtained from: Linux ath9k
* [ath_hal] Add Jupiter 2.1 (AR9462 mac 640.3) support.adrian2016-06-051-3/+32
| | | | | | | | | | | | | | | Turns out I wasn't even initialising or programming a lot of stuff for the AR9462 2.1 chip. Oops. This mostly gets it working. powersave scan results in some pretty hilarious NFcal hangs and I don't see beacons reliably. There are still some xlna gain tables missing that ath9k has; I'll follow up with some fixes and then see if the QCAFN222 NIC I have tests this path. Tested: * QCAFN222 NIC, STA mode, 2GHz and 5GHz
* [ath_hal] teach the reset path(s) about Jupiter 2.1.adrian2016-06-051-3/+4
| | | | | This was just .. not programming in things, and thus large chunks of the radio wouldn't work. Notably, 5GHz didn't work.
* [ath_hal] convert the MCI code over to work on Jupiter 2.1.adrian2016-06-051-7/+7
| | | | | (Note: jupiter 1.0 was emulation / test silicon, and was never released in production. So, yes, AR_SREV_JUPITER() would really be fine.)
* [acpi] graphics drivers want access to acpi lid handleadrian2016-06-051-1/+3
| | | | | | | the graphics drivers can benefit from access to the lid handle for querying and getting notifications Submitted by: kmacy Differential Revision: https://reviews.freebsd.org/D6643
* Add blacklist support to rlogindlidl2016-06-052-3/+27
| | | | | | | Reviewed by: rpaulo Approved by: rpaulo Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D6593
* [ath_hal] Make the AR9462 2.0 initvals from ath9k compile.adrian2016-06-051-19/+20
| | | | | The (upcoming) semi-working AR9462 2.1 support uses the 2.0 initvals where appropriate, and those need to at least compile under freebsd.
* Correct path for blacklistd.conf in OptionalObsoleteFiles.inclidl2016-06-051-1/+1
| | | | | | | | | | Fix typo made when adding the blacklistd.conf file to OptionalObsoleteFiles.inc Submitted by: Herbert J. Skuhra ( herbert at mailbox.org ) Reviewed by: rpaulo Approved by: rpaulo Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D6715
* Fix build after r301404.bdrewery2016-06-041-0/+4
| | | | | X-MFC-With: r301404 MFC after: 1 week
* Document getent(1)'s ability to enumerate netgroup members.markj2016-06-042-2/+4
| | | | MFC after: 3 days
* Fix markup.kib2016-06-042-2/+2
| | | | Sponsored by: The FreeBSD Foundation
* bhnd(4): support IPX OTP NVRAM/SPROM data sourcelandonf2016-06-0410-103/+159
| | | | | | | | | | | | | | | | Add support for fetching SPROM data from OTP on chipsets with an IPX OTP controller (including the BCM43225). This integrates the NVRAM data source into the chipc_caps capability structure, and adds a sprom_offset field that can be used with OTP to locate the SPROM image data (found within the general use region, H/W subregion). This also removes one of two duplicate parse error messages reported by both the bhnd_sprom driver and the underlying SPROM parsing API. Approved by: adrian (mentor) Differential Revision: https://reviews.freebsd.org/D6729
* Switch mips/sentry5 to bhnd(4), and unify with mips/broadcomlandonf2016-06-0418-2062/+304
| | | | | | | | | | | | | | | | | | | | | Now that bhnd(4) provides feature parity with the previous siba/mips implementation, we can switch sentry5 over and begin lifting common support code out for use across bhnd(4) embedded targets. Changes: - Fixed enumeration of siba(4) per-core address maps, required for discovery of memory mapped chipc flash region on siba(4) devices. - Simplified bhnd kernel configuration (dropped 'bhndbus' option). - Replaced files.broadcom's direct file references with their corresponding standard kernel options. - Lifted out common bcma/siba nexus support, inheriting from the new generic bhnd_nexus driver. - Dropped now-unused sentry5 siba code. - Re-integrated BCM into the universe build now that it actually compiles. Approved by: adrian (mentor) Differential Revision: https://reviews.freebsd.org/D6712
* bhnd(4): Add support for chipc-attached flashlandonf2016-06-048-6/+805
| | | | | | | | | This adds support for serial (via SPI) and parallel (via CFI) flash as found on BCM47xx/BCM53xx SoCs. Submitted by: Michael Zhilin <mizhka@gmail.com> Approved by: adrian (mentor) Differential Revision: https://reviews.freebsd.org/D6250
* Fix several MIPS/BCM-blocking bugs in bhnd(4) chipclandonf2016-06-046-26/+115
| | | | | | | | | | | | | | | - Correct IRQ lines for UART (to fix IRQ lookup in future) - Check device unit in resource assignment during chipc_add_child - If chipc hint->size is RM_MAX_END, resource end should be same as window end - Clear reference from resource list entry to resource in case of resource release - Add CHIPC_GET_CAPS implementation - Correct chipc flash constants (to be unshifted) - Default implementation of get_attach_type should iterate over device tree - Add default implementation for BHND_CHIPC_GET_CAPS usable by chipc grandchildren Submitted by: Michael Zhilin <mizhka@gmail.com> Approved by: adrian (mentor) Differential Revision: https://reviews.freebsd.org/D6584
* Update my e-mail address (and fix related typo in siba.4)landonf2016-06-044-9/+9
| | | | | Approved by: adrian (mentor) Differential Revision: https://reviews.freebsd.org/D6714
* Don't test for INKERNEL to check whether we're in kernel space.ed2016-06-041-1/+1
| | | | | | | | | | It turns out that <machine/param.h> actually defines a macro under this name, even when we're not in kernelspace. This causes us to suppress some macro definitions that are used by userspace apps. PR: 210026 Reported by: jbeich@ MFC after: 2 weeks
* Support all architectures by just using sysent.bdrewery2016-06-041-48/+35
| | | | | | | | | PowerPC64 has two different ABIs, neither of which is elf64_freebsd_sysvec. Using sysent and freebsd32_sysent achieves the same effect. X-MFC-With: r301130 MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
* Fix incorrect logic in r301394.bdrewery2016-06-041-1/+1
| | | | Reported by: Mark Millard
* DIRDEPS_BUILD: Update GCC dependencies.bdrewery2016-06-047-4/+7
| | | | Sponsored by: EMC / Isilon Storage Division
* Follow-up r301287: Pass external compiler metadata when used.bdrewery2016-06-041-0/+6
| | | | | | | This fixes WITH_SYSTEM_COMPILER, WITHOUT_CROSS_COMPILER, external compiler, to pass the external compiler metadata rather than the ${CC} metadata. On a build host that has clang as CC it was passing the clang metadata rather than GCC metadata during the build.
* Fix typo preventing pw {user,group}next -C from working as expectedbapt2016-06-042-2/+2
| | | | | Reported by: Mike Selnet via forums.freebsd.org MFC after: 3 days
* Import libucl snapshot 20160604bapt2016-06-0411-1233/+534
|\ | | | | | | | | It replaces xxhash with mumhash It fixes issues with msgpack on non x86
| * Update libucl to 20160604 snapshotbapt2016-06-0410-1231/+533
| |
* | sfxge(4): always be ready to receive batched eventsarybchik2016-06-042-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the low-latency firmware variant is running, it is reported as not being capable of batching RX events, but it can still do so if the FORCE_EV_MERGING flag is set on an RXQ. Therefore we need to handle batched RX events even if the capability isn't set. If this bug is fixed in the firmware such that the capability is set even when running the low-latency firmware variant, it will almost always be reported so I don't think we lose much by removing the check. Submitted by: Mark Spender <mspender at solarflare.com> Sponsored by: Solarflare Communications, Inc. MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D6705
* | sfxge(4): add helper to compute timer quantumarybchik2016-06-043-31/+55
| | | | | | | | | | | | | | | | | | | | | | | | This also adjusts the timer values used to match the Linux net driver implementation: a) non-zero time intervals should result in at least one quantum b) timer load/reload values are only zero biased for Falcon/Siena Submitted by: Andy Moreton <amoreton at solarflare.com> Sponsored by: Solarflare Communications, Inc. MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D6704
* | [ath] remove now unused parameters.adrian2016-06-041-4/+0
| | | | | | | | | | These will move to being part of the driver btcoex stuff I'm working on, since the HAL doesn't know what to do with them.
* | Use the UEFI event timer to update the time on arm and arm64. The currentandrew2016-06-049-5/+121
| | | | | | | | | | | | | | | | | | code uses the GetTime function from the Runtime Service, however this has been shown to not return a useable time on many arm64 UEFI implementations. Reviewed by: jhb, smh Sponsored by: ABT Systems Ltd Differential Revision: https://reviews.freebsd.org/D6709
* | [ath_hal] add STOMP_AUDIO for AR9462/QCA9565.adrian2016-06-041-0/+6
| | | | | | | | Obtained from: Linux ath9k
* | [ath_hal] add placeholders for AUDIO stomp for Kite/Kiwi.adrian2016-06-041-0/+4
| | | | | | | | It just stomps all; which is enough for some testing.
* | [ath_hal] add BTCOEX_STOMP_AUDIO; delete unused methods.adrian2016-06-041-2/+1
| |
* | [run] fix TSF locking in RX radiotap.adrian2016-06-041-0/+2
| | | | | | | | Submitted by: Imre Vadasz <imre@vdsz.com>
* | ioat(4): Always log capabilities on attachcem2016-06-041-1/+1
| | | | | | | | | | | | | | | | Different, relatively recent Intel Xeon hardware support radically different features. E.g., BDX support CRC32 while BDX-DE does not. Reviewed by: rpokala (spiritually) Sponsored by: EMC / Isilon Storage Division
* | ioat(4): Export the number of available channelscem2016-06-042-0/+9
| | | | | | | | Sponsored by: EMC / Isilon Storage Division
* | ioat(4): Make channel indices unsignedcem2016-06-042-3/+3
| | | | | | | | Sponsored by: EMC / Isilon Storage Division
* | Enable daily_ntpd_leapfile_enable by default. Otherwise an expiredcy2016-06-041-2/+1
| | | | | | | | | | | | | | | | | | | | leapfile will be ignored and ntpd will behave as if it has no leapfile. While here, remove an extraneous blank line. Suggested by: ache MFC after: 1 week
OpenPOWER on IntegriCloud