summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
...
* Add needed synchronization to the error handling code that was introducedalc2005-01-051-0/+6
| | | | | | in revision 1.141. Lock assertion failures reported by: Kris Kennaway
* o Use tab instead of spaces for puc(4) line.kuriyama2005-01-054-12/+12
| | | | o Use capitalized "Ethernet" for consistency.
* Fix comment. One of the two "Step 4" shuold be a "step 5"julian2005-01-051-1/+1
|
* Disable checksum offloading by default. It seems to produce corrupted packetscognet2005-01-051-2/+2
| | | | | | | with some revisions of the chip (particularly when using multiple TX descriptors). MFC after: 1 week
* Instead of keeping track of the index into the receive ring use the alreadyphk2005-01-042-8/+6
| | | | implemented "sis_nextdesc" pointer to keep a pointer instead.
* Forget about the sis_list_data and sis_ring_data structures and embeddphk2005-01-042-132/+109
| | | | | | | their fields directly in the softc structure. This is a no-op which shortens most of the affected source lines by N * 10 characters.
* Prototype busdma callback using the typedef.phk2005-01-041-1/+1
|
* Kill a half dead comment. It's first half was killed in rev 1.12.rik2005-01-041-1/+0
| | | | MFC after: 3 days
* Rename 'class' field to 'uclass' in the ng_hci_inquiry_response structure.emax2005-01-041-1/+1
| | | | | | | class is a reserved word in C++ Submitted by: Markus Brueffer < markus AT brueffer DOT de > MFC after: 3 days
* Allow fxp(4) cards with a revision id of 0 to use the 82503 serialmux2005-01-041-1/+1
| | | | | | | | | interface as well. This is not an expected revision id per the datasheet, but unfortunately there are such cards out there with a 82557 chipset, and they want to use the 82503. PR: kern/75739 Reported by: Andre Albsmeier <andre.albsmeier@siemens.com>
* Regenerate.jhb2005-01-044-13/+15
|
* Partial sync up to the master syscalls.master file:jhb2005-01-041-8/+9
| | | | | | | | - Mark mount, unmount and nmount MPSAFE. - Add a stub for _umtx_op(). - Mark open(), link(), unlink(), and freebsd32_sigaction() MPSAFE. Pointy hats to: several
* return after freeing data element, instead of falling through, and usingjmg2005-01-041-0/+1
| | | | | | the free'd element, and ultimate NULL deref of the failed allocation. MFC after: 1 week
* - Fix 'rebuild' command - it can no longer relay on retaste eventpjd2005-01-043-50/+34
| | | | | | | | (we ignore it). - Remove code used for handling spoil events, as spoiling is not possible anymore, because we keep consumers open for writing all the time. MFC after: 4 days
* Spoiling is now not possible, because we keep consumers open for writingpjd2005-01-043-38/+13
| | | | | | all the time. Remove unused code then. MFC after: 4 days
* Remove old wdc driver completely.nyan2005-01-041-8/+0
|
* Minor nits in formatting continued linesimp2005-01-041-2/+2
|
* cnw as a pccard device was commented out, so uncomment it so LINT will build.imp2005-01-041-1/+1
|
* Since we do not support forceful unmount of DEVFS we can do away withphk2005-01-041-45/+3
| | | | the partially implemented vnode-readoption code in vgonechrl().
* Unsupport forceful unmounts of DEVFS.phk2005-01-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After disscussing things I have decided to take the easy and consistent 90% solution instead of aiming for the very involved 99% solution. If we allow forceful unmounts of DEVFS we need to decide how to handle the devices which are in use through this filesystem at the time. We cannot just readopt the open devices in the main /dev instance since that would open us to security issues. For the majority of the devices, this is relatively straightforward as we can just pretend they got revoke(2)'ed. Some devices get tricky: /dev/console and /dev/tty for instance does a sort of recursive open of the real console device. Other devices may be mmap'ed (kill the processes ?). And then there are disk devices which are mounted. The correct thing here would be to recursively unmount the filesystems mounte from devices from our DEVFS instance (forcefully) and if this succeeds, complete the forcefully unmount of DEVFS. But if one of the forceful unmounts fail we cannot complete the forceful unmount of DEVFS, but we are likely to already have severed a lot of stuff in the process of trying. Event attempting this would be a lot of code for a very far out corner-case which most people would never see or get in touch with. It's just not worth it.
* Catchup to wd removalimp2005-01-041-12/+0
|
* Remove last vestiges of old wd driver. ata works well on pc98 andimp2005-01-048-5551/+0
| | | | | there was no objection on the pc98 list when I asked if it could be removed a while ago.
* move all the card entries to files.pc98imp2005-01-043-1734/+1732
| | | | style change: regularize tabbing
* First step in removing OLDCARD from FreeBSD 6.0:imp2005-01-042-6/+6
| | | | | o Move card from all architectures to just pc98. It is only needed there, although real issues remain with NEWCARD's support of ISA devices.
* Fix 'rebuild' command (we ignore retaste event now, so don't relay on it).pjd2005-01-033-11/+23
|
* Add PCI and device ID's to if_xl to support:rwatson2005-01-032-1/+6
| | | | | | | | | | | 3C920B-EMB-WNM Integrated Fast Ethernet Controller Submitter reports that the card appears to autonegotiate properly, and operate well with high levels of NFS traffic. PR: 75253 Submitted by: "Oleg V. Nauman" <oleg at reis dot zp dot ua> MFC after: 2 weeks
* Use byteorder(9) functions to implement the [g,s]et[d,w][b,l]e macros somarius2005-01-031-36/+14
| | | | | | | | | only one set is needed for either endianess. This also completes them for big endian archs and fixes the compilation of libncp, netncp, etc. there. Reviewed by: bp, rwatson Compile tested on: i386, sparc64 MFC after: 1 week
* When allocating bio's in the swap_pager use M_WAITOK since thephk2005-01-031-6/+7
| | | | alternative is much worse.
* Reduce diffs to work in progress before checking in serious changes.philip2005-01-032-38/+40
| | | | | | | | | | | | | | | | o Move the sysctls under debug.psm.* and hw.psm.* making them a bit clearer and more consistent with other drivers. o Remove the debug.psm_soft_timeout sysctl. It was introduced many moons ago in r1.64 but never referenced anywhere. o Introduce hw.psm.tap_threshold and hw.psm.tap_timeout to control the behaviour of taps on touchpads. People might like to fiddle with these if tapping seems to slow or too fast for them. o Add debug.psm.loglevel as a tunable so that verbosity can be set easily at boot-time (to watch probes and such) without having to compile a kernel with options PSM_DEBUG=N.
* Garbage collect unused ipx_abort().rwatson2005-01-032-13/+2
| | | | | | Spell NULL right in a KASSERT() panic message. MFC after: 1 week
* Remove unused #include.pjd2005-01-031-1/+0
|
* Exempt the superuser from mac_seeotheruids checks.rwatson2005-01-031-0/+3
| | | | | | Submitted by: bkoenig at cs dot tu-berlin dot de PR: 72238 MFC after: 2 weeks
* Remove comment that doesn't seem to be true and add comments describingjulian2005-01-031-17/+16
| | | | | | what is going on, to replace it. Slight formatting changes Code here is alredy different to NetBSD. MFC after: 1 week
* A much simpler way to work out if the required transfer can be done in 2julian2005-01-031-3/+2
| | | | | | scatter gather segments. MFC after: 1 week
* Back out previous commits. Installing new share/mk fixes this.njl2005-01-031-1/+0
|
* Add a sysctl (net.inet.tcp.insecure_rst) which allows one to specifysilby2005-01-032-2/+14
| | | | | | | that the RFC 793 specification for accepting RST packets should be following. When followed, this makes one vulnerable to the attacks described in "slipping in the window", but it may be necessary in some odd circumstances.
* NO_MAN is now NOMAN.njl2005-01-031-1/+1
|
* Fix kernel modules build. For some reason, this module now bails out withnjl2005-01-031-0/+1
| | | | an error that there is no aicasm.1 man page.
* Regen.marcel2005-01-035-6/+6
|
* uuidgen(2) is MP safe.marcel2005-01-031-1/+1
|
* If MALLOC() fails in at_pcballoc(), return ENOBUFS rather thanrwatson2005-01-031-1/+3
| | | | | | potentially panicking. MFC after: 1 week
* Acquire the socket buffer receive lock in spx_rcvoob() to permitrwatson2005-01-021-0/+3
| | | | multiple reads of receive buffer state to be performed atomically.
* Increase the coverage scope of the receive socket buffer lock inrwatson2005-01-021-10/+9
| | | | | | spx_reass() to increase atomicity across multiple operations on the socket buffer when iterating over the SPX fragment reassembly list for the ipxpcb, as well a to reduce the number of locking operations.
* Explicitly lock the send socket buffer in spx_reass() to cover the droprwatson2005-01-021-2/+3
| | | | | | | | record loop for ACK'd data, rather than relying on lokcing in sbdroprecord() and sowwakeup(), reducing the number of lock operations as well as eliminating a possible race against the head of the send buffer mbuf chain. Use the _locked variants of sbdroprecord() and sowwakeup().
* Restructure ipx_input() return code to match similar code in netinet,rwatson2005-01-021-8/+6
| | | | avoiding a goto.
* Eliminate XXX comments regarding allocation failures when retrievingrwatson2005-01-022-5/+5
| | | | | | the peer address by using M_WAITOK in ipx_setpeeraddr() to prevent allocation failure. The socket reference used to reach these calls will prevent the ipxpcb from being released prematurely.
* Use KASSERT() in preference to if()panic().rwatson2005-01-022-6/+2
|
* Extern declaration of old 'ipxpcb' list head no longer required.rwatson2005-01-021-2/+0
|
* Trim trailing whitespace.rwatson2005-01-029-37/+37
|
* Document copyright updates in netipx README as other prior updates haverwatson2005-01-021-0/+1
| | | | been documented.
OpenPOWER on IntegriCloud