Option error

[Darek Dwornikowski]

>>>>> i found that old serial_cs module had irq_list parameter. the new one does
>>>>> not have this parameter, maybe this could be a good dirty workaround. Iv
>>>>> got some IRQs free and could dedicate them for my pcmcia card.
>>>>>     
>>>>>         
>>>>>           
>>>> If they're not connected to the PCMCIA bridge, they won't be able to be
>>>> used.  The available interrupts are really a function of the PCMCIA
>>>> socket bridge and its driver, not the individual card drivers.
>>>>       
>>>>         
>>> uhm.. so what should i do ? implement shared_irq in serial_cs.c ? this
>>> is the place to do it ?
>>>     
>>>       
>> serial_cs *always* requests shared interrupts.
>>
>> What's the problem?
>>
>>   
>>     
> pccard: PCMCIA card inserted into slot 0
> pcmcia: registering new device pcmcia0.0
> pcmcia: request for exclusive IRQ could not be fulfilled.
> pcmcia: the driver needs updating to supported shared IRQ lines.
>
>
> i get this when inserting my option card. i was told on this list that
> this causes my problem.
> i am not an expert but in serial_cs.c is :
>         link->irq.Attributes = IRQ_TYPE_EXCLUSIVE;
> in serial_probe    function
>
>   
  I took axnet_cs.c for example of shared irqs:

      request_irq(dev->irq, ei_irq_wrapper, IRQF_SHARED, "axnet_cs", dev);
   
  My question is howto register my new "serial_cs" irq to implement
shared irqs in serial_cs. Or is my logic wrong ?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.infradead.org/pipermail/linux-pcmcia/attachments/20061009/73b33ae2/attachment.bin