summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
...
* Make device_detach methods really work.ru2005-09-142-2/+2
|
* Undo a tad little optimization to bpf_mtap() introduced in rev. 1.95andre2005-09-141-4/+0
| | | | | | | | | which broke the correct handling of the BIOCGSEESENT flag in the bpf listener. PR: kern/56441 Submitted by: <vys at renet.ru> MFC after: 3 days
* Increase boot-time DigiBIOS initialization timeout to allowandre2005-09-141-1/+1
| | | | | | | for a larger number of chained port modules. PR: kern/55018 Submitted by: Cyrill Shevchuk <cyrill at cyrills.net>
* Do not ignore all other TCP options (eg. timestamp, window scaling)andre2005-09-141-1/+1
| | | | | | | | when responding to TCP SYN packets with TCP_MD5 enabled and set. PR: kern/82963 Submitted by: <demizu at dd.iij4u.or.jp> MFC after: 3 days
* Remove bogous semicolons at the end of the definitions ofandre2005-09-142-7/+7
| | | | | | | 'do { ... } while (0)' macros. PR: kern/83088 Sumbitted by: <antoine.brodin at laposte.net>
* Harden the hotplug support for SATA devices.sos2005-09-144-51/+77
| | | | | | This also fixes a few races that was present in the timeout/detach code. Sponsored by: pair.com
* Add some defines for EPSON machines and use them.nyan2005-09-143-12/+29
|
* Remove EPSON PC-386 note A/W/AE/WR support.nyan2005-09-146-108/+12
|
* Fixed "Memory modified after free" panic in rl_detach() dueru2005-09-141-4/+3
| | | | | | to rl_stop() accessing already freed "struct ifnet". Fixed LOR between rl mutex and some ACPI mutex in rl_detach().
* Fix "Memory modified after free" panic on detach, caused by accessingru2005-09-141-3/+0
| | | | already freed struct ifnet.
* Fix panic when kernel compiled without INET6 by rejectingbz2005-09-141-6/+30
| | | | | | | IPv6 opcodes which are behind #if(n)def INET6 now. PR: kern/85826 MFC after: 3 days
* Bring aac_cam into line with using time_uptime instead of time_second.scottl2005-09-141-1/+1
|
* Use time_uptime for timing commands instead of time_second. This is a bitscottl2005-09-141-9/+9
| | | | | | | | | risky because the "current time" is supposed to be fed to the card during initialization, and the current time is supposed to be put into each command that is sent to the card. Hopefully either the card doesn't actually care about the timestamps, or it doesn't care about the absolute values so long and the relative values are consistent. Not an MFC candidate until more thorough testing can be done.
* Fix module unload panic which was caused by missing sx lock release.yongari2005-09-141-1/+5
| | | | | | | While I'm here add KASSERT(9) to notify failure of SYSUNINIT handler. Reported by: Ben Kaduk < minimarmot AT gmail DOT com > Tested by: Ben Kaduk < minimarmot AT gmail DOT com >
* MFp4: Migrate from CARD_CIS_SCAN to pccard_cis_scanimp2005-09-131-1/+1
|
* MFp4:imp2005-09-131-37/+13
| | | | | | o Use pccard_cis_scan o use pccard_attr_write_1 o Update comments
* MFp4: Omnibus ed changesimp2005-09-134-198/+285
| | | | | | | | | | | | | | | | | | | o Attach AX88x90's MII bus to system, and require its presence. o Reorg the mii code a little, and move more of it into pccard attachment. o Eliminate ed_pccard_{read,write}_attrmem in favor of a more appropriate function in the pccard layer. o Update comments to reflect knowledge gained. o Update how re recognize a NE-2000 ROM. I found a couple of different datasheets that define the structure of the PROM data, so the code's old heuristics have been removed, and comments updated to reflect the structure. o Eliminate work around for EC2T. It is no longer needed, and was wrong headed since the EC2T has a Winbound 82C926C in it, not a AX88x90. o Add copyright to if_ed_pccard.c, since I believe I've re-written more than 3/4 of it. # With these changes, all of my 20-odd ed based cards work, except for the # NetGear FA-410, and I'm pretty sure that's a MII/PHY problem.
* MFp4:imp2005-09-131-73/+40
| | | | | o Move to new pccard_cis_scan convenience function. o Remove compat layer goo.
* Use new convenience function to read CIS rather than the older, harder toimp2005-09-131-2/+1
| | | | use version.
* MFp4: Minor formatting nits in pccard table.imp2005-09-131-9/+9
|
* Use smaller names. The "NE2000 PCI Ethernet" is largerly redundantimp2005-09-131-9/+9
| | | | | with edX at pciY. This removes 8*22 bytes from the strings. Not a huge win, but a cheap one.
* Add the olicom OC2231 and OC2232 to the list of cards that we shouldimp2005-09-131-0/+2
| | | | | | | attach to. These cards are combo cards (in that they have a modem inside of them), but not true MFC cards. Full support of these cards will have to wait until we can pick the config to use and for the PFC support that I have brewing.
* Add a few new functions interfaces to allow reading/writing attributeimp2005-09-134-11/+172
| | | | memory, the CCR and a tweak to cis_scan.
* Define and use PCCARD_MEM_PAGE_SIZE.imp2005-09-132-1/+3
|
* Trim down now (believed to be) unused fifo_ioctl() andrwatson2005-09-131-65/+75
| | | | | | | | | | | | | | | | | | | | | | fifo_kqfilter() VOP implementations, since they in theory are used only on open file descriptors, in which case the ioctls are via fifo_ioctl_f() and kqueue requests are via fifo_kqfilter_f(). Generate warnings if they are entered for now. These printf() calls should become panic() calls. Annotate and re-implement fifo_ioctl_f(): don't arbitrarily forward ioctls to the socket layer, only forward the ones we explicitly support for fifos. In the case of FIONREAD, don't forward the request to the write socket on a read-write fifo, or the read result is overwritten. Annotate a nasty case for the undefined POSIX O_RDWR on fifos, in which failure of the second ioctl will result in the socket pair being in an inconsistent state. Assert copyright as I find myself rewriting non-trivial parts of fifofs. MFC after: 3 days
* MFp4: Remove stale functions.imp2005-09-131-21/+0
|
* Remove unused functions.nyan2005-09-131-39/+0
|
* Remove EPSON_NRDISK support.nyan2005-09-131-177/+2
|
* As a result of kqueue locking work, socket buffer locks will alwaysrwatson2005-09-131-18/+6
| | | | | | | | be held when entering a kqueue filter for fifos via a socket buffer event: as such, assert the lock unconditionally rather than acquiring it conditionall. MFC after: 3 days
* Unlock driver lock before calling resource_int_value(9).yongari2005-09-131-0/+3
| | | | This should fix LOR(in fact it's not LOR) in device attach.
* Annotate two issues:rwatson2005-09-131-0/+12
| | | | | | | | | | | | 1) fifo_kqfilter() is not actually ever used, it likely should be GC'd. 2) fifo_kqfilter_f() doesn't implement EVFILT_VNODE, so detecting events on the underlying vnode for a fifo no longer works (it did in 4.x). Likely, fifo_kqfilter_f() should forward the request to the VFS using fp->f_vnode, which would work once fifo_kqfilter() was detached from the vnode operation vector (removing the fifo override). Discussed with: phk
* MFi386: revision 1.11.nyan2005-09-131-9/+108
|
* MFi386: revisions 1.10 and 1.11.nyan2005-09-131-1/+2
| | | | - Add '-mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3' to CFLAGS.
* Introduce no-op nosup fifo kqueue filter and detach routine, which arerwatson2005-09-121-1/+33
| | | | | | | | | | | | | | | | used when a read filter is requested on a write-only fifo descriptor, or a write filter is requested on a read-only fifo descriptor. This permits the filters to be registered, but never raises the event, which causes kqueue behavior for fifos to more closely match similar semantics for poll and select, which permit testing for the condition even though the condition will never be raised, and is consistent with POSIX's notion that a fifo has identical semantics to a one-way IPC channel created using pipe() on most operating systems. The fifo regression test suite can now run to completion on HEAD without errors. MFC after: 3 days
* In netkqfilter(), return EINVAL instead of 1 (EPERM) when a filter typerwatson2005-09-121-1/+1
| | | | | | is requested on a network interface file descriptor that is non-applicable. MFC after: 3 days
* In vfs_kqfilter(), return EINVAL instead of 1 (EPERM) when an unsupportedrwatson2005-09-121-1/+1
| | | | | | kqueue filter type is requested on a vnode. MFC after: 3 days
* - Fix the locking in dsp.c to prevent a LOR (AFAIK not on the LOR page).netchild2005-09-122-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | - Remove an assertion in sound.c, it's not needed (and causes a panic now). From the conversation via mail between glebius and Ariff: ---snip--- > Well, but which mutex protects now? Do we own anything else > in pcm_chnalloc()? I see some queue(4) macros in pcm_chnalloc(), > they should be protected, shouldn't they? Queue insertion/removal occur during 1) driver loading (which is pretty much single thread / sequential) or unloading (mutex protected, bail out if there is any channel with refcount > 0 or busy). 2) vchan_create()/destroy(), (which is *sigh* quite complicated), but somehow protected by 'master'/parent channel mutex. Other thread cannot add/remove vchan (or even continue traversing that queue) unless it can acquire parent channel mutex. ---snip--- Fix the locking in dsp.c to prevent a LOR (AFAIK not on the LOR page). Submitted by: Ariff Abdullah <skywizard@MyBSD.org.my> Tested with: INVARIANTS[1] and DIAGNOSTICS[2] Tested by: netchild [1,2], David Reid <david@jetnet.co.uk> [1]
* When a request is made to register a filter on a fifo that doesn'trwatson2005-09-121-2/+2
| | | | | | | apply to the fifo (i.e., not EVFILT_READ or EVFILT_WRITE), reject it as EINVAL, not by returning 1 (EPERM). MFC after: 3 days
* Process one NMI interrupt per handler invocation as the processorjkoshy2005-09-121-4/+9
| | | | | | | | 'buffers' pending NMIs from multiple interrupting PMCs and delivers them serially. Reported by: Olivier Crameri <olivier.crameri@epfl.ch> MFC after: 3 days
* use monotonic `time_uptime' instead of `time_second'jkim2005-09-121-4/+4
| | | | | Approved by: anholt (mentor) Discussed on: arch
* When message can't fit into socket receive buffer return ENOBUFSglebius2005-09-121-2/+3
| | | | | | to userland program instead of letting it wait until end of days. PR: kern/85907
* opt_pc98.h is not needed.nyan2005-09-121-3/+0
|
* more #ifndef PC98. This really fix the pc98 tinderbox.nyan2005-09-121-0/+4
|
* Remove DFLAG_SEEKABLE from fifo file descriptors: fifos are not seekablerwatson2005-09-121-1/+1
| | | | | | according to POSIX, not to mention the fact that it doesn't make sense (and hence isn't really implemented). This causes the fifo_misc regression test to succeed.
* Only poll the fifo for read events if the fifo is attached to a readablerwatson2005-09-121-2/+2
| | | | | | | | | | | | | | file descriptor. Otherwise, the read end of a fifo might return that it is writable (which it isn't). Only poll the fifo for write events if the fifo attached to a writable file descriptor. Otherwise, the write end of a fifo might return that it is readable (which it isn't). In the event that a file is FREAD|FWRITE (which is allowed by POSIX, but has undefined behavior), we poll for both. MFC after: 3 days
* After going to some trouble to identify only the write-related eventsrwatson2005-09-121-2/+2
| | | | | | | | | to poll the write socket for, the fifo polling code proceeded to poll for the complete set of events. Use 'levents' instead of 'events' as the argument to poll, and only poll the write socket if there is interest in write events. MFC after: 3 days
* When a writer opens a fifo, wake up the read socket for read, not therwatson2005-09-121-1/+1
| | | | | | write socket. MFC after: 3 days
* Add an assertion that fifo_open() doesn't race against other threadsrwatson2005-09-121-0/+2
| | | | | | | while sleeping to allocate fifo state: due to using the vnode lock to serialize access to a fifo during open, it shouldn't happen (tm). MFC after: 3 days
* Rather than reaching into the internals of the UNIX domain socket coderwatson2005-09-121-1/+1
| | | | | | | by calling uipc_connect2() to connect two socket endpoints to create a fifo, call soconnect2(). MFC after: 3 days
* Introduce vfs_read_dirent() which can help VOP_READDIR() implementationsphk2005-09-122-0/+29
| | | | by handling all the cookie stuff.
OpenPOWER on IntegriCloud