summaryrefslogtreecommitdiffstats
path: root/sys/dev/ida/ida_eisa.c
Commit message (Collapse)AuthorAgeFilesLines
* style(9): single tab after #define.mdodd2004-01-131-9/+9
|
* Use __FBSDID().obrien2003-08-241-2/+3
| | | | Also some minor style cleanups.
* Mega busdma API commit.scottl2003-07-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Add two new arguments to bus_dma_tag_create(): lockfunc and lockfuncarg. Lockfunc allows a driver to provide a function for managing its locking semantics while using busdma. At the moment, this is used for the asynchronous busdma_swi and callback mechanism. Two lockfunc implementations are provided: busdma_lock_mutex() performs standard mutex operations on the mutex that is specified from lockfuncarg. dftl_lock() is a panic implementation and is defaulted to when NULL, NULL are passed to bus_dma_tag_create(). The only time that NULL, NULL should ever be used is when the driver ensures that bus_dmamap_load() will not be deferred. Drivers that do not provide their own locking can pass busdma_lock_mutex,&Giant args in order to preserve the former behaviour. sparc64 and powerpc do not provide real busdma_swi functions, so this is largely a noop on those platforms. The busdma_swi on is64 is not properly locked yet, so warnings will be emitted on this platform when busdma callback deferrals happen. If anyone gets panics or warnings from dflt_lock() being called, please let me know right away. Reviewed by: tmm, gibbs
* Use bioq_flush() to drain a bio queue with a specific error code.phk2003-04-011-1/+2
| | | | | | | | Retain the mistake of not updating the devstat API for now. Spell bioq_disksort() consistently with the remaining bioq_*(). #include <geom/geom_disk.h> where this is more appropriate.
* Centralize the devstat handling for all GEOM disk device driversphk2003-03-081-1/+0
| | | | | | | | in geom_disk.c. As a side effect this makes a lot of #include <sys/devicestat.h> lines not needed and some biofinish() calls can be reduced to biodone() again.
* NO_GEOM cleanup:phk2003-02-231-0/+1
| | | | | | Move ida driver to "struct disk *" centric api. Retire major number 109.
* Turn on interrupt-entropy harvesting for all/any mass storage devicesmarkm2001-03-011-1/+1
| | | | | | | I could find. I have no doubt missed a couple. Interrupt entropy harvesting is still conditional on the kern.random.sys.harvest_interrupt sysctl.
* Add crashdump support.jlemon2001-02-261-1/+7
| | | | Tested by: ps
* Add a flag value to the board identifiers, and use this to enable thejlemon2001-01-091-8/+13
| | | | | | firmware for selected revisions of the controller. Spotted by: Alexander Hausner <alex@hugo.bmg.gv.at>
* The DEC version of the Smart controller has its configuration informationjlemon2000-07-271-1/+2
| | | | | | | stored at a different location in the PCI space, so adjust accordingly. Also, when using more than two smart controllers in one machine, the disks were assigned the wrong drive number; fix this as well.
* Separate the struct bio related stuff out of <sys/buf.h> intophk2000-05-051-1/+1
| | | | | | | | | | | | | | | <sys/bio.h>. <sys/bio.h> is now a prerequisite for <sys/buf.h> but it shall not be made a nested include according to bdes teachings on the subject of nested includes. Diskdrivers and similar stuff below specfs::strategy() should no longer need to include <sys/buf.> unless they need caching of data. Still a few bogus uses of struct buf to track down. Repocopy by: peter
* - Define registers as offsets from register base rather than offsets frommdodd2000-04-161-1/+0
| | | | | | | EISA slot base. - Remove unused IOPORT resource. Reviewed by: jlemon
* - Add an additional call to eisa_add_iospace() so we get the right IOPORTmdodd2000-04-131-1/+2
| | | | | | | | | | in attach. - Change a EISA_CHANNEL_CLEAR to EISA_CHANNEL_BUSY in ida_v1_submit(). This may fix the problem with EISA IDA adapters though we have not heard back from testers yet. Reviewed by: jlemon
* Add support for older EISA compaq cards and newer Smart 4200 cards.jlemon2000-03-081-0/+330
Change disk names to `idad' to avoid naming conflicts with the controller, and enable the new disk code to pick up the drives. Tested by: david.w.james@bt.com (existing compaq support) Reviewed by: msmith Approved by: jordan
OpenPOWER on IntegriCloud