summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add nge. (I've used one for about a week in an XP1000.)alc2004-09-111-0/+1
|
* Add a threadcount field which we will need later for device removalphk2004-09-111-0/+1
| | | | | | | cleanup. Adding it now and MT5'ing will preserve binary compatibility if this code is later MFC'ed. MT5 candidate.
* Fix build if both of BKTR_USE_FREEBSD_SMBUS and BKTR_NEW_MSP34XX_DRIVER aredwhite2004-09-111-0/+4
| | | | | | | defined. Thanks to Damian Gerow <dgerow@afflictions.org> for pointing out this problem. RELENG_5 candidate.
* Add two spare fields to struct resource for some planned enhacenmentsimp2004-09-111-0/+2
| | | | | to make it possible to merge them w/o changing the size of struct resource which some drivers unfortunately still need to know.
* Double the number of kernel page tables for amd64 and for i386/PAE. The oldscottl2004-09-112-3/+5
| | | | | | | | value was only enough for 8GB of RAM, the new value can do 16GB. This still isn't optimal since it doesn't scale. Fixing this for amd64 looks to be fairly easy, but for i386 will be quite difficult. Reviewed by: peter
* Remove unneeded VGE_UNLOCK() in vge_detach().wpaul2004-09-111-1/+0
|
* Whitespace fixjulian2004-09-111-1/+0
| | | | MFC after: 2 days
* Try committing from the right tree this timejulian2004-09-111-3/+3
| | | | MFC after: 2 days
* o Print more info in the verbose mode;sobomax2004-09-101-31/+32
| | | | | | | | o use zlib(3) function which computes maximum length of the output buffer instead of rolling own version; o allow size of input file to be not multiple of cluster size by applying zero padding.
* Add vge(4) to the Hardware Notes.simon2004-09-103-0/+5
|
* Make up my mind if cpu pinning is stored in the thread structure or thejulian2004-09-105-20/+53
| | | | | | | | | scheduler specific extension to it. Put it in the extension as the implimentation details of how the pinning is done needn't be visible outside the scheduler. Submitted by: tegge (of course!) (with changes) MFC after: 3 days
* Clarify/extend in several places and make sure that everything matches reality.sobomax2004-09-101-16/+32
|
* Bump WARNS level to 6.trhodes2004-09-101-0/+1
| | | | | Submitted by: keramida Tested on: i386, sparc64 (panther)
* Add some code to allow threads to nominat a sibling to run if theyu are ↵julian2004-09-105-9/+55
| | | | | | going to sleep. MFC after: 1 week
* Add a manual page for the vge(4) driver.wpaul2004-09-102-0/+188
|
* Add device driver support for the VIA Networking Technologieswpaul2004-09-1015-1/+4130
| | | | | | | | | | | | VT6122 gigabit ethernet chip and integrated 10/100/1000 copper PHY. The vge driver has been added to GENERIC for i386, pc98 and amd64, but not to sparc or ia64 since I don't have the ability to test it there. The vge(4) driver supports VLANs, checksum offload and jumbo frames. Also added the lge(4) and nge(4) drivers to GENERIC for i386 and pc98 since I was in the neighborhood. There's no reason to leave them out anymore.
* Add two spare elements for planned but not yet implemented stuff relatedphk2004-09-101-0/+5
| | | | | | | | to device driver unloading. Adding these two now and MT5'ing them will allow us to preserve binary compatibility on RELENG_5 when these facilities are MFC'ed. MT5 Candiate.
* Add mkuzip(8), non-GPL utility to compress filesystem images for use withsobomax2004-09-104-0/+356
| | | | | | | | | | | | | | geom_uzip module. This is based on utility I wrote some 3 years ago for a hack for md(4), which functionally was close to what geom_uzip does today. Since I don't have a time to test that it compiles/works on other arches, stick it to i386 only. Will do it later. Unlike original cloop util, this one embedds FreeBSD-compatible shell code into the generated image, not Linux one. Unfortunately severe space restriction imposed by the CLOOP format doesn't allow to put conditional code which will work both on Linux and FreeBSD. In fact it was quite a challenge to fit necessary FreeBSD code into 127 bytes. ;-)
* Fix oversight reported by Norikatsu Shigemura for the "sym" driverse2004-09-101-0/+1
| | | | | | | | (which was derived from the "ncr" driver) and add a MODULE_DEPEND on "cam". MT5 candidate, IMHO. MFC after: 1 week
* Add netrate (netreceive, netsend), a tool for generating (and sinking)rwatson2004-09-106-0/+398
| | | | | UDP packets of specified size at a fixed rate. I've been using this for netperf-related testing.
* Make it depend on PCI as well.mjacob2004-09-101-0/+1
| | | | Submitted by: Stefan eSSer
* Make sym depend, as a module, on cam.mjacob2004-09-101-0/+1
| | | | Submitted by:"Norikatsu Shigemura" <nork@FreeBSD.org>
* Remove the debugging tunable, it was not being used.trhodes2004-09-102-14/+3
| | | | | | Enable first match by default.[1] We should: rwatson [1]
* I found "portsdb -u" dumps core with recent INDEX file, and this iskuriyama2004-09-101-0/+2
| | | | | | | | | | | | | | | caused by refering broken (uninitialized?) pointer which is retrieved from __bt_new() (and from mpool_new()). I don't know why this linp[0] is read before stored because this should be controlled by .lower and .upper member of PAGE structure which are correctly initialized. But this workaround fixes the problem on my environment and this module has #ifdef PURIFY option which initializes new and reused memory from mpool by memset(p, 0xff, size) like as I did. Please feel free to fix the real bug instead of my workaround.
* Sync with recent English versionsden2004-09-1013-327/+700
| | | | MFC after: 2 days
* o Initialize a local variable and make gcc happy.maxim2004-09-101-0/+2
| | | | | PR: bin/71485 Submitted by: Jukka A. Ukkonen
* Fix a type bug which sometimes wrote unusable lock sectors on the disk.phk2004-09-101-2/+2
|
* Reduce the amount of memory reported to busdma.sos2004-09-102-8/+10
| | | | | This made the requirements for bouncebuffers too big with PAE. Cleanup the way size defines for transfers are implemented.
* Convert sndstat_lock from a mutex to an sx lock. sndstat_read()truckman2004-09-101-26/+29
| | | | | | | | | | | | | | | holds sndstat_lock across a call to uiomove(), which is not legal to do with a mutex because of the possibility that the data transfer could sleep because of a page fault. It is not possible to just unlock the mutex for the uiomove() call without introducing another locking mechanism to prevent the body of sndstat_read() from being re-entered. Converting sndstat_lock to an sx lock is the least complicated change. This is a candidate for RELENG_5. LOR: 030 MFC after: 4 days
* Remove spare ")"brueffer2004-09-101-1/+1
| | | | MFC after: 3 days
* Better fix the busdma problem exposed by ATA. With the CMD 646 formarcel2004-09-101-1/+5
| | | | | | | | | | example the maximum segment size is 64K while the boundary is set to 8K due to controller limitations. It is impossible to NOT cross the boundary for any segment size that's larger than the boundary. So, once we inherited the boundary from the parent tag, make sure to reduce the maximum segment size to the boundary if it was larger. MT5 candidate.
* Fix a problem mentioned in the previous revision in a different,ru2004-09-101-3/+3
| | | | | non-intrusive way. This should also fix the PowerPC build that broke due to this change.
* Fix format strings to unbreak with -DDEBUG option.kuriyama2004-09-104-19/+20
|
* The previous commit, roughly one and a half years ago removed themarcel2004-09-101-62/+14
| | | | | | | | | | | | | | | | | | | | | | branch prediction optimization for LINT, because the kernel was too large. This commit now removes it altogether since it causes build failures for GENERIC kernels and the various applicable trends are such that one can expect that it these failure will cause more problems than they're worth in the future. These trends include: 1. Alpha was demoted from tier 1 to tier 2 due to lack of active support. The number of people willing to fix build breakages is not likely to increase and those developers that do have the gumption to test MI changes on alpha are not likely to spend time fixing unexpected build failures first. 2. The kernel will only increase in size. Even though stripped-down kernels do link without problems now, compiler optimizations (like inlining) and new (non-optional) functionality will likely cause stripped-down kernels to break in the future as well. So, with my asbestos suit on, get rid of potential problems before they happen. MT5 candidate.
* remove giant required from kqueue_close..jmg2004-09-101-2/+0
| | | | | Reported by: kuriyama MFC after: 3 days
* - grammar fixesbrueffer2004-09-101-3/+3
| | | | | | - fix path to a source file MFC after: 3 days
* Connect cnw.4 to the build.brueffer2004-09-101-0/+1
| | | | MFC after: 5 days
* Add a manpage for the cnw(4) driver, adopted from NetBSD.brueffer2004-09-091-0/+130
| | | | MFC after: 5 days
* - add a HARDWARE section based on the driver READMEbrueffer2004-09-091-5/+47
| | | | | | | - capitalization fixes - bump document date MFC after: 3 days
* Add the .h files to the .o dependency lists so the .h's are created beforeobrien2004-09-091-2/+2
| | | | trying to build the .o's.
* Add comments about why we're freeing subdevs (which is completelyimp2004-09-091-8/+11
| | | | | | | | | | redundant at this point and should be retired). Don't free subdevs if we don't attach any devices. This was leaving stale device_t's around. Don't touch the device if it isn't attached since the name isn't meaningful then. Switch from strncpy (properly used) to strlcpy. From a patch submitted by Peter Pentchev
* We don't need a uhub_child_detached() routine now that we don't detachimp2004-09-091-34/+2
| | | | | | | | | | | | | | device_t instances when no driver attaches. They are left around, and we need to remember them. # The usbd_device_handle->subdevs[] array likely is completely bogus # at this point, but one change at a time, since its removal will need # to have similar code replace it extracted from newbus. Part of the patch submitted by Peter Pentchev after an excellent analysis of the underlying problems. MFC After: 1 week
* Teach the stack trace code how to step across a double fault when steppingjhb2004-09-091-0/+20
| | | | | | | | | across frames. Basically, if the current frame is for the 'dblfault_handler' function, then get the next %eip and %ebp values to use from the original TSS of the thread that has the saved state when the double fault triggered. MFC after: 4 days
* Shame on me. I screwed up product ID for the 3COM Bluetooth PC-Card.emax2004-09-091-1/+1
| | | | | | It's 0x0040 not 0x0400. MFC after: 3 days
* For the moment, back out my back out of green's 1.87 commit. While itimp2004-09-091-11/+9
| | | | | | | | produced better results for a test program I had here, it didn't substantially change the number of crashes that I saw. Both the old code and the new code seemed to produce the same crashes from the usb layer. Since the new code also solves a close() crash, go with it until the underlying issues wrt devices going away can be addressed.
* Use the recently introduced RES_DFLRETRY parameter instead of a well-hiddenyar2004-09-091-1/+1
| | | | constant for the default number of retries.
* Add the macro RES_DFLRETRY long-promised by resolver(5).yar2004-09-091-0/+1
| | | | | | | | | | It specifies the default number of retries per a name server. This makes the code consistent with the manpage and allows to kill another constant in res_init.c that should have been a #define'd parameter. (This appears to be a case when the manpage was better than the code, so the latter was to be fixed.) PR: bin/62139 (in the audit trail)
* Improve the description of "timeout" and "attempts" resolveryar2004-09-091-5/+14
| | | | | | options to avoid user confusion from now on. PR: bin/62139 (inspired by)
* sparc64 is not ready for PREEMPTION, so turn it off for now.scottl2004-09-091-1/+1
|
* Restore NetBSD SCM ID.obrien2004-09-091-1/+1
| | | | Submitted by: delphij@beastie.frontfree.net
OpenPOWER on IntegriCloud