summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Convert all users of fldoff() to offsetof(). fldoff() is badphk2000-10-2749-119/+36
| | | | | | | | | | | | | | | | | | | | | | | because it only takes a struct tag which makes it impossible to use unions, typedefs etc. Define __offsetof() in <machine/ansi.h> Define offsetof() in terms of __offsetof() in <stddef.h> and <sys/types.h> Remove myriad of local offsetof() definitions. Remove includes of <stddef.h> in kernel code. NB: Kernelcode should *never* include from /usr/include ! Make <sys/queue.h> include <machine/ansi.h> to avoid polluting the API. Deprecate <struct.h> with a warning. The warning turns into an error on 01-12-2000 and the file gets removed entirely on 01-01-2001. Paritials reviews by: various. Significant brucifications by: bde
* Expand on the reasons for and against defining NO_F00F_HACK. This is one ofdougb2000-10-272-4/+4
| | | | | | those options that is frequently misunderstood, and ends up on -questions. PR: 21852
* Backout revision 1.7 which was a bad idea since it would force peopledfr2000-10-271-1/+1
| | | | | | | | | | to reinstall boot1 after a 'make world'. Unfortunately this means that people who have already installed a new boot1 from a 'make world' after 2000/09/18 *must* reinstall it after their next build using something like: # disklabel -B /dev/da0c
* Remove bogus undocumented macros used to control conditional assembly.phk2000-10-271-13/+0
|
* Remove #if DO_DEFLATEphk2000-10-272-6/+0
| | | | | | Remove #if DO_BSD_COMPRESS They are the wrong way to enable/disable features and undocumented to boot.
* Declare or #define per-cpu globals in <machine/globals.h> in all cases.bde2000-10-2717-77/+12
| | | | The i386 UP case was messily different.
* Fetch the protocol header (TCP, UDP, ICMP) only from the first fragmentru2000-10-271-16/+11
| | | | | | | | of IP datagram. This fixes the problem when firewall denied fragmented packets whose last fragment was less than minimum protocol header size. Found by: Harti Brandt <brandt@fokus.gmd.de> PR: kern/22309
* Merge from i386: Add MSP ioctlroger2000-10-271-0/+10
|
* As the blocking model has seems to be troublesome for many, disablemarkm2000-10-2711-1/+30
| | | | | | | it for now with an option. This option is already deprecated, and will be removed when the entropy-harvesting code is fast enough to warrant it.
* Add PCI device ID for an upcoming revision of the product.msmith2000-10-272-1/+3
|
* Add a missing newline to a diagnostic.msmith2000-10-271-1/+1
|
* Add and document the WITNESS_SKIPSPIN and WITNESS_DDB kernel options.jhb2000-10-273-0/+14
|
* - Use MUTEX_DECLARE() and MTX_COLD for the WITNESS code's internal mutex sojhb2000-10-273-168/+114
| | | | | | | | | | | | | | | | it can function before malloc(9) is up and running. - Add two new options WITNESS_DDB and WITNESS_SKIPSPIN. If WITNESS_SKIPSPIN is enabled, then spin mutexes are ignored by the WITNESS code. If WITNESS_DDB is turned on and DDB is compiled into the kernel, then the kernel will drop into DDB when either a lock hierarchy violation occurs or mutexes are held when going to sleep. - Add some new sysctls: debug.witness_ddb is a read-write sysctl that corresponds to WITNESS_DDB. The kernel option merely changes the default value to on at boot. debug.witness_skipspin is a read-only sysctl that one can use to determine if the kernel was compiled with WITNESS_SKIPSPIN. - Wipe out the BSD/OS-specific lock order lists. We get to build our own lists now as we add mutexes to the kernel.
* Yet another bug fix/optimization for the Davicom DM9100/9102: increasewpaul2000-10-272-0/+10
| | | | | | | | | the PCI latency timer value to 0x80. Davicom's Linux driver does this, and it drastically reduces the number of TX underruns in my tests. (Note: this is done only for the Davicom chips. I'm not sure it's a good idea to do it for all of them.) Again, still waiting on confirmation before merging to stable.
* Install the loader manpages.obrien2000-10-261-1/+0
|
* add reinit functions to mixerscg2000-10-2613-21/+100
| | | | | unstaticize chn_start() add reset/resetdone functions to channels
* do not attach to soundblaster 1.x - they are unsupportedcg2000-10-261-3/+7
|
* Change comment from sprintf to snprintfimp2000-10-261-1/+1
|
* Change snprintf to strncpy.imp2000-10-261-2/+9
| | | | | Also add a comment about a bogus assumption in the current code found at bsdcon by jhb.
* Add new ioctls for userland access to the MSP deviceroger2000-10-263-0/+30
|
* add a version tag for the alpha linulator to depend ongallatin2000-10-261-0/+2
|
* Fix typoroger2000-10-261-1/+1
|
* Minor build fixes.dfr2000-10-264-3/+4
|
* Update osf1_setuid() and osf1_setgid() to use the new change_euid() andgallatin2000-10-261-8/+13
| | | | | | | | | | change_ruid() in kern_prot.c. This fixes an incorrect use of chgproccnt(). Update both osf1_setuid() and osf1_setgid() to use setsugid() instead of just frobbing the flag. (mostly) submitted by: truckman
* unstaticize change_ruid() because it is needed by osf1_setuid()gallatin2000-10-262-3/+2
|
* RFC 791 says that IP_RF bit should always be zero, but nothingru2000-10-261-52/+29
| | | | | | | | in the code enforces this. So, do not check for and attempt a false reassembly if only IP_RF is set. Also, removed the dead code, since we no longer use dtom() on return from ip_reass().
* fix conflicts from rcsidsdarrenr2000-10-2628-356/+1198
|
* Wrong header length used for certain reassembled IP packets.ru2000-10-261-2/+2
| | | | | | This was first fixed in rev 1.82 but then broken in rev 1.125. PR: 6177
* Add infrastructure for Cologne Chip HFC-S PCI driver.hm2000-10-261-1/+4
|
* Add infrastructure for Cologne Chip HFC-S PCI driver.hm2000-10-262-10/+12
| | | | Increment isdn4bsd step.
* Make the software HDLC decoder work again.hm2000-10-261-3/+5
| | | | Submitted by: Hans Petter Selasky <hselasky@c2i.net>
* handle AFMT_QUERY rightcg2000-10-261-6/+15
|
* Close PR22152 and PR19511 -- correct the naming of a variableluigi2000-10-261-1/+1
|
* Set the DC_TX_INTR_ALWAYS and DC_TX_STORENFWD flags for the Davicomwpaul2000-10-252-4/+4
| | | | | | | | | | | | | | | | | | | DM9100/DM9102 chips. Do not set DC_TX_ONE. The DC_TX_USE_TX_INTR flag causes dc_encap() to set the 'interrupt on TX completion' bit only once every 64 packets. This is an attempt to reduce the number of interrupts generated by the chip. You're supposed to get a 'no more TX buffers left' interrupt once you hit the last packet whether you ask for one or not, however it seems the Davicom chip doesn't generate this interrupt, or at least it doesn't generate it under the same circumstances. The result is that if you transmit n packets, where n is less than 64, and then wait 5 seconds, you'll get a watchdog timeout whether you want one or not. The DC_TX_INTR_ALWAYS causes dc_encap() to request an interrupt for every frame. I'm still waiting on confirmation from a couple of users to see if this fixes their problems with the Davicom DM9102 before I merge this into -stable, but this fixed the problem for me in my own testing so I'm willing to make the change to -current right away.
* Add a missing SK_UNLOCK() to sk_attach_xmac().wpaul2000-10-252-0/+2
|
* Move the call to extend_heap() from main to start so that if our BSSdfr2000-10-252-3/+6
| | | | | | expands beyond the limit we will extend the address space before trying to zero the BSS. This should give us plenty of headroom for modest expansion of the loader.
* Don't build start.S as part of libalpha.a - its built specially.dfr2000-10-251-1/+1
|
* Don't indirect through a null pointer if we run out of kernel filenames.dfr2000-10-251-1/+1
|
* Make a few functions inline to save space.dfr2000-10-251-3/+3
|
* Bring cpuinfo closer to what it looks like in Linux 2.2.des2000-10-253-33/+141
| | | | Submitted by: R Bradford Jones <brad@kazrak.com>
* Add /proc/<pid>/status and /proc/<pid>/stat (the latter being mostlydes2000-10-259-15/+560
| | | | | | zeroes for the time being). Prompted by: Nathan Boeger <nathan@khmere.com>
* - Add atomic_cmpset_{acq_,rel_,}_longjhb2000-10-252-0/+104
| | | | - Add in atomic operations for 8-bit, 16-bit, and 32-bit integers
* This driver doesn't have a software interrupt handler, so don't attempt tojhb2000-10-251-8/+0
| | | | schedule a non-existant handler to run.
* Catch up to the new software interrupt code.jhb2000-10-252-6/+8
| | | | Noticed by: phk
* - Catch up to new software interrupt code.jhb2000-10-253-9/+9
| | | | | | - Add a missing curly brace. Noticed by: phk
* - Remove unneeded machine/ipl.h #include.jhb2000-10-251-6/+1
| | | | | | | | | | | | - Change the softintr() macro to do nothing on FreeBSD. Previously, this macro would set a bit in spending and schedule the softinterrupt thread to run. However, the bs driver never actually registers a a software interrupt handler, so all this work achieved nothing. From the code it is not clear what exactly the softintr() macro is actually supposed to be doing. It looks like it is supposed to be possibly running the hardware interrupt handler maybe? This handler is only present in the #ifdef __NetBSD__ code however. I have no idea how this driver handles interrupts at all, but at least it compiles now.
* Catch up to the new swi code.jhb2000-10-255-16/+4
| | | | Noticed by: phk
* We now keep the ip_id field in network byte order all theru2000-10-252-0/+8
| | | | | | | time, so there is no need to make the distinction between ip_output() and ip_input() cases. Reviewed by: silence on freebsd-net
* Fast interrupts have no associated process, therefore do not tryps2000-10-254-44/+52
| | | | and schedule it. This fixes booting machines with broken MP tables.
* The USB scanner driver. To be used together with SANE.n_hibma2000-10-259-0/+684
|
OpenPOWER on IntegriCloud