summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Some partitioning tools may have a different opinion about diskae2011-05-271-2/+7
| | | | | | geometry and partitions may start from withing the first track. If we found such partitions, then do not reserve space of the first track, only first sector.
* o Swap the SVR numbers for MPC8533 & MPC8533Emarcel2011-05-271-2/+10
| | | | o Add SVR defines for P1011(E), P1020(E), P2010(E) & P2020(E)
* Change new constant names to ones used by OpenSolaris.mav2011-05-272-4/+4
|
* Oops, fix typo in r222336.mav2011-05-271-1/+1
|
* Add ses/srcs/eltsub.h to the list of files to be installed.mav2011-05-271-0/+1
| | | | It is required for user-level SES example tools build.
* Add names for few more SES element types according SES-2 specification.mav2011-05-272-0/+16
|
* The check for whether a block is going to be claimed by a snapshotmckusick2011-05-261-4/+12
| | | | | needs to happen before we notify the underlying layer that it is being freed.
* In ipoib_cm_handle_rx_wc(): Count incoming packets anddelphij2011-05-261-2/+2
| | | | | | bytes toward incoming counters. Reviewed by: jeff
* Add a check for MNTK_UNMOUNTF at the beginning of nfs_sync()rmacklem2011-05-261-1/+11
| | | | | | | | | in the new NFS client so that a forced dismount doesn't get stuck in the VFS_SYNC() call that happens before VFS_UNMOUNT() in dounmount(). Additional changes are needed before forced dismounts will work. MFC after: 2 weeks
* For Timedia multiport serial adapters, the first two ports use a SUN1889jhb2011-05-261-0/+6
| | | | | | | | which uses a non-standard clock (* 8) while any additional ports use SUN1699 chips which use a standard clock. Tested by: N.J. Mann njm of njm me uk MFC after: 1 week
* Don't assume we have a valid bootinfo pointer.marcel2011-05-261-2/+5
|
* Fix tftp_log() usage.rodrigc2011-05-261-1/+1
|
* Introduce AR9287 support to the FreeBSD HAL.adrian2011-05-262-31/+69
|
* Fix a macro name - it's currently unused in this file however, butadrian2011-05-261-1/+1
| | | | keep it consistent with ar9280.c.
* Revert this erroneous commit and re-disable the AR9285 combined antennaadrian2011-05-261-2/+0
| | | | diversity.
* Include an EEPROM dump program for the AR9287 EEPROM format.adrian2011-05-266-0/+508
|
* Fix support for RACCT_CORE by merging forgotten file.trasz2011-05-261-2/+4
|
* Raise the default blocksize for UFS/FFS filesystems frommckusick2011-05-261-2/+2
| | | | | | | | | | | | | | | | | | | 16K to 32K and the default fragment size from 2K to 4K. The rational is that most disks are now running with 4K sectors. While they can (slowly) simulate 512-byte sectors by doing a read-modify-write, it is desirable to avoid this functionality. By raising the minimum filesystem allocation to 4K, the filesystem will never trigger the small sector emulation. Also, the growth of disk sizes has lead us to double the default block size about every ten years. The rise from 8K to 16K blocks was done in 2001. So, by the 10-year metric, the time has come for 32K blocks. Discussed at: May 2011 BSDCan Developer Summit Reference: http://wiki.freebsd.org/201105DevSummit/FileSystems
* Ignore MCR[6] during the probe to fix a false negative. Bit 6 of themarcel2011-05-261-1/+7
| | | | | | | | | | MCR register on the Sunix Sun1699 chip tends to be set but doesn't seem to have a function. That is, FreeBSD just works (provided the correct RCLK is used) regardless. PR: kern/129663 Diagnostics: Eygene Ryabinkin <rea-fbsd at codelabs.ru> MFC after: 3 days
* Remove the three-chain scaled power check for the AR9287 - it isn'tadrian2011-05-261-6/+0
| | | | needed.
* Make sure only two chains are calibrated for the AR9287.adrian2011-05-261-2/+2
|
* Add some open-loop TX power debugging for AR9287.adrian2011-05-261-0/+5
|
* Close a race between libzfs and mountd when updating NFS exports.will2011-05-261-0/+1
| | | | | | | | | - Flush the file descriptor for the new ZFS exports file before sending a SIGHUP to mountd. Reviewed by: pjd Approved by: ken MFC after: 3 days
* Bring over the AR5416 per-rate TX power code, modified to use theadrian2011-05-261-9/+199
| | | | | | | | | | | | | AR9287 EEPROM layout. The AR9287 only supports 2ghz, so I've removed the 5ghz code (but left the 5ghz edge flags in there for now) and hard-coded the 2ghz-only path. Whilst I'm there, fix a typo (ar9285->ar9287.) This meets basic TX throughput testing - iperf TX tests == 27-28mbit in 11g, matching the rest of my 11g kit.
* Flesh out ar9287SetTransmitPower() based on the AR9285 routine.adrian2011-05-261-6/+116
| | | | | | Hard-code the per-rate TX power at 5dBm for now so testing can be done. This passes initial TX testing in 11g mode (but, obviously, at 5dBm.)
* Add a missing isync.nwhitehorn2011-05-261-0/+1
|
* Flesh out the TX power calibration for the AR9287.adrian2011-05-264-0/+179
| | | | | | | | | | | | | | I'm assuming for now that the AR9287 is only open-loop TX power control (as mine is) so I've hard-coded the attach path to fail if the NIC is not open-loop. This greatly simplifies the TX calibration path and the amount of code which needs to be ported over. This still isn't complete - the rate calculation code still needs to be ported and it all needs to be glued together. Obtained from: Linux ath9k
* Added myself as src committer.ray2011-05-262-0/+4
| | | | Approved by: adrian (mentor)
* Add Marvell 88SE9172 chip PCI ID.mav2011-05-261-0/+1
|
* Add the AR9287 chip identification string.adrian2011-05-261-0/+2
|
* Marvell 88SE91xx controllers are known to report soft-reset completionmav2011-05-261-28/+49
| | | | | | | | | | | | | | without waiting for device readiness (or at least not updating FIS receive area in time). To workaround that, special quirk was added earlier to wait for the FIS receive area update. But it was found that under same PCI ID 0x91231b4b and revision 0x11 there are two completely different chip versions (firmware?): HBA and RAID. The problem is that RAID version in some cases, such as hot-plug, does not update FIS receive area at all! To workaround that, differentiate the chip versions by their capabilities, and, if RAID version found, skip FIS receive area update waiting and read device signature from the PxSIG register instead. This method doesn't work for HBA version when PMP attached, so keep using previous workaround there.
* Fix a bad merge from a previous commit.adrian2011-05-261-4/+6
|
* Merlin -> Kiwiadrian2011-05-261-2/+2
|
* Bring over my AR9287 work in progress.adrian2011-05-2616-1/+2293
| | | | | | | | | | | | | | | | | | | | | | | | | | | It isn't linked into the build because it's missing the TX power and PDADC programming code. This code is mostly based on the ath9k codebase, compared against the Atheros codebase as appropriate. What's implemented: * probe/attach * EEPROM board value programming * RX initial calibration * radio channel programming * general MAC / baseband setup * async fifo setup * open-loop tx power calibration What's missing before it can be enabled by default: * TX power / calibration setting code * closed-loop tx power calibration routines * TSF2 handling * generic timer support from ath9k Obtained from: Atheros, ath9k
* AR9287 prep work:adrian2011-05-263-3/+32
| | | | | | | | * Add PCI/PCIE devids * Add AR9287/Kiwi version check macros * AR_SREV_9287 -> AR_SREV_KIWI Obtained from: Atheros, ath9k
* Add temp sense to the EEPROM variable list;adrian2011-05-262-23/+15
| | | | Export the temperature sense variables to ah_eeprom_9287.c
* Add better names for the Intel HDMI audio codecs.mav2011-05-261-12/+14
|
* + Tighten up (and simplify) the pass_cmd_vars_1 "variable definition arrivedobrien2011-05-251-12/+9
| | | | | from the calling make" test. + Be more tolerant of newlines in the plus_flag "supports the '+' flag" test.
* sh: Show errno messages in cd.jilles2011-05-251-1/+4
|
* Add some missing mutex locking to the new NFS client.rmacklem2011-05-251-0/+2
| | | | MFC after: 2 weeks
* Bump the date of the man page to the date of the actual commit.bcr2011-05-251-1/+1
| | | | Noticed by: brix
* Fix the new NFS client so that it correctly sets the "must_commit"rmacklem2011-05-253-18/+11
| | | | | | | | argument for a write RPC when it succeeds for the first one and fails for a subsequent RPC within the same call to the function. This makes it compatible with the old NFS client for this case. MFC after: 2 weeks
* Document the device name change from gpioctl to gpioc in thebcr2011-05-251-5/+5
| | | | | | | | man page. PR: docs/157075 Submitted by: brix Reviewed by: gonzo
* Fix a regression introduced with previous changeset: if output is stdout,delphij2011-05-251-1/+2
| | | | do not check for symbolic link.
* [mdoc] Fixed .Dt call.ru2011-05-2518-18/+18
|
* According to SATA specification, when Serial ATA Enclosure Management Bridgemav2011-05-253-29/+65
| | | | | | | | | | | | | | | | | | | | (SEMB) is unable to communicate to Storage Enclosure Processor (SEP), in response to hard and soft resets it should among other things return value 0x7F in Status register. The weird side is that it means DRQ bit set, which tells that reset request is not completed. It would be fine if SEMB was the only device on port. But if SEMB connected to PMP or built into it, it may block access to other devices sharing same SATA port. Make some tunings/fixes to soft-reset handling to workaround the issue: - ahci(4): request CLO on the port after soft reset to ignore DRQ bit; - siis(4): gracefully reinitialize port after soft reset timeout (hardware doesn't detect reset request completion in this case); - mvs(4): if PMP is used, send dummy soft-reset to the PMP port to make it clear DRQ bit for us. For now this makes quirks in ata_pmp.c, hiding SEMB ports of SiI3726/SiI4726 PMPs, less important. Further, if hardware permit, I hope to implement real SEMB support.
* Prevent non-aligned reading from provider while tasting. Rejectae2011-05-252-0/+10
| | | | | | | providers with unsupported sectorsize. Reported by: Joerg Wunsch MFC after: 1 week
* Bring back r222275. runfw(4) will statically link in rt2870.fw.uukevlo2011-05-252-2/+0
| | | | | | to the kernel, though I have MODULES_OVERRIDE="" in GENERIC. Spotted by: thompsa
* Do not truncate available disk space to the closest track boundary.ae2011-05-251-7/+3
|
* Do not truncate available disk space to the closest track boundary.ae2011-05-251-2/+1
|
OpenPOWER on IntegriCloud