linux-mips
[Top] [All Lists]

Re: SEGEV defines

To: Bradley Bozarth <bbozarth@cisco.com>
Subject: Re: SEGEV defines
From: Daniel Jacobowitz <dan@debian.org>
Date: Thu, 7 Nov 2002 17:10:29 -0500
Cc: linux-mips@linux-mips.org, george@mvista.com
In-reply-to: <Pine.LNX.4.44.0211071229340.7794-100000@bbozarth-lnx.cisco.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.GSO.3.96.1021107201241.5894L-100000@delta.ds2.pg.gda.pl> <Pine.LNX.4.44.0211071229340.7794-100000@bbozarth-lnx.cisco.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.1i
Presumably they match IRIX... like the rest of MIPS's oddball
definitions.  A little hard to change them now.

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.
> 
> 
> 
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

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