summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Add detection code for NVidia Riva 128,TNT,TNT2ache1999-06-091-1/+19
| | | | | | | (TNT2 from me) PR: 12094 Submitted by: Ilya Naumov camel@avias.com
* Use kmem_alloc_nofault() rather than kmem_alloc_pageable() to allocatedt1999-06-083-6/+6
| | | | kernel virtual address space for UPAGES.
* Add a function kmem_alloc_nofault() - same as kmem_alloc_pageable(), butdt1999-06-082-2/+27
| | | | | | create a nofault entry. It will be used to allocate kmem for upages. (I am not too happy with all this, but it's better than nothing).
* Keep fpcurproc locked in memory, so that we always can save the FP statedt1999-06-087-14/+35
| | | | | | | | correctly. This should fix the "pmap_changebit didn't" panic that some people see. Reviewed by: dfr
* From the submitter:msmith1999-06-072-21/+18
| | | | | | | | | | | | | | | | | - this causes POSIX locking to use the thread group leader (p->p_leader) as the locking thread for all advisory locks. In non-kernel-threaded code p->p_leader == p, so this will have no effect. This results in (more) correct POSIX threaded flock-ing semantics. It also prevents the leader from exiting before any of the children. (so that p->p_leader will never be stale) in exit1(). We have been running this patch for over a month now in our lab under load and at customer sites. Submitted by: John Plevyak <jplevyak@inktomi.com>
* ksprintn() may be called with base=2, so redefine MAXNBUF accordingly.archie1999-06-071-18/+19
| | | | | | Other brucification tweaks. Obtained from: bde@freebsd.org
* The FD options are now in /sys/conf/options so need to duplicate themsteve1999-06-062-8/+2
| | | | here and keep people from building new kernels. :)
* Small optimization: use wi_seek() in wi_read_record() and wi_write_record()wpaul1999-06-062-54/+18
| | | | | instead of frobbing the buffer access path registers directly. Saves a few lines of duplicated code.
* Sync with sys/i386/conf/majors.i386 revision 1.76.kato1999-06-061-1/+2
|
* Sync with sys/boot/i386/libi386/bootinfo.c revision 1.19.kato1999-06-061-1/+5
|
* Reserve cdev major 126 for sync support.phk1999-06-062-2/+4
|
* typo in previous commitphk1999-06-061-2/+2
|
* Introduce IFF_SMART bit.phk1999-06-062-6/+10
| | | | | | | | This means that the driver will add/delete routes when it knows it is up/down, rather than have the generic code belive it is up if configured. This is probably most useful for serial lines, although many PHY chips could probably tell us if we're connected to the cable/hub as well.
* The function ksprintn(), which is used to convert numbers to ASCII, is notarchie1999-06-061-8/+14
| | | | | reentrant because it returns a static buffer. This results in a race condition when/if an interrupt handler calls log(), printf() etc. Fix this.
* vm_mmap:alc1999-06-051-3/+4
| | | | | | | Insure that device mappings get MAP_PREFAULT(_PARTIAL) set, so that 4M page mappings are used when possible. Reviewed by: Luoqi Chen <luoqi@watermarkgroup.com>
* Fix an accounting problem when prefaulting 4M pages.luoqi1999-06-052-4/+4
| | | | PR: kern/11948
* Floppy driver options moved to conf/options.dfr1999-06-053-9/+6
|
* * Implement ISA dma (only for CIA now but more chipsets to follow).dfr1999-06-0513-20/+1115
| | | | * Port the fd driver to alpha.
* Various changes lifted from the OpenBSD cvs tree:peter1999-06-0519-165/+228
| | | | | | | | | | | | | | | txdr_hyper and fxdr_hyper tweaks to avoid excessive CPU order knowledge. nfs_serv.c: don't call nfsm_adj() with negative values, windows clients could crash servers when doing a readdir of a large directory. nfs_socket.c: Use IP_PORTRANGE to get a priviliged port without a spin loop trying to bind(). Don't clobber a mbuf pointer or we get panics on a NFS3ERR_JUKEBOX error from a server when reusing a freed mbuf. nfs_subs.c: Don't loose st_blocks on NFSv2 mounts when > 2GB. Obtained from: OpenBSD
* Fix a malloc racepeter1999-06-052-6/+24
| | | | Obtained from: OpenBSD (csapuntz)
* Don't mistake a non-async block that needs to be committed for anpeter1999-06-052-4/+4
| | | | | | interrupted write. Obtained from: fvdl@NetBSD.org via OpenBSD.
* Restructure pipe_read in order to eliminate several race conditions.alc1999-06-051-68/+46
| | | | Submitted by: Matthew Dillon <dillon@apollo.backplane.com> and myself
* Fixed null setting of `rc_started'. This was fixed for thebde1999-06-042-14/+4
| | | | | | | | | | corresponding variable `rc_wakeup_started' in rev.1.36 but broken again in rev.1.37. This bug only caused excessive polling (it gave NRC activations for each of the SWI handler and the timeout handler instead of 1 of each). Moved cdevsw attachment from the driver probe routine to the driver attach routine.
* Really fix cy-driver-related panics when SMP is configured. Rev.1.88 onlybde1999-06-043-9/+15
| | | | | | fixed half the problem. Tested by: Michael Scott Boers <mboers@datacompusa.com>
* Fix the cdevsw_add change made by PHK.roger1999-06-042-10/+10
| | | | | (It was accidentally added to the BSDI bktr_probe and not the FreeBSD bktr_probe)
* Add remark about where bInterfaceProtocol number for USB Zip drive comesn_hibma1999-06-041-1/+1
| | | | | | from. 0x50 == 'P' for protoype. Obtained from: Pat LaVarre <LAVARRE@iomega.com> on linux-usb@suse.com
* Oops, remove redundant comments.kato1999-06-041-3/+3
|
* Declare Crtat and Atrat because screen savers use these variables.kato1999-06-041-1/+7
| | | | Pointed out by: Nobuyuki Koganemaru <kogane@koganemaru.co.jp>
* Modify the boot loader to recognize the -C flag and pass the RB_CDROMghelmer1999-06-043-3/+15
| | | | | | | | | | | flag to the kernel to mount a CDROM as the root filesystem. Alternatively, the boot_cdrom env var can be set. As Mike Smith noted, "-C is the "wrong" way to do this", but this is an acceptable stopgap in lieu of a better way. PR: bin/11884 Reviewed by: msmith@freebsd.org
* Add the 3Dfx Voodoo Bansheemharo1999-06-041-1/+9
|
* Plug a mbuf leak in tcp_usr_send(). pru_send() routines are expectedpeter1999-06-042-8/+38
| | | | | | | | | | | | | | | | | | | | | | | | | to either enqueue or free their mbuf chains, but tcp_usr_send() was dropping them on the floor if the tcpcb/inpcb has been torn down in the middle of a send/write attempt. This has been responsible for a wide variety of mbuf leak patterns, ranging from slow gradual leakage to rather rapid exhaustion. This has been a problem since before 2.2 was branched and appears to have been fixed in rev 1.16 and lost in 1.23/1.28. Thanks to Jayanth Vijayaraghavan <jayanth@yahoo-inc.com> for checking (extensively) into this on a live production 2.2.x system and that it was the actual cause of the leak and looks like it fixes it. The machine in question was loosing (from memory) about 150 mbufs per hour under load and a change similar to this stopped it. (Don't blame Jayanth for this patch though) An alternative approach to this would be to recheck SS_CANTSENDMORE etc inside the splnet() right before calling pru_send() after all the potential sleeps, interrupts and delays have happened. However, this would mean exposing knowledge of the tcp stack's reset handling and removal of the pcb to the generic code. There are other things that call pru_send() directly though. Problem originally noted by: John Plevyak <jplevyak@inktomi.com>
* Remove a rather bogus search path reference..peter1999-06-033-3/+3
|
* GC unused prototypepeter1999-06-031-2/+1
|
* Quieten the bt_isa_probe() messages since they get a bit much whenpeter1999-06-033-9/+12
| | | | the isa probe has gone hunting for a card on it's own.
* remove references to isa_device, it's no longer associated with interrupts.peter1999-06-032-10/+2
|
* Remove VM86 option.kato1999-06-031-5/+4
|
* Sync with sys/i386/i386/machdep.c revision 1.339.kato1999-06-032-590/+1118
| | | | | | | | New function getmemsize_pc98 is added in this commit, since PC98 is quite different in obtaining memory size from IBM-PC. Many lines of this function is shareable with IBM-PC's getmemsize function, but sharing needs many #ifdef PC98 statements. Therefore, I gave up sharing code with IBM-PC's and just added new function.
* Sync with sys/i386/conf/files.i386 and options.i386 revisions 1.246kato1999-06-034-8/+6
| | | | and 1.115, respectively.
* Fix PS/2 MouseMan+ protocol. We have been looking at a wrong placeyokota1999-06-032-4/+4
| | | | for the sign bit for roller movement!
* Use MACHINE_ARCH instead of MACHINE to check x86 architecture.kato1999-06-031-2/+2
| | | | Pointed out by: Akio Morita <amorita@meadow.scphys.kyoto-u.ac.jp>
* Backed out the previous backout. We may as well have a version of ucmpdi2.cbde1999-06-021-2/+2
| | | | that actually compiles, and I use it for i386's with 64 bit longs.
* Back out last commit (did I get all of them?)newton1999-06-022-0/+6
| | | | Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
* Remove vinum from the build until Greg reviews phk's cdevsw changes.jb1999-06-021-2/+3
| | | | Preferred by: phk (rather than committing the patch without review).
* Unbreak memory sizing for SMP.jlemon1999-06-013-23/+33
|
* || vs && confusion in cdevsw_add().dt1999-06-011-2/+2
|
* Remove an unused variable.dt1999-06-012-4/+2
|
* cdevsw_add(&cn_devsw), not cdevsw_add(&dev).dt1999-06-011-3/+2
|
* Change the warning message issued if pci_map_port() fails. I think thiswpaul1999-06-011-5/+5
| | | | | | | | | | happens if you have a BIOS with a 'Plug & Play OS' setting and you leave it set to 'Yes.' This is wrong for FreeBSD (and LoseNT): it should be set to 'No.' Apparently it's still possible to map the iobase of the NIC and have the card work by reading the config space manually (which is what the driver does if pci_map_port() fails) but we need to warn the user to do fix their machine anyway. Anyway, warn the user to check the 'Plug & Play OS' setting in their BIOS if mapping the io space fails.
* Introduce the makebdev() function, it does the same as the makedev()phk1999-06-016-25/+33
| | | | function for now, but that will change.
* Null commit; note that there is a new memory sizing routine that usesjlemon1999-06-012-2/+2
| | | | | | | the BIOS calls to determine the memory configuration. This should fix problems with >64M for good. Reviewed by: Mike Smith
OpenPOWER on IntegriCloud