From owner-freebsd-ppc@freebsd.org Sun Oct 11 21:52:09 2015 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 522109B20FD for ; Sun, 11 Oct 2015 21:52:09 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AFED1F6E for ; Sun, 11 Oct 2015 21:52:09 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by ioii196 with SMTP id i196so135689669ioi.3 for ; Sun, 11 Oct 2015 14:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references; bh=oCJdJsWK0b0G6O+0dvGmEU4uxJfkyEhEisGWCnF5Ir8=; b=atb45OGQUlyFHOTFm6lrdlINUMKbrX+N1t8YJXg8KCmW4fWL7yFw2lLy+Ii9xm7gSZ JluFn5yYbec/tbDkFXIjaFcYpCX6cgzPr57YzFJ/2u8SINpVRg8WN00nRDN1+12tHDQb 0F6vqtdaoJ+ZrVZ7eX2BJGRdoFhsfgro79WMgqvjOvImo261bnnUo03F/UZqNNz61PBy I5ZA0Zk9AjCFRk+Obm+Dj+dtXjHfcZE12YhcmTNzQPHuJRdsfskIUFSAJ5Kz+LzUN5V4 ce1c4630l4nLahHRMvEUT0G9ECEWL9agAmQjWobx5LpxjAsbycHIg1jctzT8nqI6KxxA EtBg== X-Received: by 10.107.130.217 with SMTP id m86mr28812990ioi.22.1444600328538; Sun, 11 Oct 2015 14:52:08 -0700 (PDT) Received: from blackstar.knownspace (c-98-240-160-157.hsd1.mn.comcast.net. [98.240.160.157]) by smtp.gmail.com with ESMTPSA id t2sm3763744igs.18.2015.10.11.14.52.07 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 11 Oct 2015 14:52:08 -0700 (PDT) Cc: "freebsd-ppc@FreeBSD.org" Message-Id: From: Justin Hibbits To: Thomas Rix In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: e500 SPE support Date: Sun, 11 Oct 2015 16:52:30 -0500 References: X-Mailer: Apple Mail (2.936) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2015 21:52:09 -0000 You can find it on amazon, = http://www.amazon.com/Mikrotik-RB800-RouterBOARD-MiniPCI-RouterOS/dp/B00D8= 4KR76/ref=3Dsr_1_1?ie=3DUTF8&qid=3D1444599696&sr=3D8-1&keywords=3DRouterBo= ard+RB800=20 . It's kind of expensive, but FreeBSD netboots fine on it (I'm working =20 on getting it to locally boot). I thought FreeBSD would boot on the =20 p2020, can you tell me what doesn't work for it? - Justin On Oct 9, 2015, at 5:07 PM, Thomas Rix wrote: > I have a p2020rdb I would prefer to use but it doesn=B9t seem to have > freebsd kernel support so toolchain work is only on linux. > Please send me a link to where you bought your board, I will see about > getting one. > Thanks, > Tom > > --- > Tom Rix > Sr. Staff Compiler Engineer > trix@juniper.net > > > > > > On 10/9/15, 2:14 PM, "Justin Hibbits" wrote: > >> After talking with others, I'll be creating a new target, >> powerpc/powerpcspe. This will live in a branch while I stabilize it >> (I'll create a branch this weekend). My testing will be on the >> Mikrotik RouterBoard RB800, but if anyone has hardware they can test >> on, all the better. >> >> To keep things simple, I'll be overloading the enable_vec()/=20 >> save_vec() >> functions, and using this common API between Altivec and SPE. >> >> - Justin >> >> On Tue, Oct 6, 2015 at 10:30 AM, Thomas Rix wrote: >>> I see the spe feature is in ToT llvm, but not no target is has this >>> enabled by default. >>> What hardware/software are you using to exercise the feature ? >>> Asking so I could play too :) >>> >>> Likely folks wanting the feature would be willing to trade off with >>> altivec. >>> So mutually exclusive for me. >>> >>> Sprinkling code with spe specific seems clunky. >>> Could there be some task bit that linker/compiler sets that the =20 >>> loader >>> uses to do this automagically ? >>> A tie into the task state would help with ptrace and possible =20 >>> debugger >>> support. >>> >>> Tom >>> >>> --- >>> Tom Rix >>> Sr. Staff Compiler Engineer >>> trix@juniper.net >>> >>> >>> >>> >>> >>> On 10/4/15, 9:14 PM, "owner-freebsd-ppc@freebsd.org on behalf of =20 >>> Justin >>> Hibbits" >> chmeeedalf@gmail.com> >>> wrote: >>> >>>> I've been doing some work on the e500 Signal Processing Engine =20 >>>> (SPE, >>>> sort of like Altivec, only weirder), but have some questions on >>>> implementation: >>>> >>>> * This is mutually exclusive to Altivec, of course, because it =20 >>>> shares >>>> the GPRs, extending them to 64-bits, but only for SPE instructions. >>>> Should the implementation be mutually exclusive, as well? =20 >>>> Meaning, is >>>> it better to have enable_spe()/save_spe() strewn throughout the =20 >>>> code, >>>> like is done with Altivec and FPU, or is it better to name them >>>> *_vec(), and have a compile-time option of switching between =20 >>>> Altivec >>>> and SPE? The userland ABI would be different as well, which =20 >>>> brings the >>>> next question: >>>> >>>> * Do we want another target, like how Linux does it =20 >>>> (powerpcspe)? Or >>>> have this as just a different build option in src.conf? >>>> >>>> Suggestions are welcome and wanted. >>>> >>>> - Justin >>>> _______________________________________________ >>>> freebsd-ppc@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>>> To unsubscribe, send any mail to = "freebsd-ppc-unsubscribe@freebsd.org=20 >>>> " >>> >