summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Update the atkbdc, atkbd, and psm drivers to probe/attachyokota2001-09-0610-335/+728
| | | | | | | | more cleanly and consistently in all APCI, PnP BIOS, and "hint" cases. NOTE: this doesn't necessarily solve the problem that the PS/2 mouse is not detected after the recent ACPI update.
* Fix verbose probe message.sos2001-09-061-6/+8
| | | | PR: 29360
* Don't use a silly test to define INTR_ENTROPY.scottl2001-09-061-1/+1
| | | | Submitted by: peter
* Add support for set/getting the region code on DVD drives.sos2001-09-061-0/+3
| | | | PR: 28604
* Wrap array accesses in macros, which also happen to be lvalues:jlemon2001-09-0624-80/+99
| | | | | | | ifnet_addrs[i - 1] -> ifaddr_byindex(i) ifindex2ifnet[i] -> ifnet_byindex(i) This is intended to ease the conversion to SMPng.
* Cosmetic cleanups and rearrangement for code to come. There should bejlemon2001-09-061-63/+68
| | | | no functional change in this commit.
* Sigh. Dig up text from a signature in a 1994 Usenet post I made and redopeter2001-09-051-5/+12
| | | | the ..uhh... ``console test'' to avoid another 50 emails about GPL issues.
* Attach if_vlan to the build process.brooks2001-09-051-0/+1
|
* vlan.h is obsolete, don't create it anymore.brooks2001-09-055-21/+5
|
* Deconditionalize vlan support.brooks2001-09-051-14/+3
|
* Update tx(4) to always enable vlan(4) support.brooks2001-09-053-17/+1
| | | | Approved by: semenu
* Patric Gualat tells me that I can't do basic bit math. He's right.imp2001-09-051-4/+4
| | | | | | | | When either bit 3 or 4 is set, we need to *SET* bit 5, not clear it in the card control register. This makes TI PCI-1030, 1130 and 1131 not work anymore without this fix. MFC: soon
* Don't specify the number of vlan interfaces any more, they are createdbrooks2001-09-052-2/+2
| | | | at runtime.
* Make vlan(4) loadable, unloadable, and clonable. As a side effect,brooks2001-09-059-163/+205
| | | | | | | interfaces must now always enable VLAN support. Reviewed by: jlemon MFC after: 3 weeks
* Bring the aac driver *much* closer to style(9).scottl2001-09-0510-3246/+3428
| | | | Reviewed by: ken
* Include <sys/_lock.h> for the definition of struct lock_object. Don'tjhb2001-09-051-0/+1
| | | | | | understand why this wasn't added when _mutex.h was added. Noticed by: jlemon
* Remove superfluous statement.jlemon2001-09-052-2/+0
|
* add a method for recording of specific channels for devices with more thancg2001-09-056-15/+64
| | | | | one hardware record channel. new devices, /dev/dsprX.Y where X is unit number and Y is channel index.
* style(9) the structure definitions.obrien2001-09-052-2/+2
|
* don't try to dump nonexistent data when recordingcg2001-09-051-1/+1
|
* Merge linker set relocations with the rest.dfr2001-09-052-0/+2
|
* It is the last-second trivial changes that kill me every time.peter2001-09-051-1/+1
| | | | | | Fix nested comment. :-( Submitted by: obrien
* style(9) the structure definitions.obrien2001-09-059-20/+20
|
* Rework the ISA PnP driver pnp and the PnP resource parser to fixyokota2001-09-058-360/+701
| | | | | | | | | | | | | | | | | | | | | | | | the following bugs. - When constructing a resource configuration, respect the order in which resource descriptors are read, in order to establish the correct mapping between the descriptors and configuration registers. "Plug and Play ISA Specification, Version 1.0a", Sec 4.6.1, May 5, 1994. "Clarifications to the Plug and Play ISA Specification, Version 1.0a", Sec 6.2.1, Dec. 10, 1994. - Do not ignore null (empty) descriptors; they are valid descriptors acting as filler. "Clarifications to the Plug and Play ISA Specification, Version 1.0a", Sec 6.2.1. - Correctly set up logical device configuration registers for null resources. "Clarifications to the Plug and Play ISA Specification, Version 1.0a" - Handle null resources properly in the resource allocator for the ISA bus.
* Attempt to refine the __IDSTRING() macros so that they dont collide withpeter2001-09-051-4/+12
| | | | | | | | | | | each other. This will allow multiple __RCSID() entries in the same file and even __RCSID() in headers. **HOWEVER**, the usefulness of this in headers is somewhat marginal in non-ELF since they would go into the data section where they cannot be easily compressed or stripped. It (id's in headers) is also not useful in the non-GCC case since it is hard to generate unique variable names. I have an idea on that though. Now for mcs: http://mirrors.ccs.neu.edu/cgi-bin/unixhelp/man-cgi?mcs+1
* style(9) the structure definitions.obrien2001-09-0514-22/+22
|
* Fix the definition generation code from rev 1.15 that generates non-style(9)obrien2001-09-051-4/+4
| | | | compliant structure definitions.
* style(9) the structure definitions.obrien2001-09-0525-58/+52
|
* Style(9)obrien2001-09-051-47/+47
|
* Add cloning support for the tap(4) device similar to that in the tun(4)brooks2001-09-052-136/+221
| | | | | | device. Submitted by: Maksim Yevmenkin <myevmenk@digisle.net>
* Regenerate.wpaul2001-09-041-1/+5
|
* Add support for the BCM5401 and BCM5411 10/100/1000Mbps copper gigE PHYs.wpaul2001-09-043-26/+79
| | | | | This basically updates the brgphy driver to support 10/100 modes in addition to 1000Mbps modes.
* I don't know what I was thinking- if I have two separate busses on onmjacob2001-09-041-174/+136
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SIM (as is true for the 1280 and the 12160), then I have to have separate flags && status for *both* busses. *Whap*. Implement condition variables for coordination with some target mode events. It's nice to use these and not panic in obscure little places in the kernel like 'propagate_priority' just because we went to sleep holding a mutex, or some other absurd thing. Remove some bogus ISP_UNLOCK calls. *Whap*. No longer require that somebody do a lun enable on the wildcard device to enable target mode. They are, in fact, orthogonal. A wildcard open is a statement that somebody upstream is willing to accept commands which are otherwise unrouteable. Now, for QLogic regular SCSI target mode, this won't matter for a damn because we'll never see ATIOs for luns we haven't enabled (are listening for, if you will). But for SCCLUN fibre channel SCSI, we get all kinds of ATIOs. We can either reflect them back here with minimal info (which is isp_target.c:isp_endcmd() is for), or the wildcard device (nominally targbh) can handle them. Do further checking against firmware attributes to see whether we can, in fact, support target mode in Fibre Channel. For now, require SCCLUN f/w to supoprt FC target mode. This is an awful lot of change, but target mode *still* isn't quite right. MFC after: 4 weeks
* Note for ATIOs returned because of BDRs or Bus Resets for which bus thismjacob2001-09-041-20/+34
| | | | | | | | | | applies to. Do more bus # foo things. Acknowledge Immediate Notifies right away prior to throwing events upstream (where they're currently being ignored, *groan*) Capture ASYNC_LIP_F8 as with ASYNC_LIP_OCCURRED. Don't percolate them upstream as if they were BUS RESETS- they're not.
* If we're on an interrupt stack, mark things so that we don't trymjacob2001-09-041-10/+11
| | | | | | | | | | and cv_wait for mailbox commands to complete if we start them from here. Fix residuals for target mode such that we only check the residual and set it in the CTIO if this is the last CTIO (when we're sending status). MFC after: 4 weeks
* I don't know what I was thinking- if I have two separate busses on onmjacob2001-09-041-4/+6
| | | | | | | | | | | | SIM (as is true for the 1280 and the 12160), then I have to have separate flags && status for *both* busses. *Whap*. Implement condition variables for coordination with some target mode events. It's nice to use these and not panic in obscure little places in the kernel like 'propagate_priority' just because we went to sleep holding a mutex, or some other absurd thing. MFC after: 4 weeks
* Don't report power interrupts.imp2001-09-041-2/+0
|
* MFS: put debug writes behind boot verbose.imp2001-09-041-7/+16
|
* Fix SET_IID_VAL/SET_BUS_VAL macros to usable.mjacob2001-09-041-2/+2
| | | | MFC after: 4 weeks
* Fix a memory leak in __getcwd() that can occur after a filesystemiedowse2001-09-041-1/+3
| | | | | | | | | | has been forcibly unmounted. If the filesystem root vnode is reached and it has no associated mountpoint (vp->v_mount == NULL), __getcwd would return without freeing 'buf'. Add the missing free() call. PR: kern/30306 Submitted by: Mike Potanin <potanin@mccme.ru> MFC after: 1 week
* Make the csc and function interrupts ISA on shutdown. This shouldimp2001-09-041-1/+13
| | | | | | | help with the hanging problem on reboot. Note: we need to do the other things as well. Also, turn off the bits in the stat change interrupt mask and the cardbus interrupt mask as well in an attempt to shut off all interrupt sources.
* Add support for Conexant LANfinity miniPCI controllers. People who havewpaul2001-09-044-6/+98
| | | | | | | | | | laptops with this chip should test this and report back as I don't have access to this hardware myself. People with -stable systems should try the patch at: http://www.freebsd.org/~wpaul/conexant.patch.gz Submitted by: Phil Kernick <Phil@Kernick.org>
* Reenable RTC interrupts after wakeup. Some laptops have a problemiwasaki2001-09-048-8/+113
| | | | | | | | | with system statistics monitoring tools (such as systat, vmstat...) because of stopping RTC interrupts generation. Restore all the timers (RTC and i8254) atomically. Reviewed by: bde MFC after: 1 week
* Remove long overdue obsolete file ide_pcireg.hsos2001-09-041-63/+0
|
* There is no option IDE_DELAY and havn't been for a long time..sos2001-09-041-1/+0
|
* Add `-I.' option to CFLAGS so that we can compile asm code togetheriwasaki2001-09-041-0/+1
| | | | with `-nostdinc' option.
* Just print a message in acpi_tz_monitor() only when new active stateiwasaki2001-09-041-2/+5
| | | | | | | | is different from the previous active state. This reduce tons of 'acpi_tz0: _AC0: temperature 64.0 >= setpoint 64.0' messages. Reviewed by: msmith
* Fix sysctl comment field, s/the the/then thealfred2001-09-041-1/+1
| | | | Pointed out by: ru
* Enable bootforth.dfr2001-09-042-2/+2
|
* Avoid an alignment fault on 64bit architectures.dfr2001-09-041-1/+1
| | | | Reviewed by: dcs
OpenPOWER on IntegriCloud