Am 2005-01-04 16:15 +0200 schrieb Olav Kongas:
> Could you please be more specific here.
Well, IIRC we postet our actual problems to this list...
> > irq65: nobody cared
>
> I think "nobody cared" means two things: either there was no
> irq handler for that irq installed, or the existing handler
> returned neither IRQ_HANDLED nor IRQ_NONE. To discriminate
> between these cases, you can add to the end of the
> isp116x_irq(), just before the 'return ret;' statement a
> prink showing the 'ret' value.
When I do that, the stack_dump and reg_dump
output is ommitted and the kernel spews a
dozen "ret value: 0x1" on the console (printk("ret value: 0x%x\n",
ret); between spin_unlock and return).
I mean exact two or three "ret value: 0x1" when initialing and than when
insertring a storage device for ever.
> There is no dma resource parsing in the driver. You can
> remove this entry.
OK, we were not 100% sure :)
> Are you sure this directly copied reset function really
> works for you too?
Hell noo! This way I see when it is triggered and will implement it
later. The isp1161a1 should be ready to use after POR.
> these. Maybe you have to set some other parameters (see
> usb_isp116x.h).
The HWCF Register Setup is triple checked and should be OK.
> Otherwise, the platform conf seems ok.
Hm. Nice to know. But insertring the printk does cause so weird errors.
wtf?
Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
