linux-mips
[Top] [All Lists]

Re: SEGEV defines

To: Daniel Jacobowitz <dan@debian.org>
Subject: Re: SEGEV defines
From: tor@spacetec.no (Tor Arntsen)
Date: Fri, 8 Nov 2002 10:14:53 +0100
Cc: linux-mips@linux-mips.org, george@mvista.com, Bradley Bozarth <bbozarth@cisco.com>
In-reply-to: Daniel Jacobowitz <dan@debian.org> "Re: SEGEV defines" (Nov 7, 23:11)
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
On Nov 7, 23:11, Daniel Jacobowitz wrote:
>Presumably they match IRIX... like the rest of MIPS's oddball
>definitions.  A little hard to change them now.

FWIW: You are correct, those values come from IRIX.

>On Thu, Nov 07, 2002 at 12:33:55PM -0800, Bradley Bozarth wrote:
>> Can these be changed?
>> 
>> > Now a question, why does mips use these values:
>> >  #define SIGEV_SIGNAL   129     /* notify via signal */
>> >  #define SIGEV_CALLBACK 130     /* ??? */
>> >  #define SIGEV_THREAD   131     /* deliver via thread
>> > creation */
>> >
>> > It is the only platform that adds anything to the simple
>> > 1,2,3 values used on other platforms.  The reason I ask, is
>> > that I would like to change them to conform to all the
>> > others.

<Prev in Thread] Current Thread [Next in Thread>