| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
don't care about the alignment, set it to 1, meaning single byte alignment.
|
| |
|
|
| |
driver is probably not far from being MI now anyway.
|
| |
|
|
| |
the isa probe has gone hunting for a card on it's own.
|
| | |
|
| | |
|
| |
|
|
| |
to the BUS_SETUP_INTR call.
|
| |
|
|
| |
the isa bus doesn't clear the hints at that point.
|
| |
|
|
|
|
|
|
|
|
|
| |
- fix cut/paste problem. :-)
- don't forget to call isa_dmacascade()
- reset the port after we release resources.
That last one is a trap to watch out for.. The isa bus driver uses the
same port/irq/mem/etc variables for the initial probe hints as it does
for allocation/deallocation tracking. Releasing a resource clears the
variable and then you loose the hint during attach.. (ouch!)
|
| |
|
|
|
|
|
|
|
| |
had a quirk that made a shim rather hard to implement properly and it was
just easier to convert the drivers in one go. The changes to the
buslogic driver go beyond just this - the whole driver was new-bus'ed
including pci and isa. I have only tested the EISA part of this so far.
Submitted by: Doug Rabson <dfr@nlsystems.com>
|
| | |
|
| |
|
|
|
| |
commands sent to card, into the base driver module. It is now used for
EISA board probes too.
|
| | |
|
| |
|
|
|
|
|
|
| |
hasseen_isadev so this will be less noisy when conflicts do exist.
Also eliminate redundant warnings about conflicts.
Requested by: bde
Reviewed by: gibbs
|
| |
|
|
|
|
|
|
|
|
| |
o For bt and aha only probe the one I/O range if a specific I/O is specified
in the config file.
o Don't even try to probe I/O ranges that have been seen already.
o If we conflict with an IRQ or DRQ, then fail the probe.
Requested by: bde, gibbs
Approved by: jkh
|
| |
|
|
| |
empty but regressed to including it here.
|
| |
|
