On Thu, Sep 14, 2000 at 06:26:13PM +0200, Tomasz Motylewski wrote:
> On Thu, 14 Sep 2000 [EMAIL PROTECTED] wrote:
>
> > Can you explain the example a little more? Both cards can be installed in the
> > same box at the same time? Or not?
>
> Yes.
>
> >
> > In any the rtl_request_irg irq handler is called with the irq# as an argument so
> > why doesn't that get you what you need?
>
> Because we are back to the solution used in Linux 1.2. I have to maintain the
> table of devices assigned to interrupts. This is so general functionality,
> that should be provided by the OS.
>
> I agree that doing such lookup (irq->dev_id) uses some time. So what about
> providing a macro which could be called in RT-ISR
>
> get_device_id()
Would
rtl_dev_t get_device_id(irq);
int assign_device_id(irq,devid);
work?
>
> ?
>
> So, registration routine should save device_id and name somewhere. But
> getting this information in RT-ISR would by optional - no performance
> penalty if not used. What about such solution?
>
> > And what about sigaction(int signum, const struct sigaction *act, struct
> > sigaction *oldact)?
>
> I do not understand relation of sigaction to interrupts.
In RTLV3
sigaction(RTL_SIGIRQMIN+n,&act,&oldact)
installs an interrupt handler for irq=n using standard sigaction conventions.
This is essentially a wrapper for rtl_request_irq
>
> Best regards,
> --
> Tomek
--
---------------------------------------------------------
Victor Yodaiken
Finite State Machine Labs: The RTLinux Company.
www.fsmlabs.com www.rtlinux.com
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
