From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <521DFBE7.2090406@xenomai.org> Date: Wed, 28 Aug 2013 15:32:23 +0200 From: Philippe Gerum MIME-Version: 1.0 References: <521DD3DD.6010300@siemens.com> <521DD7D9.6040108@siemens.com> <521DD92F.7010509@xenomai.org> <521DDA0C.9040204@siemens.com> In-Reply-To: <521DDA0C.9040204@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] IPIPE_KEVT_SETAFFINITY List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Xenomai On 08/28/2013 01:07 PM, Jan Kiszka wrote: > On 2013-08-28 13:04, Philippe Gerum wrote: >> On 08/28/2013 12:58 PM, Jan Kiszka wrote: >>> On 2013-08-28 12:41, Jan Kiszka wrote: >>>> Hi Philippe, >>>> >>>> please push to ipipe.git what introduces IPIPE_KEVT_SETAFFINITY. I'm >>>> riding on the tip of all trees and cannot build forge anymore. >>> >>> Ah, oversaw it. It's in stable ipipe-3.8 only. Will pick it up for my >>> master queue. >>> >>>> Or does >>>> this event rather require some feature detection in forge? >>> >>> I suppose the policy for forge is still to require latest, full-featured >>> I-pipe patches, right? >>> >> >> Yes, so that we start playing with wrappers as late as possible, at >> least not before the first official release is out. > > But wrappers for older kernel version (3.x) are fine? Asking as I will > introduce one for the procfs stuff of 3.10. See [1]. > Yes, since -forge still supports 3.8 anyway. Currently, the oldest supported release is 3.5. > Jan > > [1] > http://git.xenomai.org/?p=xenomai-jki.git;a=commitdiff;h=e94d8b0b53b7309d640a97309f65056accbb2ec7 > -- Philippe.