summaryrefslogtreecommitdiffstats
path: root/sys/dev/isp/isp_sbus.c
Commit message (Collapse)AuthorAgeFilesLines
* Move the inclusion of <machine/ofw_machdep.h> after the inclusion ofmarcel2003-09-021-1/+1
| | | | | | | <dev/ofw/openfirm.h> to allow the former to contain prototypes that use types defined in the latter. Reviewed by: mjacob@
* Use __FBSDID().obrien2003-08-241-2/+3
| | | | Also some minor style cleanups.
* s=include <ofw/=include <dev/ofw/= to reflect removal of -I$S/devimp2003-08-231-1/+1
|
* Mega busdma API commit.scottl2003-07-011-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | 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
* Back out M_* changes, per decision of the TRB.imp2003-02-191-2/+2
| | | | Approved by: trb
* Remove M_TRYWAIT/M_WAITOK/M_WAIT. Callers should use 0.alfred2003-01-211-2/+2
| | | | Merge M_NOWAIT/M_DONTWAIT into a single flag M_NOWAIT.
* Redo dma tag creation to correctly reflect the boundary and segmentmjacob2002-09-231-8/+7
| | | | limitations inherent to the isp1000 on SBus cards.
* Frequency default should be '25' for 25MHz, not 25000000.mjacob2002-07-251-7/+23
| | | | | | | | | | Through the PITA of endiannness, clock has to be MHz freq << 8. Don't trust NVRAM on SBus cards. Set a default initiator ID sensibly. SBus/ISP now working, what with the change to sbus.c earlier today.
* Make sure that if are in fact using 'full SMP', make the interruptmjacob2002-07-251-6/+9
| | | | | | | | | flags include INTR_MPSAFE. Put the flags in a common place so that both isp_sbus && isp_pci DTRT. In isp_mbxdma setup, drop any locks prior to calling things like bus_dmatag_create. This gets rid of these obnoxious WITNESS messages about 'sleeping with locks held' blah blah blah blah blah.
* Remove a couple of debugging lines.mjacob2002-07-111-7/+0
|
* 'Support' for ISP SBus cards.mjacob2002-07-111-0/+841
This code does not imply that SBus cards work yet. They hang for me. But I can't netboot the latest snapshot on my ultra1e, and things hang at bus_setup_intr time. Since I'm offline for a while, I thought I'd toss this in in case somebody else who has a bit better luck wants to fart around with it. Please try and wait until I get back to check things in.
OpenPOWER on IntegriCloud