summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Use vtopde() instead of pmap_pde() in pmap_kextract(); vtopde() is smalleralc2004-12-211-1/+1
| | | | | and faster in cases, such as pmap_kextract(), where the pde is known to exist.
* This should not be permitted, but some GEOM classes held the topology lockpjd2004-12-211-6/+30
| | | | | | while doing g_(read|write)_data() (e.g. BSD). This can cause a deadlock in MIRROR class. Not sure if this is safe to drop the topology lock in BSD class, so change the code in MIRROR class to avoid this deadlock.
* Implement g_topology_try_lock().pjd2004-12-211-0/+2
| | | | No objection from: phk
* NOFORTH -> NO_FORTHru2004-12-219-9/+9
|
* - The IQ80321 has a jumper which changes the PCI device id from 4 to 8 for thecognet2004-12-211-5/+13
| | | | | | | | | GigE controller, so handle this. - Use the outbound window 0 if the PCI mem requested is in its range, instead of inconditionally use the outbound window 1. This should be enough to get FreeBSD/arm to work on the IQ80321 board as well. Reported and tested by: Jia-Shiun Li <jiashiun at gmail dot com>
* NOINET6 -> NO_INET6ru2004-12-213-4/+4
|
* NOCRYPT -> NO_CRYPTru2004-12-212-2/+2
|
* NOSHARED -> NO_SHAREDru2004-12-213-3/+3
|
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-2126-26/+26
| | | | OK'ed by: core
* GEOMify the OFW disk driver. Code taken unashamedly fromgrehan2004-12-211-147/+126
| | | | the preload case in dev/md/md.c.
* Protect the NM expansion.obrien2004-12-211-1/+1
|
* Fix a mis-sort.obrien2004-12-211-1/+1
|
* Hide/remove various printfs, now that root mounting doesn't seem to explodephk2004-12-201-9/+2
| | | | on people.
* fix a misleading sleep identifier.phk2004-12-201-1/+1
|
* We can only ever get to vgonechrl() from a devfs vnode, so we do notphk2004-12-203-4/+2
| | | | | | | need to reassign the vp->v_op to devfs_specops, we know that is the value already. Make devfs_specops private to devfs.
* Oops, this one isn't readyjulian2004-12-201-625/+87
| | | | back it out until fixed
* Add a couple of KASSERTS to try to diagnose a problem reported.phk2004-12-201-1/+5
|
* Add a bunch of USB definitions from NetBSD.julian2004-12-201-87/+625
| | | | | | | | | | | This is part of an ongoing cycle of commits on all the BSDs to merge the USB vendor and device defintions.. A merge from OpenBSD is still pending. Submitted by: barry bouwsma (freebsd-misuser@NOSPAM.dyndns.dk) Obtained from: NetBSD MFC after: 1 week
* Merge in a bunch of USB device and manufacturer definitions..julian2004-12-201-75/+97
| | | | | | Submitted by: barry bouwsma (freebsd-misuser@NOSPAM.dyndns.dk) Obtained from: Dragonfly MFC after: 3 days
* Only use the current value if there's one IRQ. Some systems returnnjl2004-12-201-8/+8
| | | | | | | | | multiple IRQs (which is nonsense for _CRS) when the link hasn't been programmed. Before, this was a KASSERT. A ServerWorks system was seen returning IRQs of 0, 2 in response to _CRS before link setup. Thanks to sam@ for quick testing and turnaround on this. Tested by: sam
* Only try to use the 82503 serial interface for the 82557 chipsets. Themux2004-12-201-2/+2
| | | | | | | | | datasheet says it is only valid for such chipsets and shouldn't be used with others. This fixes some 82559 based cards which otherwise only work at 10Mbit. MFC after: 5 days Tested by: krion
* Enable jumbo frames on Yukon variants of sk(4).bz2004-12-202-4/+18
| | | | | | | | | | In contrast to OpenBSD we enable jumbo frame support depending on MTU setting (like done for xmac). Approved by: pjd (mentor) Obtained from: OpenBSD if_sk.c r1.52 (YU_SMR_MFL_JUMBO flag) Tested by: Heinz Knocke <knockefreebsd at o2 dot pl> MFC after: 5 days
* Only report a critical battery level once until it's gone non-critical.njl2004-12-201-3/+9
| | | | | | | An improvement would be to check all batteries for critical state before printing a message. Reported by: Kevin Oberman (oberman at es net)
* add ancillary wlan modules and fixup commentssam2004-12-201-2/+16
| | | | Requested by: silby
* Remove unused variables.pjd2004-12-191-6/+1
|
* - Argument 'flags' in g_mirror_destroy_consumer() function is unsed -pjd2004-12-191-2/+3
| | | | | | mark it as such. - Before closing consumer check if it is open. It can be closed here when g_mirror_connect_disk() fails on g_access().
* Some major cleanups.pjd2004-12-191-175/+107
| | | | | | | | | | | | | | | | | | | | | | Keeping consumers open when device is closed is very hard. We need to open consumers sometimes to update metadata, etc. Many hacks was introduced in the past to made it possible. You cannot be sure that you can open consumer for writing always, even if you think it should be allowed. If one of the mirror components is for example da0 and you try to open it, you can get EPERM when da0s1 is opened for reading (because BSD class opens consumers (da0) with an extra 'e' bit set). Waiting for the events queue to be empty may do the trick, but it makes code much uglier (as you cannot always call g_waitidle()), it doesn't solve all edge cases and it can introduce deadlocks if there are events in the queue that wait for gmirror. I removed those hacks. Now all consumers are open r1w1e1 always, even if device is closed. Maybe it is less clean from GEOM perspective, but simpify code a lot and make it much more reliable. The only issue was retaste event which is sent when we close consumers opened for writing. I ignore retaste event by not detaching consumer immediately (so retaste event is not send to my class) and sending event right after it to detach and destroy consumer.
* Don't quit on first failure, just skip failures.pjd2004-12-191-6/+6
|
* Initialise init_addr in pf_map_addr() in the PF_POOL_ROUNDROBIN,dhartmei2004-12-191-3/+5
| | | | | | | | | | | | | | prevents a possible endless loop in pf_get_sport() with 'static-port' ICMP state entries use the ICMP ID as port for the unique state key. When checking for a usable key, construct the key in the same way. Otherwise, a colliding key might be missed or a state insertion might be refused even though it could be inserted. The second case triggers the endless loop, possibly allowing a NATed LAN client to lock up the kernel. PR: kern/74930 Reported and tested by: Hugo Silva, Srebrenko Sehic MFC after: 3 days
* Move launching the worker thread from a SYSINIT to the first device'snjl2004-12-191-4/+10
| | | | | attach. This fixes the previous behavior where systems without hptmv hardware always had a worker thread running.
* We already have ng_fec.4 manpage. And sys/modules is not a correctglebius2004-12-191-8/+0
| | | | place for documentation.
* Assert queue mutex in ng_dequeue() and ng_queue_rw().glebius2004-12-191-0/+4
|
* Update the StrongArm port to match the current code.cognet2004-12-183-6/+15
| | | | | | - Implement arm_mask_irqs and arm_unmask_irqs - Provide the available physical address range after pmap_bootstrap allocated things, instead or before, or bad things happen.
* Make sure gcc doesn't generate something such as swp r3, r4, [r3] for __swp,cognet2004-12-181-1/+1
| | | | as it has unpredictable results.
* Add support for FC929X, which apparently is just a PCI-X version of FC929.sobomax2004-12-181-0/+7
| | | | MFC after: 3 days
* 1. msleep returns EWOULDBLOCK not ETIMEDOUT, use EWOULDBLOCK instead.davidxu2004-12-181-8/+6
| | | | 2. Eliminate a possible lock leak in timed wait loop.
* 1. make umtx sharable between processes, the way is two or more processesdavidxu2004-12-189-180/+616
| | | | | | | | | | call mmap() to create a shared space, and then initialize umtx on it, after that, each thread in different processes can use the umtx same as threads in same process. 2. introduce a new syscall _umtx_op to support timed lock and condition variable semantics. also, orignal umtx_lock and umtx_unlock inline functions now are reimplemented by using _umtx_op, the _umtx_op can use arbitrary id not just a thread id.
* Make ip_nat compile again. Should read #if->n<-def LARGE_NAT as in ipf 4.xmlaier2004-12-181-1/+1
|
* Slight change to formatting so that 'ctags' doesn'tjulian2004-12-181-1/+3
| | | | | | | give up on teh file half way through.. Might have been my mistake earlier anyhow. No actual code change MFC after: 5 days
* Add support for the 5721 which seems to be similar to the 5750/5751.ps2004-12-172-0/+3
| | | | Tested by: Vivek Khera vivek at khera dot org
* Diff reduce wi_write_wep() relative to revision 1.168mdodd2004-12-171-41/+38
|
* Eliminate another unnecessary call to vm_page_busy(). (See revision 1.333alc2004-12-171-5/+0
| | | | for a detailed explanation.)
* Recognize the 32-bit form of the twe binary passthrough ioctl()s so thatpeter2004-12-172-0/+59
| | | | | | | there is some hope for the 32-bit management utilities to run. I've used the cli successfully, but 3dm2 doesn't work for other reasons. Of course, a native binary of the 3dm2 and cli would be much better, but that doesn't exist.
* Enable debug.mpsafevm by default on alpha.alc2004-12-171-1/+1
|
* Move two variables that are unused if LARGE_NAT is defined inside an #ifdefdarrenr2004-12-171-1/+4
| | | | | | to keep them out of harms way when compiling. PR: 72783
* Fix wep operation for station mode:sam2004-12-171-4/+28
| | | | | | | | | | o don't encapsulate on tx; the chip expect a raw frame w/o the crypto header o clear the WEP bit in the 802.11 header on rx so the 802.11 layer doesn't try to strip the crypto header o clobber the "drop unencoded frames" state bit when privacy is enabled so rx'd frames we pass up to the 802.11 layer are not discarded as unencrypted This stuff will need to be redone if anyone decides to add WPA support.
* set ic_ibss_chan when entering RUN state to match ic_bss so the channelsam2004-12-171-0/+1
| | | | reported when associated to an AP is correct
* don't try to recurse on the bpf lock.. kqueue already locks the bpf lockjmg2004-12-171-2/+1
| | | | | | | now... Submitted by: Ed Maste of Sandvine Inc. MFC after: 1 week
* remove power save logic from the tx path; the driver isn't ready to supportsam2004-12-171-6/+0
| | | | it so don't mislead folks
* Allow ipnat redirect rules to work for non-TCP/UDP packets.darrenr2004-12-171-3/+5
| | | | | | | PR: 70038 Submitted by: fming@borderware.com Reviewed by: darrenr Obtained from: fming@borderware.com
OpenPOWER on IntegriCloud