On Thu, Jan 01, 2004 at 05:35:15PM -0800, David Brownell wrote:
> >From include/asm/signal.h, SIGRTMIN == 32, SIGRTMAX == 31.
>
> Try linux/include/asm-i386/signal.h ... 32 realtime signals.
We are looking in the same place. The file I mentioned
(include/asm/signal.h) is a symlink to linux/include/asm-i386/signal.h
on an i386 platform.
On Fri, Jan 02, 2004 at 01:25:58AM +0100, Oliver Neukum wrote:
> For async IO. You can arrange to be sent a signal if the urb you
> submitted finishes. The legal values appear to be 31 and 32, 0
> meaning no signal.
> Perhaps you might send in a patch to correct the comment. Talking
> about
> an unsigned variable being -1 should not happen.
I think the logic
if (uurb.signr != 0 && (uurb.signr < SIGRTMIN || uurb.signr > SIGRTMAX))
causes the error return if (signr < 32) or (signr > 31). I cannot think of
any integers that don't meet this (except 0 because of the separate test).
What is the design intention here? Which signals should be allowed?
I don't see why the driver shouldn't send any signal the user asks for.
If the users asks for one of the ones with special side effects, he
deserves what happens. But why not allow signals like SIGUSR1/2?
Don Reid
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
