Lemme look through the code base tommorrow and get a feel for this.

If just cutting over isn't that hard I may just write this all up, post it
for comments on tech-kern and go ahead. Otherwise yes, migration is simpler
(probably with macro overrides so someone doesn't have to change the names
twice as isa_intr_establish is a perfectly good name).

James

>
>You can introduce isa_intr_establish_no_panic() (just pick a better name :)
>which returns NULL on failure and then slowly migrate the drivers over
>to using that.
>I think that would be a better solution.
>
>    -- Lennart
>
>jchacon@genuity.net wrote:
>
>> There's 2 ways to really look at this:
>>
>> 1. wssattach() looks at already assigned irq's and doesn't try to attach if
>>    it's irq is taken. (Ok, yuck..violates some abstraction and gets very bad
>>    very quick).
>>
>> 2. Have isa_intr_establish return NULL on conflict cases and all drivers that
>>    use it start checking return values. (Not horrible, but would require some
>>    fairly wide code changes).
>>
>> James
>
>
>
>
>