summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add Basque (Spain) locales: eu_ES.ISO8859-1, eu_ES.ISO8859-15, eu_ES.UTF-8.tjr2004-08-2810-10/+161
| | | | | | | | (This differs somewhat from the version originally submitted - any mistakes are my own.) PR: 68524 Submitted by: J. Vicente Carrasco -Bixen-
* Re-generate from ru_RU.KOI8-R.src. Due to a bug in either iconv ortjr2004-08-281-1/+1
| | | | | | ru_RU.CP866.src, the previous version of this file contained a strange conversion error: nostr had U+255C BOX DRAWINGS UP DOUBLE AND LEFT SINGLE instead of U+0435 CYRILLIC SMALL LETTER IE.
* Add support Corega CG-LAPCIGT Gigabit Ethernet(8169S)sanpei2004-08-283-0/+9
| | | | | | PR: [FreeBSD-users-jp 80667] Submitted by: FUJIMOTO Kou <fujimoto@j.dendai.ac.jp> MFC after: 1 week
* Don't be too smart, just try packet mode of INT13 first.yar2004-08-282-5/+9
| | | | | | | | | | | | | | | This way of operation is more robust than the "AI" used before. Add flags to mbr accessible from make.conf as BOOT_MBR_FLAGS. Only one flag is defined now, "allow using packet mode", which is 0x80 in accord with the rest of i386 boot code. The "packet" flag is on by default. PR: i386/70241 Submitted by: Valentin Nechayev <netch <@> netch.kiev.ua> (inital version) Discussed with: jhb (by Valentin Nechayev) Tested on: bochs (with EDD turned on or off by patching the BIOS), PCs
* Try packet mode of INT13 on a hard disk first if not prohibited byyar2004-08-281-19/+21
| | | | | | | | | | | the flag, fall back to the old INT13/AH=02 function if that fails. This way of operation is less likely to fail with modern BIOSes and large disks of strange geometries. PR: i386/70241 Submitted by: Valentin Nechayev <netch <@> netch.kiev.ua> (inital version) Discussed with: jhb (by Valentin Nechayev) Tested on: bochs (with EDD turned on or off by patching the BIOS), PCs
* Avoid double appearing of cloned interfaces in the outputyar2004-08-281-3/+4
| | | | | | | | | | | | | | | from list_net_interfaces() when network_interfaces=auto. Rationale: Since the auto case is special, the lesser evil had to be chosen among not adding cloned interfaces to _tmplist or removing duplicates from _tmplist after adding cloned interfaces. Since list_net_interfaces() must not use /usr/bin tools, the former "evil" appeared clearer and much more efficient. (See the PR audit trail for discussion.) PR: conf/63700 Reviewed by: brooks MFC after: 5 days
* Make -C and -T work correctly together.kientzle2004-08-281-4/+5
| | | | | MFC after: 3 days Thanks to: Guy Helmer
* 1. try to use existing mailbox address in thread_update_usr_ticks.davidxu2004-08-281-4/+6
| | | | 2. remove '\n' in KASSERT.
* Move TDF_CAN_UNBIND to thread private flags td_pflags, this eliminatesdavidxu2004-08-282-23/+7
| | | | | | | need of sched_lock in some places. Also in thread_userret, remove spare thread allocation code, it is already done in thread_user_enter. Reviewed by: julian
* document that m_free returns m_next of the free'd mbufjmg2004-08-281-1/+5
|
* Recognize and skip 'x' and 'g' pax extension entries. In particular,kientzle2004-08-281-0/+15
| | | | | | | this avoids the creation of "PaxHeader" dirs when unpacking pax-format tar archives such as those written by bsdtar. MFC after: 3 days
* Warn the user if we are not going to use the whole provider's space.pjd2004-08-281-1/+21
|
* Use sc->sc_mediasize instead of sc->sc_provider->mediasize which containspjd2004-08-281-4/+3
| | | | exactly the same value, but is shorter.
* Warn the user if we are not going to use whole provider space.pjd2004-08-282-9/+21
| | | | Requested by: Michael Handler <handler@grendel.net>
* - If error string begins with "warning: ", don't exit, treat it as a warningpjd2004-08-281-4/+6
| | | | | only. - Use getprogname() function when informing about versions problem.
* Don't allow to insert providers, which are too small.pjd2004-08-281-0/+4
| | | | Reported by: Michael Handler <handler@grendel.net>
* Backout the previous backout (with scott's ok). sched_ule.c:1.122 ispeter2004-08-281-0/+2
| | | | believed to fix the problem with ULE that this change triggered.
* s/smp_rv_mtx/smp_ipi_mtx/gobrien2004-08-286-23/+23
| | | | Requested by: jhb
* Commit Jeff's suggested changes for avoiding a bug that is exposed bypeter2004-08-281-4/+2
| | | | | | | preemption and/or the rev 1.79 kern_switch.c change that was backed out. The thread was being assigned to a runq without adding in the load, which would cause the counter to hit -1.
* - Auto generate device listings for the following drivers: snd_ad1816,simon2004-08-273-52/+23
| | | | | | snd_cmi, snd_cs4281, snd_ds1, snd_emu10k1, snd_es137x, and snd_solo. MFC after: 5 days
* remove unused prototypesos2004-08-271-1/+0
|
* Make code ready to switch debug.mpsafenet to 1 since I've not able torik2004-08-272-2/+4
| | | | commit MPSAFE code for now it is just IFF_NEEDSGIANT.
* Add manual pages for several sound drivers.simon2004-08-279-0/+508
| | | | | | Submitted by: Atte Peltomaki <koston@iki.fi> Reviewed by: cg MFC after: 5 days
* Catch up with the drive-by renaming of IA32 to COMPAT_IA32. Missedmarcel2004-08-271-2/+2
| | | | | 11 days ago when all the other places were fixed and finally caught by the tinderbox run...
* Forced commit to add additional comment.gibbs2004-08-270-0/+0
| | | | | | | | | | | | | | | o Add MOUSE_PS2_TAP into syncmask[0] correctly when we're built with PSM_CONFIG_FORCETAP. The previous code from revision 1.56 attempted to do this but updated the a mask variable that would be clobbered later. o If syncmask[1] hasn't yet been set when ioctl(MOUSE_GETMODE) is called, zero syncmask[0] and syncmask[1] so that sync validation is effectively disabled in userland applications and moused doesn't misbehave. The psm driver performs sync validation so there is no loss in functionality in clearing the sync mask. o If PSM_NEED_SYNCBITS is set, setup syncmask[1], even if it's already correct. This prevents the PSM_NEED_SYNCBITS bit from being left on after a re-initialisation and erroneously causing a subsequent out-of-sync packet to mis-set syncmask[1].
* - Improve handling of trailing punctuation characters for the Xr macro.simon2004-08-271-3/+7
| | | | MFC after: 3 days
* Move config_new_drive() to the correct place and rename it tole2004-08-273-32/+30
| | | | gv_config_new_drive().
* Fix a comment, IA32 was renamed to COMPAT_IA32arved2004-08-271-1/+1
| | | | Approved by: marcel
* Improve sync recovery algorithm:gibbs2004-08-272-194/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o Remove PSM_SYNCERR_THRESHOLD1. This value specified how many sync errors were required before the mouse is re-initialised. Re-initialisation is now done after (packetsize * 2) sync errors as things aren't likely to improve after that. o Reset lastinputerror when re-initialisation occurs. We don't want to continue to drop data after re-initialisation. o Count the number of failed packets independently of the syncerrors statistic. syncerrors is useful for recovering sync within a single packet. pkterrors allows us to detect when the mouse changes its packet mode due to some external event (e.g. KVM switch). o Reinitialize the mouse if we see more than psmpkterrthresh errors during the validation period. The validation period begins as soon as a sync error is detected and continues until psmerrsecs/msecs time has elapsed. The defaults for these two values force a reset if we see two packet errors in a 2 second period. This allows rapid detection of packet framing errors caused by the mouse changing packet modes. o Export psmpkterrthresh as a sysctl o Export psmloglevel as a sysctl. o Enable more debugging code to be enabled at runtime via psmloglevel. o Simplify verbose conditioned loging by using a VLOG macro. o Add several comments describing the sync recovery algorithm of this driver. Large Portions by: Brian Somers <brian@Awfulhak.org> Inspired and Frustrated by: Belkin KVMs Reviewed by: njl, philip
* Poll() uses the array smallbits that is big enough to hold 32 structandre2004-08-271-3/+3
| | | | | | | | | | | | pollfd's to avoid calling malloc() on small numbers of fd's. Because smalltype's members have type char, its address might be misaligned for a struct pollfd. Change the array of char to an array of struct pollfd. PR: kern/58214 Submitted by: Stefan Farfeleder <stefan@fafoe.narf.at> Reviewed by: bde (a long time ago) MFC after: 3 days
* From __FreeBSD_version 600001 on PFIL_HOOKS is permanently in the kernel andandre2004-08-272-2/+3
| | | | doesn't require to include opt_pfil_hooks.h.
* - Auto generate device listing for ath(4).simon2004-08-273-8/+3
| | | | MFC after: 3 days
* opt_pfil_hooks.h is no longer required.andre2004-08-271-1/+0
|
* When detaching an interface, don't leave an obsolete pointer to thebrooks2004-08-271-0/+1
| | | | | | | soon to be deleted struct ifnet around. PR: kern/52260 MFC After: 3 days
* Move the kernel-specific logic to adjust frompc from MI to MD. Formarcel2004-08-278-38/+123
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | these two reasons: 1. On ia64 a function pointer does not hold the address of the first instruction of a functions implementation. It holds the address of a function descriptor. Hence the user(), btrap(), eintr() and bintr() prototypes are wrong for getting the actual code address. 2. The logic forces interrupt, trap and exception entry points to be layed-out contiguously. This can not be achieved on ia64 and is generally just bad programming. The MCOUNT_FROMPC_USER macro is used to set the frompc argument to some kernel address which represents any frompc that falls outside the kernel text range. The macro can expand to ~0U to bail out in that case. The MCOUNT_FROMPC_INTR macro is used to set the frompc argument to some kernel address to represent a call to a trap or interrupt handler. This to avoid that the trap or interrupt handler appear to be called from everywhere in the call graph. The macro can expand to ~0U to prevent adjusting frompc. Note that the argument is selfpc, not frompc. This commit defines the macros on all architectures equivalently to the original code in sys/libkern/mcount.c. People can take it from here... Compile-tested on: alpha, amd64, i386, ia64 and sparc64 Boot-tested on: i386
* - For column lists: ignore first item when it is likely to be a header.simon2004-08-271-18/+55
| | | | | | | | - Clean up and improve handling of trailing punctuation characters. - Handle the Pa macro. - Give a warning when ignoring unimplemented mdoc commands. MFC after: 3 days
* Bump __FreeBSD_version to indicate permanent PFIL_HOOKS.andre2004-08-271-1/+1
|
* Provide extern declarations for btext and etext when GPROF is defined.marcel2004-08-271-0/+5
| | | | These are referenced in subr_prof.c when building a profiling kernel.
* Have the linker provide the btext symbol when referenced. This is neededmarcel2004-08-271-0/+1
| | | | | for profiling kernels. Apparently, nobody has ever tried to build one on alpha...
* The machine-independent parts of the virtual memory system always pass aalc2004-08-274-64/+0
| | | | | | | valid pmap to the pmap functions that require one. Remove the checks for NULL. (These checks have their origins in the Mach pmap.c that was integrated into BSD. None of the new code written specifically for FreeBSD included them.)
* Semi-gratuitous white space synchronization with KAME tree: to reducerwatson2004-08-271-10/+12
| | | | | | diffs against #ifdef'd version of IPSEC, use "struct thread *p" rather than "struct proc *p", fix some white space, and make some already inconsistent white space inconsiste differently.
* Apply error and success logic consistently to the function netisr_queue() andandre2004-08-2716-28/+25
| | | | | | | | | | | | | | | | | | its users. netisr_queue() now returns (0) on success and ERRNO on failure. At the moment ENXIO (netisr queue not functional) and ENOBUFS (netisr queue full) are supported. Previously it would return (1) on success but the return value of IF_HANDOFF() was interpreted wrongly and (0) was actually returned on success. Due to this schednetisr() was never called to kick the scheduling of the isr. However this was masked by other normal packets coming through netisr_dispatch() causing the dequeueing of waiting packets. PR: kern/70988 Found by: MOROHOSHI Akihiko <moro@remus.dti.ne.jp> MFC after: 3 days
* Diff reduce against KAME: minor white space synchronization to KAMErwatson2004-08-271-4/+4
| | | | tree.
* Hide a printf under bootverbose.phk2004-08-271-1/+3
|
* Properly document and enable the IPFIREWALL_FORWARD option.andre2004-08-271-0/+5
|
* In the case the destination of a packet was changed by the packet filterandre2004-08-271-2/+2
| | | | | | | | | | | | to point to a local IP address; and the packet was sourced from this host we fill in the m_pkthdr.rcvif with a pointer to the loopback interface. Before the function ifunit("lo0") was used to obtain the ifp. However this is sub-optimal from a performance point of view and might be dangerous if the loopback interface has been renamed. Use the global variable 'loif' instead which always points to the loopback interface. Submitted by: brooks
* Remove a junk line left over from the recent IPFW to PFIL_HOOKS conversion.andre2004-08-271-1/+0
|
* Always compile PFIL_HOOKS into the kernel and remove the associated kernelandre2004-08-2725-123/+58
| | | | | | | | | | | compile option. All FreeBSD packet filters now use the PFIL_HOOKS API and thus it becomes a standard part of the network stack. If no hooks are connected the entire packet filter hooks section and related activities are jumped over. This removes any performance impact if no hooks are active. Both OpenBSD and DragonFlyBSD have integrated PFIL_HOOKS permanently as well.
* B1FLAGS -> BOOT_BOOT1_FLAGS, which is consistent withyar2004-08-272-4/+4
| | | | naming of other boot-related make vars.
* Remove the misleading description of the 'key' argument toroam2004-08-271-17/+1
| | | | | | | | | mpool_open(3) - it is *not* really used for synchronization; in fact, it is not used at all. PR: 70929 Submitted by: Martin Kammerhofer <dada@sbox.tugraz.at> MFC after: 3 days
OpenPOWER on IntegriCloud