summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Fix YMF719 detection (report by jose@we.lc.ehu.es).luigi1999-01-043-12/+27
| | | | | Fix compile problems without "controller pnp0" (fix by German Tischler)
* Fix a potential sign extension bug on 8-bit chars.peter1999-01-041-3/+3
| | | | | Outputting a backspace isn't supposed to be destructive.. It isn't on most terminals, nor on the standard bios output (vs. TERM_EMU mode)
* Fix variable initialization.. It was written with '==' instead of '-'.peter1999-01-041-2/+3
| | | | #include <string.h> for string prototypes.
* Clean some unused variables lintpeter1999-01-041-2/+4
|
* Don't forget a trailing \n when loading a kernel that has been stripped.peter1999-01-041-7/+8
| | | | | (This might make ELF_VERBOSE look funny, but I'm tempted to delete that anyway)
* Bring in ad1816 patches from German Tischler.luigi1999-01-049-18/+1748
| | | | | Fix 'device not configured' problem that people were experiencing when only PCI devices are present.
* Sync with sys/i386/conf/options.i386 revision 1.101.kato1999-01-042-2/+42
|
* Sync with sys/i386/conf/majors.i386 revision 1.59.kato1999-01-041-1/+2
|
* Sync with sys/i386/conf/files.i386 revision up to 1.217.kato1999-01-042-2/+140
|
* Sync with sys/i386/boot/rawboot/Makefile revision 1.12.kato1999-01-041-4/+3
|
* Sync with sys/i386/boot/netboot/Makefile revision 1.22.kato1999-01-041-6/+3
|
* Sync with sys/i386/boot/kzipboot/Makefile revision 1.10.kato1999-01-041-3/+3
|
* Sync with sys/i386/boot/biosboot/Makefile revision 1.68.kato1999-01-041-14/+5
|
* Sync with sys/i386/boot/Makefile.inc revision up to 1.5.kato1999-01-041-1/+3
|
* Restore dependancy to build loader.help heremsmith1999-01-041-2/+2
|
* Add dependancy to build loader.help heremsmith1999-01-041-1/+1
|
* Temporary workaround (bandaid) for case where you have READmjacob1999-01-031-3/+5
| | | | | | | | CAPACITY fail for a non-removable media device. There's a race condition where the device entry is removed and then xpt_release_ccb is called which attempts to give back the ccb to a device that's now gone. In this bandaid release the ccb early and then remember to not call xpt_release_ccb later.
* First cut at generating loader.help for the alphamsmith1999-01-031-0/+12
|
* Reenable generation of the loader.help filemsmith1999-01-031-9/+9
|
* Recognize IDE controler even if HDD is not connected.kato1999-01-031-1/+23
| | | | Submitted by: IMAI Takeshi <take-i@ceres.dti.ne.jp>
* Corrected the major number for usb and added ums as major 111n_hibma1999-01-034-6/+8
|
* - Remove bus-dependent addresses from `ic' file.kato1999-01-035-126/+236
| | | | | | | | - Special registers of IO-DATA device's RSA series are defined in ic/rsa.h (new file). Pointed out by: Bruce Evans <bde@zeta.org.au> Submitted by: Takahashi Yoshihiro <nyan@wyvern.cc.kogakuin.ac.jp>
* catch a /boot doc instance I missed.jkh1999-01-033-6/+6
|
* Revert r1.4 - I was confused as to its real meaning.jkh1999-01-031-1/+1
| | | | Noted by: bde
* Support following devices:kato1999-01-038-880/+2028
| | | | | | | | | | | | | | | | | - on board 2nd CCU - Midori Elec. MDC-926Rs - Midori-Hayes ESP98 - NEC PC-9861K, PC-9801-101 PC-9801-120 - Melco IND-SP and IND-SS - PIO-9032A/B/C - B98-01 and B98-02 - IO-data device RSA-98II and RSA-98III - MC-16550 - MC-RS98 - Media Inteligent RSB-2000/3000 and RSB-384 - PCMCIA modem card Submitted by: Takahashi Yoshihiro <nyan@wyvern.cc.kogakuin.ac.jp>
* Clean up some more residual /usr/mdec references. I left all thejkh1999-01-032-4/+4
| | | | | extra rbootd/boot rom cruft pointing at /usr/mdec since it either doesn't exist or doesn't work anyway, so who cares? :)
* Minor bug: in the case where allocating a fresh mbuf for the receive ringwpaul1999-01-033-12/+9
| | | | | | fails, we need to set the descriptor status word so that the 'OWN' bit is set again so that the chip can reuse it. Previously, this wasn't being done.
* Update for new boot block location.jkh1999-01-021-5/+1
|
* Now empty DOS filesystems default to long file names. Non-empty filesystemsdt1999-01-022-10/+14
| | | | without traces of Win95 default to short file names, as before.
* Extraneous space.hoek1999-01-023-6/+6
|
* Ensure that deHighClust in direntry always initialized.dt1999-01-022-38/+58
| | | | | | | | | Noticed by: Carl Mascott <cmascott@world.std.com> Don't write access time of a file more than once per day. (Its precision is 1 day anyway). Don't try to write access and creation time in nonwin95 case. Suggested by: bde (long time ago).
* Ifdefed conditionally used simplock variables.bde1999-01-0212-14/+36
|
* Remove the last clients of vfs_object_create(..., waslocked=1);eivind1999-01-021-3/+7
| | | | | | waslocked will go away shortly. Reviewed by: dg
* unbreak devfs support after wrong cut&paste...luigi1999-01-011-17/+16
| | | | ReportedBy: Louis A. Mamakos
* Fixed bitrot in a comment. Fixed some style bugs.bde1999-01-011-5/+3
|
* Use M_VGA_VG320 if M_VESA_CG800x600 is not available. It looks ugly indes1999-01-012-46/+62
| | | | | | low-res, but it works... Submitted by: Ben Smithurst <ben@scientia.demon.co.uk>
* Correct typo in macro name.des1999-01-013-6/+6
|
* Don't use __BEGIN_DECLS/__END_DECLS in the kernel.bde1999-01-011-10/+8
| | | | Fixed some other, even more minor style bugs.
* Minor English and spelling fixes.bde1999-01-011-3/+3
|
* The previous commit was bogus. malloc(..., M_WAITOK) should not bebde1999-01-012-4/+12
| | | | | | | used in device attach routines. At least for attaches at boot time, actually waiting, or actually failing for malloc(..., M_NOWAIT), are almost equally unlikely and harmless, but using M_WAITOK interferes with automatic detection of bogus M_WAITOK's.
* Fixed bitrot in comments.bde1999-01-011-3/+5
|
* Made this compile if UMAPFS_DIAGNOSTIC is defined. This has been brokenbde1999-01-012-4/+4
| | | | | since before rev.1.1, so UMAPFS_DIAGNOSTIC should not be trusted. UMAPFS_DIAGNOSTIC is commented out in LINT to hide various bugs.
* Part 3 of the pcvt/voxware revival.peter1999-01-0112-0/+18029
| | | | Reviewed by: core
* Part 2 of pcvt/voxware revival. I hope I have not clobbered any otherpeter1999-01-0180-0/+37053
| | | | | | | | | deltas, but it is possible since I had a few merge conflicts over the last few days while this has been sitting ready to go. (Part 1 was committed to the config files, but cvs aborted grrr..) Approved by: core
* Part 1 of pcvt/voxware revival. I hope I have not clobbered any otherpeter1999-01-019-23/+462
| | | | | | | deltas, but it is possible since I had a few merge conflicts over the last few days while this has been sitting ready to go. Approved by: core
* Oops, forgot to commit entry in LINT for statically configured vinum.peter1999-01-013-3/+9
|
* The mount_mfs process that stays in a supervisor context handling MFSdillon1999-01-011-1/+11
| | | | | | I/O requests must be marked P_SYSTEM because if it isn't and the system decides to swap it or (god forbid) kill it, the system stands a good chance of locking up.
* This commit adds a software workaround for a hardware bug in certain PNICwpaul1998-12-312-13/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | chip revisions. (A buggy taiwanese chip? I'm just shocked; shocked I tell you.) So far I have only observed the anomalous behavior on board with PCI revision 33 chips. At the moment, this seems to include only the Netgear FA310-TX rev D1 boards with chips labeled NGMC169B. (Possibly this means it's an 82c169B part from Lite-On.) The bug only manifests itself in promiscuous mode, and usually only at 10Mbps half-duplex. (I have not observed the problem in full-duplex mode, and I don't think it ever happens at 100Mbps.) The bug appears to be in the receiver DMA engine. Normally, the chip is programmed with a linked list of receiver descriptors, each with a receive buffer capable of holding a complete full-sized ethernet frame. During periods of heavy traffic (i.e. ping -c 100 -f 8100 <otherhost>), the receiver will sometimes appear to upload its entire FIFO memory contents instead of just uploading the desired received frame. The uploaded data will span several receive buffers, in spite of the fact that the chip has been told to only use one descriptor per frame, and appears to consist of previously transmitted frames with the correct received frame appended to the end. Unfortunately, there is no way to determine exactly how much data is uploaded when this happens; the chip doesn't tell you anything except the size of the desired received frame, and the amount of bogus data varies. Sometimes, the desired frame is also split across multiple buffers. The workaround is ugly and nasty. The driver assembles all of the data from the bogus frames into a single buffer. The receive buffers are always zeroed out, and we program the chip to always include the receive CRC at the end of each frame. We therefore know that we can start from the end of the buffer and scan back until we encounter a non-zero data byte, and say conclusively that this is the end of the desired frame. We can then subtract the frame length from this address to determine the real start of the frame, and copy it into an mbuf and pass it on. This is kludgy and time consuming, but it's better than dropping frames. It's not too bad since the problem only happens at 10Mbps. The workaround is only enabled for chips with PCI revision == 33. The LinkSys LNE100TX and Matrox FastNIC 10/100 cards use a revision 32 chip and work fine in promiscuous mode. Netgear support has confirmed that they "have some previous knowledge of problems in promiscuous mode" but didn't have a workaround. The people at Lite-On who would be able to suggest a possible fix are on vacation. So, I decided to implement a workaround of my own until I hear from them. I suppose this problem made it through Netgear's QA department since Windows doesn't normally use promiscuous mode, and if Windows doesn't need the feature than it can't possibly be important, right? Grrr.
* Happy 1999!wosch1998-12-311-2/+2
|
* Add support for some FACILITY words:abial1998-12-311-1/+74
| | | | | | | | | | | | key? ( -- flag) \ check to see if there's a key to be read from input ms ( u -- ) \ wait that many milliseconds seconds ( -- u ) \ get number of seconds from midnight. 'words' now outputs the list page by page - this probably should go through libstand's pager, but will have to wait for closer integration of built-ins with Forth... Submitted partially by: W Gerald Hicks <wghicks@bellsouth.net>
OpenPOWER on IntegriCloud