Messages in this thread | | | Subject | Re: More on the IDE multiwrite problem | From | Jes Sorensen <> | Date | 18 Dec 1999 21:57:38 +0100 |
| |
>>>>> "Mark" == Mark Lord <mlord@pobox.com> writes:
Mark> Jes Sorensen wrote: ... >> Isn't there a way to disable the interrupt in the IDE controller's >> registers? Using disable_irq is nasty since many IDE controllers, >> in particular on non x86, run with shared interrupts.
Mark> There is no standard way to do it. Each IDE chip does it's own Mark> thing for interrupt enable/disable. There is a way to do it at Mark> the drive, but the interrupt is supposed to be enabled when we Mark> issue the command, or else we might miss it later. -- Mark Lord Mark> Real-Time Remedies Inc. mlord@pobox.com
Then I would suggest to have the low level drivers register a function that does the chipset specific stuff. The generic IDE code really shouldn't know anything about disable_irq()/enable_irq() nor try to use them.
Jes
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |