summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* o Determine the number of LAWs in a way the is future proof. Only themarcel2011-05-281-7/+14
| | | | | | | | | | | | MPC8555(E) has 8 LAWs, so don't make that the default case. Current processors have 12 LAWs so use that as the default instead. o Determine the target ID of the PCI/PCI-X and PCI-E controllers in a way that's more future proof. There's almost a perfect mapping from HC register offset to target ID, so use that as the default. Handle the MPC8548(E) specially, since it has a non-standard target ID for the PCI-E controller. Don't worry about whether the processor implements the target ID here, because we should not get called for PCI/PCI-X or PCI-E host controllers that don't exist.
* Remove unused defines. They're distracting...marcel2011-05-281-5/+0
|
* Fix shell-based partitioning.nwhitehorn2011-05-281-1/+1
|
* Fix AR9287 operation when >1 TX chain is enabled.adrian2011-05-281-0/+1
| | | | | I didn't pick this up with the initial commit because I was only testing with 11bg.
* Update the manual page to reflect the new 32K/4K defaults.mckusick2011-05-281-4/+4
| | | | Reminded by: Ivan Voras
* Due to a lag in updating the fs_pendinginodes count, we cannot dependmckusick2011-05-281-1/+1
| | | | | | | on it to decide whether we should try to reclaim inodes when we run short. Discovered by: Peter Holm
* printf(1): Document that %c and precision for %b/%s use bytes, not chars.jilles2011-05-281-6/+17
| | | | | | | This means these features do not work as expected with multibyte characters. This perhaps less than ideal behaviour matches printf(3) and is specified by POSIX.
* printf: Allow multibyte characters for '<char> form, avoid negative codes.jilles2011-05-285-8/+25
| | | | | | | | | | | | | Examples: LC_ALL=en_US.UTF-8 printf '%d\n' $(printf \'\\303\\244) LC_ALL=en_US.ISO8859-1 printf '%d\n' $(printf \'\\344) Both of these should print 228. Like some other shells, incomplete or invalid multibyte characters yield the value of the first byte without a warning. Note that there is no general way to go back from the character code to the character.
* New boot loader menus from Devin Teske.julian2011-05-2828-285/+3099
| | | | | | | | Discussed on hackers and recommended for inclusion into 9.0 at the devsummit. All support email to devin dteske at vicor dot ignoreme dot com . Submitted by: dteske at vicor dot ignoreme dot com Reviewed by: me and many others
* Better support different kernel hand-offs. When loaded directlymarcel2011-05-283-53/+62
| | | | | | | | | | | | | | | | | | | | from U-Boot, the kernel is passed a standard argc/argv pair. The Juniper loader passes the metadata pointer as the second argument and passes 0 in the first. The FreeBSD loader passes the metadata pointer in the first argument. As such, have locore preserve the first 2 arguments in registers r30 & r31. Change e500_init() to accept these arguments. Don't pass global offsets (i.e. kernel_text and _end) as arguments to e500_init(). We can reference those directly. Rename e500_init() to booke_init() now that we're changing the prototype. In booke_init(), "decode" arg1 and arg2 to obtain the metadata pointer correctly. For the U-Boot case, clear SBSS and BSS and bank on having a static FDT for now. This allows loading the ELF kernel and jumping to the entry point without trampoline.
* Upgrade to 9.6-ESV-R4-P1, which address the following issues:dougb2011-05-28724-1139/+886
| | | | | | | | | | | | | | | | 1. Very large RRSIG RRsets included in a negative cache can trigger an assertion failure that will crash named (BIND 9 DNS) due to an off-by-one error in a buffer size check. This bug affects all resolving name servers, whether DNSSEC validation is enabled or not, on all BIND versions prior to today. There is a possibility of malicious exploitation of this bug by remote users. 2. Named could fail to validate zones listed in a DLV that validated insecure without using DLV and had DS records in the parent zone. Add a patch provided by ru@ and confirmed by ISC to fix a crash at shutdown time when a SIG(0) key is being used.
* o The P1020(E) & P2020(E) also have two cores. This conditional hasmarcel2011-05-271-18/+20
| | | | | | | | | | a tendency to grow unwieldy so we may want to revisit this in due time. o Simplify the CPU reset function by writing to the reset control register irrespective of whether the CPU has one and automatically falling back to the debug control register if we didn't reset the CPU. The side-effect is that we now properly reset future processors without first having to add the system version to the list.
* Wire the kernel using TLB1 entry 0 rather than entry 1. A more recentmarcel2011-05-272-23/+10
| | | | | | U-Boot as found on the P1020RDB doesn't like it when we use entry 1 (for some reason) whereas an older U-Boot doesn't mind if we use entry 0. If anything else, this simplifies the code a bit.
* find: If a part of an expression is unknown, do not call it an option.jilles2011-05-271-1/+1
| | | | | | | | | | | Although most of the primaries and operators start with "-", they are not options. Examples: find . -xyz find . -name xyz -or bad MFC after: 1 week
* Fix the new NFS client so that it handles NFSv4 statermacklem2011-05-276-34/+109
| | | | | | | | | | | | | | | | | correctly during a forced dismount. This required that the exclusive and shared (refcnt) sleep lock functions check for MNTK_UMOUNTF before sleeping, so that they won't block while nfscl_umount() is getting rid of the state. As such, a "struct mount *" argument was added to the locking functions. I believe the only remaining case where a forced dismount can get hung in the kernel is when a thread is already attempting to do a TCP connect to a dead server when the krpc client structure called nr_client is NULL. This will only happen just after a "mount -u" with options that force a new TCP connection is done, so it shouldn't be a problem in practice. MFC after: 2 weeks
* sh: Remove the "exp" builtin.jilles2011-05-272-2/+2
| | | | | | | | | | | | | | | | | | | | | | | The "exp" builtin is undocumented, non-standard and not very useful. If exp's return value is not used, something like VAR=$(exp EXPRESSION) is equivalent to VAR=$((EXPRESSION)) except that errors in the expression are fatal and quoting special characters is not needed in the latter case. If exp's return value is used, something like if exp EXPRESSION >/dev/null can be replaced by if [ $((EXPRESSION)) -ne 0 ] with similar differences. The exp-run showed that "let" is close enough to bash's and ksh's builtin that removing it would break a few ports. Therefore, "let" remains in 9.x. PR: bin/104432 Exp-run done by: pav (with some other sh(1) changes)
* sh: Correct criterion for using CDPATH in cd.jilles2011-05-273-1/+29
| | | | | | | CDPATH should be ignored not only for pathnames starting with '/' but also for pathnames whose first component is '.' or '..'. The man page already describes this behaviour.
* Remove definitions for RACCT_FSIZE and RACCT_SBSIZE - these two are rathertrasz2011-05-274-31/+20
| | | | | performance-sensitive and not that useful, so I won't be merging them before 9.0.
* sh: Add simple CDPATH test.jilles2011-05-271-0/+23
|
* Whitespace fixeskevlo2011-05-271-2/+2
| | | | Reviewed by: jpaetzel
* sh: Various updates to the TOUR document.jilles2011-05-271-29/+8
|
* sh: Fix unquoted $@/$* if IFS=''.jilles2011-05-272-2/+44
| | | | | | If IFS is null, unquoted $@/$* should still expand to separate words. This differs from quoted $@ (which does not depend on IFS) in that pathname generation is performed and empty words are removed.
* Add example how to create MBR and BSD schemes and install boot code.ae2011-05-271-1/+28
|
* Synchronize manpage's synopsis with program's usage. Since -l and -rae2011-05-272-5/+6
| | | | | | | keys are mutually exclusive for the `gpart show` command, then mark them so. Requested by: ru
* - Move some internal functions to the private namespacegabor2011-05-271-9/+12
| | | | | Submitted by: kan Approved by: delphij (mentor)
* Silence warnings about unsupoorted value types.pjd2011-05-271-0/+4
| | | | MFC after: 2 weeks
* 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.
OpenPOWER on IntegriCloud