summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix problem caused by previous commit where some users' buttonsnjl2004-02-192-11/+2
| | | | | | | stopped returning events. Don't disable the event when removing the handler because it still needs to be enabled for the other handler. Also, remove duplicate AcpiEnableEvent calls since the install function now does this for us.
* Add support for 'h' and 'hh' modifiers for printf(9).njl2004-02-191-2/+21
| | | | | Submitted by: Bruno Ducrot <ducrot AT poupinou.org> Reviewed by: bde
* Checkpoint the NOTES I was working on.obrien2004-02-191-152/+114
|
* Unbreak fixit crunch: since Feb/17/2004, mount(8) requires libufs.matusita2004-02-193-3/+3
| | | | | | See also src/sbin/mount/Makefile rev 1.14. Noticed by: snapshots.jp.FreeBSD.org
* Fix a long-standing bug where select on vchans doesn't workmatk2004-02-191-3/+13
| | | | | | (never wake up) by iterating over them when they exist. Approved by: tanimura (mentor)
* Switch to using the new $PIR interrupt routing code and remove the oldjhb2004-02-184-436/+22
| | | | | code. The pci_cfgreg.c file now just controls reading/writing PCI config registers.
* Rework the $PIR (aka PCIBIOS) PCI interrupt routing code and split it offjhb2004-02-181-609/+445
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into its own file: - All of the $PIR interrupt routing is now done in a link-centric fashion. When a host-PCI bridge that uses the $PIR attaches, it calls pir_parse() to parse the table. This scans for link devices and merges all the masks for each link device from the table entries. It then looks at the intline register of PCI devices connected to a link to figure out if the BIOS has routed this link and if so to which IRQ. - The IRQ for any given link can be overridden via a hint like so: 'hw.pci.link.0x62.irq=10' Any IRQ set in this matter is treated as if it were set that way by the BIOS. - We only call the BIOS to route each link device once. - When a PCI device wants to route an interrupt, we look it up in the $PIR to find the associated link. If the link is routed, we simply return the IRQ it is using. If it is not routed, we have to pick one. This uses a different algorithm from the old code. First off, when we try to pick an interrupt from a mask of possible interrupts, we try to pick the one that is least loaded as far as PCI devices. We maintain this weight based on the number of devices attached to each link device. When choosing an IRQ, we first attempt to route using any PCI only interrupts (the old code did this as well). If that doesn't work, we try to use the list of IRQs that the BIOS has used. This is a new step that the new code didn't do and avoids using IRQ 3 or 4 for every virgin interrupt routing. If none of the IRQs that the BIOS used worked, then we fall back to trying anything. - The fallback mask for !PC98 was fixed to include IRQ 3 and not allow IRQ 2. - We don't use the $PIR to route interrupts on a PCI-PCI bridge unless it has already been used to route on at least one Host-PCI bridge. This helps to avoid mixing and matching x86 firmware PCI interrupt routing methods (which is a Bad Thing(tm)). Silence on: current@
* Improve contents, ruin formatting.phk2004-02-181-38/+68
|
* Install gnuregex.h as wrapper for gnu/regex.h (with warning)ache2004-02-182-1/+6
|
* Use %zu for size_t, like God intended.des2004-02-181-1/+1
|
* Fix printf() format bug in previous commit (size_t != int).des2004-02-181-17/+19
| | | | | | | Use %ju and an (uintmax_t) cast to print size_t values. Use %jd and an (intmax_t) cast to print off_t values. Use off_t variables to hold the difference between two off_t values. Don't bother with unsigned char where char will do nicely.
* Change the disk(9) API in order to make device removal more robust.phk2004-02-1828-273/+335
| | | | | | | | | | | | | | | | | | | | | | | | Previously the "struct disk" were owned by the device driver and this gave us problems when the device disappared and the users of that device were not immediately disappearing. Now the struct disk is allocate with a new call, disk_alloc() and owned by geom_disk and just abandonned by the device driver when disk_create() is called. Unfortunately, this results in a ton of "s/\./->/" changes to device drivers. Since I'm doing the sweep anyway, a couple of other API improvements have been carried out at the same time: The Giant awareness flag has been flipped from DISKFLAG_NOGIANT to DISKFLAG_NEEDSGIANT A version number have been added to disk_create() so that we can detect, report and ignore binary drivers with old ABI in the future. Manual page update to follow shortly.
* Add */lib/getopt* I miss somehow initially.ache2004-02-181-0/+2
|
* Correct minor typos.ceri2004-02-181-2/+2
|
* Only call chflags() on directories once.ceri2004-02-181-5/+4
| | | | | Approved by: ru MFC after: 1 week
* Remove thr_getschedparam.c since it's contents have been moved intomtm2004-02-181-1/+0
| | | | thr_setschedparam.c
* Add a -n option that stops ip6fw making any changes to the rulesdwmalone2004-02-182-29/+58
| | | | | | | in the kernel. Submitted by: Orla McGann <orly@redbrick.dcu.ie> MFC after: 3 weeks
* There are consumers of rwlocks, inluding our own libc, that depend onmtm2004-02-181-96/+24
| | | | | | | | | | a PTHREAD_RWLOCK_INITIALIZER to do for rwlocks what a similarly named symbol does for statically initialized mutexes. This symbol was dropped in The Open Group Base Specifications Issue 6 and does not exist in IEEE Std 1003.1, 2003, but it should still be supported for backwards compatibility. Pointy hat: mtm
* o Catch up with the mutex priority protocol fixes.mtm2004-02-182-121/+65
| | | | | o Move pthread_getschedparam() into the same file with it's pthread_set* counterpart. Copyright on both files is identical.
* o Stylemtm2004-02-182-48/+39
| | | | | | o Instead of checking both the passed in pointer and its value for NULL, only check the latter. Any caller that passes in a NULL pointer is obviously wrong.
* o Refactor and, among other things, get rid of insane nesting levels.mtm2004-02-182-811/+305
| | | | | | | o Fix mutex priority protocols. Keep separate counts of priority inheritance and protection mutexes to make things easier. This will not have much affect since this is only the userland side, and the rest involves kernel scheduling.
* Revamp the statistics code, and switch to a much more compact displaydes2004-02-181-48/+56
| | | | | format. The old code tried to produce the exact same output as the pre-libfetch implementation, but I no longer see any value in this.
* Move the initialization of thread priority to a common function.mtm2004-02-182-6/+3
|
* Move the weak references to the top of the file to conformmtm2004-02-181-43/+22
| | | | to the format of other similar files in libthr.
* Add partial support for large (>4GB) files on ext2 filesystems. Thistjr2004-02-186-2/+32
| | | | | | | | support is partial in that it will refuse to create large files on filesystems that haven't been upgraded to EXT2_DYN_REV or that don't have the EXT2_FEATURE_RO_COMPAT_LARGE_FILE flag set in the superblock. MFC after: 2 weeks
* o Fix a bridge example: sysctl net.inet.ip.forwarding=1 is needless,maxim2004-02-182-2/+2
| | | | | | | bridge(4) is working on a level below. Suggest sysctl net.inet.ip.check_interface=0 instead. MFC after: 2 weeks
* Add "-q" argument to setfmac and setfsmac to allow the patient butrwatson2004-02-183-13/+27
| | | | exhausted reader not to see non-fatal warnings.
* Use correct thousands separator for the Italian locale.cperciva2004-02-181-1/+1
| | | | | | | PR: misc/54477 Submitted by: Nicola Vitale <nivit@libero.it> Approved by: rwatson (mentor) Confirmed by: #freebsd, Google
* Don't ignore errors from vfs_allocate_syncvnode.cperciva2004-02-181-1/+1
| | | | | | PR: kern/18503 Submitted by: Anatoly Vorobey <mellon@pobox.com> Approved by: rwatson (mentor)
* Mention that kernel environment variables may be configured inwes2004-02-181-2/+8
| | | | | | /boot/loader.conf. Make the description flow a bit better. Complaints by: Nate Lawson <nate@root.org>
* Fix misspellings in the freebsd-tips fortunes. The same PR hascperciva2004-02-181-4/+4
| | | | | | | | | a patch to mention portupgrade in freebsd-tips as well; I'm not sure if that belongs here, so I'll leave it for someone else. PR: misc/37073 Submitted by: Sean Chittenden <sean@chittenden.org> Approved by: rwatson (mentor)
* Fixed some style bugs (spaces instead of tabs in macro definitions ...).bde2004-02-181-11/+11
|
* Checkpoint a hack to enable running i386 libc_r binaries on a 64 bitpeter2004-02-181-4/+22
| | | | | | kernel. I'm not happy with it yet - refinements are to come. This hack allows the kern.ps_strings and kern.usrstack sysctls to respond to a 32 bit request, such as those coming from emulated i386 binaries.
* Backout MT_TAG removal (i.e. bring back MT_TAGs) for now, as dummynet ismlaier2004-02-1817-465/+442
| | | | | | not working properly with the patch in place. Approved by: bms(mentor)
* remove dead coderees2004-02-171-53/+0
| | | | Approved by: alfred
* Add vector for memmove() (currently aliased to memcpy()) a implementwpaul2004-02-171-0/+20
| | | | ExInterlockedAddLargeStatistic().
* Make the distinction between sysctl kernel environment variables andwes2004-02-171-1/+4
| | | | | | | | | | | | | device.hints kernel environment variables when disabling ACPI. Some users are getting confused when they see hint.acpi.0.disabled. They are confusing it with a sysctl MIB. Finally, add a reference for device.hints(5) and kenv(1) in the "SEE ALSO" section of the man page. PR: docs/62974 Submitted by: Christian S.J. Peron <maneo@bsdpro.com>
* Dont use the bio_taskqueue if we are in timeout.sos2004-02-171-2/+2
| | | | | Use taskqueue_thread rather than taskqueue_swi (maybe we should have a taskqueue_ata).
* l2ping(8) should not loose echo data if target does not responds to the pingemax2004-02-172-24/+36
| | | | Reviewed by: imp (mentor), ru
* Do not place dirmask in unnamed padding. Move it to the bottom of thistrhodes2004-02-171-1/+1
| | | | | | list where it should have been added originally. Prodded by: bde
* IPSEC and FAST_IPSEC have the same internal API now;ume2004-02-177-105/+42
| | | | | | so merge these (IPSEC has an extra ipsecstat) Submitted by: "Bjoern A. Zeeb" <bzeeb+freebsd@zabbadoz.net>
* o Be consistent with the declaration: pri -> priority.maxim2004-02-171-2/+2
| | | | | Spotted by: Dmitry Rzhavin MFC after: 1 week
* Correct a comment.dwmalone2004-02-172-2/+2
| | | | Reviewed by: alfred, tanimura
* Backed out previous commit since it just causes panics unless a specialbde2004-02-171-1/+1
| | | | | | | | | | | | value for MSGBUF_SIZE is configured. MSGBUF_SIZE = (32768 * bootverbose ? 2 : 1) is always 1 or 2, so there is not enough space in the buffer for metadata, and blindly using the nonexistent space tends to cause fatal pagefaults. I think MSGBUF_SIZE = (32768 * (bootverbose ? 2 : 1)) would be always 32768 since bootverbose is only statically initialized to 0 early when MSGBUF_SIZE is used. MSGBUF_SIZE = (32768 * ((boothowto & RB_VERBOSE) ? 2 : 1)) should work, but this belongs in <sys/msgbuf.h> even less than previous versions. MSGBUF_SIZE shouldn't be a macro.
* Mechanical whistespace cleanup.des2004-02-171-19/+19
|
* Remove configurations which aren't used in production.des2004-02-174-31/+0
|
* Whitespace nit.des2004-02-171-1/+1
|
* If the "next free cluster" field of the FSInfo block is 0xFFFFFFFF,tjr2004-02-171-2/+4
| | | | | | | | | | it means that the correct value is unknown. Since this value is just a hint to improve performance, initially assume that the first non-reserved cluster is free, then correct this assumption if necessary before writing the FSInfo block back to disk. PR: 62826 MFC after: 2 weeks
* Report the difference between ufs and ufs2.grog2004-02-172-3/+16
| | | | Submitted by: "Christian S.J. Peron" <maneo@bsdpro.com>
* Re-add sio.S, and properly deal with assembler files.ru2004-02-174-383/+8
| | | | Repocopied by: joe
OpenPOWER on IntegriCloud