| To: | Bryan Althouse <bryan.althouse@3phoenix.com> |
|---|---|
| Subject: | RE: custom ide driver causes "Badness in smp_call_function" |
| From: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
| Date: | Fri, 26 Aug 2005 16:47:24 +0100 |
| Cc: | linux-mips@linux-mips.org, "'Ralf Baechle'" <ralf@linux-mips.org> |
| In-reply-to: | <20050826145303Z8224974-3678+7581@linux-mips.org> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20050826145303Z8224974-3678+7581@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Gwe, 2005-08-26 at 10:58 -0400, Bryan Althouse wrote:
> Ralf,
>
> The patch doesn't seem to make any difference. :(
Assuming your hardware is sane another approach might be to force
drive->unmask = 1. That will mean that PIO mode is running with
interrupts enabled which should avoid the problem.
Add a .fixup handler to your driver (assuming you are using a recent
2.6.x) and in the handler do something like this:
+void ide_unmask_interrupts(ide_hwif_t *hwif)
+{
+ int i;
+ for (i = 0; i < 2; i++) {
+ ide_drive_t *drive = &hwif->drives[i];
+ if(drive->present)
+ drive->unmask = 1;
+ }
+}
hopefully that will be early enough.
|
| Previous by Date: | RE: custom ide driver causes "Badness in smp_call_function", Bryan Althouse |
|---|---|
| Next by Date: | Re: patch / rfc, Pete Popov |
| Previous by Thread: | RE: custom ide driver causes "Badness in smp_call_function", Bryan Althouse |
| Next by Thread: | RE: custom ide driver causes "Badness in smp_call_function", Bryan Althouse |
| Indexes: | [Date] [Thread] [Top] [All Lists] |