From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.genesippc.com (mithrandir.softwarenexus.net [66.98.186.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 9F39067B77 for ; Sun, 23 Jul 2006 23:28:15 +1000 (EST) From: "Matt Sealey" To: "'Segher Boessenkool'" Subject: RE: AltiVec in the kernel Date: Sun, 23 Jul 2006 15:28:02 +0200 Message-ID: <006701c6ae5b$d5e83620$7302a8c0@bakuhatsu.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" In-Reply-To: Cc: 'Olof Johansson' , 'linuxppc-dev list' , 'Paul Mackerras' Reply-To: matt@genesi-usa.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > You could give Freevec a whole lot more exposure, to people > who might be more interested in it than the average glibc > user, by putting it into uClibc first. [snip] > You'll have to update uClibc's PowerPC port first though > (mostly just copying stuff from recent glibc) -- it seems the > libc AltiVec support (for handling setjmp() etc.) isn't in there yet. I remember a discussion from one of the Gentoo guys wanting to do this with libfreevec. Getting into Gentoo, though, is not difficult. The problem with this is Gentoo is one Linux distribution. I would be more impressed if code was in Debian or Ubuntu considering their exhausting lead times on producing new package trees and accepting new code :D -- Matt Sealey Manager, Genesi, Developer Relations