summaryrefslogtreecommitdiffstats
path: root/sys/dev
Commit message (Collapse)AuthorAgeFilesLines
* Add support nForce3 250 audiosanpei2004-09-201-0/+4
| | | | | | PR: kern/71726 Submitted by: FUJIMOTO Kou <fujimoto@j.dendai.ac.jp> MFC after: 1 week
* Record a problem we can't workaround for now regarding duplicate interruptsnjl2004-09-201-0/+7
| | | | | because of links left enabled while in APIC mode. A large scale rework of irq links is underway by jhb@ which should fix this eventually.
* add '/* Panasonic products */' line(I removed it)sanpei2004-09-201-0/+1
|
* Fix compilation of vinum(4) when VINUMDEBUG is not defined.marius2004-09-202-2/+2
| | | | | | PR: 71341 Submitted by: Phil Budne <phil@tripadvisor.com> MT5 candidate.
* Correct value and description of the unused MK48TXX_WDAY_FT macro.marius2004-09-201-1/+1
|
* Commit the new version of the adlink driver which can do non-cyclicphk2004-09-191-305/+250
| | | | capture. Now we just need somebody to write a gnu-radio frontend :-)
* - Some of the upper bits of the time related (seconds, minutes, etc.)marius2004-09-192-19/+131
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | registers are control bits or depending on the model contain additional time bits with a different meaning than the lower ones. In order to only read the desired time bits and not change the upper bits on write use appropriate masks in the gettime and settime function respectively. Due to the polarity of the stop oscillator bit and the fact that the century bits aren't used on sparc64 not masking them didn't cause problems so far. - Fix two off-by-one errors in the handling of the day of week. The genclock code represents the dow as 0 - 6 with 0 being Sunday but the mk48txx use 1 - 7 with 1 being Sunday. In the settime function when writing the dow to the clock the range wasn't adjusted accordingly but the clock apparently played along nicely otherwise the second bug in the gettime function which mapped 1 - 7 to 0 - 6 but with 0 meaning Saturday would have been triggered. Fixing these makes the date being stored in the same format Sun/Solaris uses and cures the "Invalid time in real time clock. Check and reset the date immediately!" when the date was set under Solaris prior to booting FreeBSD/sparc64. [1] Looking at other clock drivers/code e.g. FreeBSD/alpha the former "bug", i.e. storing the dow as 0 - 6 even when the clock uses 1 - 7, seems to be common but might be on purpose for compatibility when multi-booting with other OS which do the same. So it might make sense to add a flag to handle the dow off-by-one for use of this driver on platforms other than sparc64. - Check the state of the battery on mk48txx that support this in the attach function. - Add a note that use of the century bit should be implemented but isn't required at the moment because it isn't used on sparc64. Problem noted by: joerg [1] MT5 candidate.
* spell RX correctlyjmg2004-09-191-16/+10
| | | | | | | don't call re_rxeof a second time when we've already done the work pull common code out from if and else clauses MFC after: 3 days
* Add Sitecom's LN-029 USB 2.0 Ethernet adapter.iedowse2004-09-182-0/+5
|
* Add support for the fxp(4) based card in ICH6 (i915) chipsets.mux2004-09-181-0/+1
| | | | | | This is a RELENG_5 candidate. Submitted by: Mike Tancsa <mike@sentex.net>
* pass in pointer to m_head to re_encap because m_defrag could free thejmg2004-09-181-13/+13
| | | | | | | original mbuf causing a free'd mbuf passed to bpf later and panic'ing the system.. This should only effect jumbo frames. MFC after: 5 days
* Use tty->t_sc to find out softc.phk2004-09-182-12/+11
|
* Actually this order (unlock, wakeup) in this case is race-safe and canpjd2004-09-181-1/+1
| | | | | | save us 2 context switches. Explained by: njl
* Fix an issue with ng_tty which (ab)used the tty->t_sc field which isphk2004-09-171-4/+6
| | | | | | reserved for the device drivers: Add a t_lsc field for line discipline private use.
* Fix compilation again.phk2004-09-171-3/+0
|
* The long dead hand of the past has pushed forward useless bits in thisimp2004-09-174-28/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | driver. Trim its fingernails by removing some useless bits before fixing the 'thread not terminated on detach' problem. o dmacnt is no longer used now that we allocate at attach time. Remove it from struct fdc_data. o ISPNP was only ever set, but never tested. It used to be used for the allocation routines to change how it allocated resources. Since that's no longer necessary, retire the flag. o ISPCMICA was only ever tested, but never set. GC it. This removes a special case in determining the drive type. The drive type is now set in fdc_pcmcia.c, so the hack isn't needed anymore. Sadly, this isn't tested with a Y-E Data pcmcia floppy drive because there are a number of other issues that preclude it from working. o Fix ifdef for reading from the rtc. I'm of the opinion that this ifdef should be moved into fdc_isa.c, but not today as ideally there'd be other fixes to the probing of children. So now we just read it on i386 ! pc98 (there's no #define for MACHINE_ARCH, just MACHINE, hence this slightly inelegant kludge) and amd64. The PC98 exclusion likely isn't meaningful since pc98 uses a different driver, but will be when merging of the pc98 floppy code into this driver is complete (this is the other reason I think this block of code belongs outside fdc.c). All of these changes are safe to MT5.
* Overhaul ucom serial driver by using generic stuff instead of homerolledphk2004-09-175-440/+154
| | | | all over the place.
* Use ttyalloc() instead of ttymalloc(NULL)phk2004-09-177-7/+7
|
* Commit patch to supress spurious link change events. Apparently, withwpaul2004-09-171-2/+11
| | | | | | | | | | | | | | | | | | | | | | | copper NICs, a link change event is posted whenever MII autopolling is toggled off and on, which happens whenever someone calls bge_miibus_readreg() or bge_miibus_writereg() to access the PHY registers. This means anytime someone called the SIOCGIFMEDIA ioctl on a bge interface, the link would reset. Even a simple "ifconfig bge0" would do it, though other apps like dhclient or the PPPoE daemon could trigger it as well. An obvious symptom of this problem is lots of "bgeX: gigabit link up" messages appearing on the console for no apparent reason. Through experimentation, I determined that when a real link change event occurs, the BGE_MIMODE_AUTOPOLL in the BGE_MI_MODE register is always set, so now if we have a copper NIC and an link change event occurs and the BGE_MIMODE_AUTOPOLL bit is clear, we ignore the event. Note that this does not apply to the original BCM5700 chip since we use a different method for sensing link changes with that chip (the status block method was broken), nor to fiber optic NICs since they don't use the GMII PHY access registers.
* Handle _FDE results of 5 bytes (vs. 5 uint32_t's). BIOS vendors find yetnjl2004-09-171-37/+54
| | | | | | | | | | another way to misinterpret the spec. Also, always fall back to the hints probe on any attach failure, not just when _FDE fails. Thanks to imp and scottl for finding this. Tested by: rwatson (minimally) MFC after: 5 days
* - Make md(4) 64-bit clean.pjd2004-09-161-161/+89
| | | | | | | | | After this change it should be possible to use very big md(4) devices. - Clean up and simplify the code a bit. - Use humanize_number(3) to print size of md(4) devices. - Add 't' suffix which stands for terabyte. - Make '-S' to really work with all types of devices. - Other minor changes.
* There is no need to keep 'npage' value inside our softc structure,pjd2004-09-161-8/+8
| | | | | | | it is only used in one function. While doing so, change its type to vm_ooffset_t. We are still limited for swap-backed devices to 16TB on 32-bit architectures where PAGE_SIZE is 4096 bytes.
* Allocate tty at attach time rather than open time.phk2004-09-161-49/+43
| | | | | | | | Use the init/lock*in/out fields in struct tty and remove them from our softc. Use tty->t_sc to find out softc when convenient. Mostly OK'ed by: bde
* - Do not use bio_pblkno as it is going away anyway.pjd2004-09-161-13/+14
| | | | - Prefer bio_length than bio_bcount.
* First wakeup, then unlock.pjd2004-09-161-2/+1
|
* Type 'int' is too small for 'i' and 'lastp' variables. Use proper type,pjd2004-09-161-2/+2
| | | | which is vm_pindex_t (unsigned 64bit on i386).
* Don't print a warning message if the _CRS value is empty. This is alreadynjl2004-09-161-7/+5
| | | | | | covered by other printfs under ACPI_DEBUG and is not a failure case. MFC after: 3 days
* Ignore leading '_' in model name returned by devices.sos2004-09-161-1/+1
| | | | | | | This make "_NEC" devices appear as "NEC" which is more corrent. The reason is tha NEC originally screwed up on the byteorder in the model string, so now that they have realized that they prefixed the '_' so that not every ATA driver on the planet would call them "EN C" :)
* default: case shouldn't set an error yet either.imp2004-09-161-1/+0
|
* Reserve the DMA memory at attach time, rather than at use. Whileimp2004-09-161-15/+12
| | | | | | | | | reserving it at use time is more miserly, low memory (< 16MB) evaporates quickly on many systems, so there may not be any suitable buffers available. This specifically doesn't use the newer, fancier isa_dma_init to ease merging to 5. Reviewed by: tegge, phk
* If the timeout handler runs and notices that commands are timed out, checkscottl2004-09-162-0/+11
| | | | | | | | the firmware status register on the card to see if the firmware is still running. There is no way to recover from this, but at least it can give a hint as whether the car has crashed (which happens all too often). MFC after: 3 days
* For the moment, treat failures to attach floppy drives as non-fatalimp2004-09-161-2/+0
| | | | | | | errors for the attachment process for the floppy controller. This is a band-aide because it doesn't try any of the fallback methods when _FDE isn't long enough, but should be sufficient for people experiencing the dreaded mutex not initialized panic.
* Backout the code which tries to use undocumented way to determine ifsobomax2004-09-151-43/+5
| | | | | | | | fm801 has sound capabilities or not. Unfortunately this code doesn't work as expected. Submitted by: many MFC after: 3 days
* Flush the queue of minor fixes to pst.sos2004-09-153-5/+3
|
* #include <isa/isavar.h> instead of <i386/isa/isa_dma.h>phk2004-09-152-2/+2
|
* Fix a typo that affects !i386.alc2004-09-152-2/+2
|
* Add missing NGE_LOCK_DESTROY() to nge_detach().wpaul2004-09-141-0/+2
|
* Make two major changes to this code to address some stability/corruptionwpaul2004-09-142-300/+239
| | | | | | | | | | | | | | | | | | | problems: 1) Add locking for SMP, code provided by Alan Cox 2) While testing Alan's patches, I observed serious problems with the jumbo buffer allocation code (machine crashed twice), so I gutted it and rewrote the receive handler to use multiple chained descriptors. Each RX descriptor gets a single 2K cluster, and the chip will fill in as many as it needs to hold the complete packet. User reports that this corrects the data corruption issues previously observed and discussed on -current. Note that this driver still needs to be hit with the busdma stick. I intend to inflict said beating in the near future. MFC after: 1 week
* Deallocate VM object on failure.pjd2004-09-141-0/+2
|
* One more missing NDFREE(9).pjd2004-09-141-0/+1
|
* - Don't forget about NDFREE() in case of vn_open() failure.pjd2004-09-141-2/+4
| | | | - Don't forget about vn_close() in case of failure.
* Fix UMA zone leak.pjd2004-09-141-0/+1
|
* Use bus_setup_intr in preference to BUS_SETUP_INTR.imp2004-09-141-1/+1
|
* Set up the data flow flag correctly so that bounced buffers have a chance ofscottl2004-09-141-1/+1
| | | | working in amr_enquire().
* Checkpoint the fdc resource changes:imp2004-09-144-121/+121
| | | | | | | | | | | | o Allow for up to 3 resource I/O ranges to be given for the floppy controller, rather than just two that are allowed for now. o Make sure that we can work with either a base address of 0x3f0 or 0x3f2. o Create new inline functions to access the YE DATA's unique BDCR register. o Update pccard attachment to add the fd device. o Do some minor style(9) polishing. # I'm guessing that the fdc pccard attachment broke some time ago, since # there are a number of issues with it still.
* Pull the correct clock frequency value out of OFW. Why the helper functionscottl2004-09-131-2/+6
| | | | | | doesn't do this is beyond me, but that will be investigated later. This results in programming the chip with the correct frequency, which in turn allows devices to negotiate up to the full 20MB/s.
* Change sb_lock() calls to sbc_lockassert() and remove the sb_unlock()truckman2004-09-121-4/+2
| | | | | | | | | | | calls in sb_cmd2() and sb_getmixer(). The lock has already be grabbed before these functions are called. This is a RELENG_5 candidate. PR: 71189 Submitted by: stephane MFC after: 3 days
* Put some of the probe messages under bootverbose so to lessen the noise.scottl2004-09-121-15/+16
|
* Remove unneeded TX channel wakeup from vge_txeof(). This was putwpaul2004-09-111-1/+0
| | | | | there for testing and forgotten. It's not really needed, and taking it out saves a register access.
* 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.
OpenPOWER on IntegriCloud