From owner-freebsd-arm@freebsd.org Wed Jun 8 18:56:08 2016 Return-Path: Delivered-To: freebsd-arm@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 BA5F7B6F890 for ; Wed, 8 Jun 2016 18:56:08 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E6521335 for ; Wed, 8 Jun 2016 18:56:08 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2B00E21D50; Wed, 8 Jun 2016 14:56:07 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 08 Jun 2016 14:56:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= blackskyresearch.net; h=cc:content-transfer-encoding :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=0WdzL On7Gk0bGkBan0BwxHQ1Qkc=; b=j79AQsvHjvLFG6kjhr8y4D1m7OvEFTi82hlRi /+x1UY0tSnKOWJD4+7c0RSyDWUDrdDGn/yfqZZuxXDSaI6pJdufvwF/Lpb8gph7P VOSQz9pDVcoH7PGY1STHMJbZmau2bQ2xeRPS7coA/p9qjWxlql9tzSyQO7Pi0AcR f2eJZE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=0WdzLOn7Gk0bGkB an0BwxHQ1Qkc=; b=RHU/FnGW2uxN1H6mR3vCjGR/RLtR4Ve+XUVIWG9FAYLzAD4 yRyGMevX0UFkizugsmLz/ejr0k3r7ewtn9l2dBaxGCf+EN95MCnQrM2rt8cncv2v gfOdU2ecm/JVIdSANK15HYSDkeFqLjjhRw5wE2w8ROU7FSGofRUc/E9eK3TE= X-Sasl-enc: /WFFqYPx36aU6CHCQ3RDavmh3FskkLNO4DfFSUZXcV3a 1465412166 Received: from [10.22.162.12] (unknown [66.111.12.42]) by mail.messagingengine.com (Postfix) with ESMTPA id C8648CCDB1; Wed, 8 Jun 2016 14:56:06 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: RPI3 Hackathon at BSDCan/Dev SUmmit From: "Isaac (.ike) Levy" In-Reply-To: <20160608182810.GC63330@mutt-hardenedbsd> Date: Wed, 8 Jun 2016 14:56:06 -0400 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0E28F6C5-96BC-4696-AD8F-C898CA0082D9@blackskyresearch.net> References: <20160607043134.GB22884@mutt-hardenedbsd> <20160607123450.GA75317@mutt-hardenedbsd> <20160608165711.GA63330@mutt-hardenedbsd> <20160608170107.GB63330@mutt-hardenedbsd> <20160608182810.GC63330@mutt-hardenedbsd> To: Shawn Webb X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2016 18:56:08 -0000 > On Jun 8, 2016, at 2:28 PM, Shawn Webb = wrote: >=20 > Your builds would be ARMv7, correct? As far as I know, there are no > ARMv8 BeagleBone boards. Oh, I could be very mistaken- perhaps someone on list could help me = understand this- (searching the web isn't helping me here), Can anyone on list here help me clarify the ARMv7 or ARMv8 = architectures? -- I have a couple of Beaglebone Black boards, I'm unclear if it's ARMv7 or = ARMv8, because all the Beagleboard/TexasInstruments literature just says = "Cortex-A8". https://beagleboard.org/black https://www.ti.com/product/am3358 It's a 32 bit cpu, but no mention of ARMv7 there? Interestingly, I see there's a ton of new excitement for ARMv8, (SO WISH = I WAS THERE!) https://www.bsdcan.org/2015/schedule/events/549.en.html yet from searching the net, the ARM page in the FreeBSD wiki currently = has no mention of ARMv8, https://wiki.freebsd.org/FreeBSD/arm I may just be searching poorly :) >=20 > I'm excited to see that you're making progress, nonetheless! Me too, will be happy if it compiles! (I have a nice little applied use for a simple/el-cheapo wireless access = point in an odd location, and if I can get this working with OPNsense, = I'll be delighted.) Best, .ike >=20 > On Wed, Jun 08, 2016 at 02:21:34PM -0400, Isaac (.ike) Levy wrote: >> Hi Shawn, >>=20 >> Sadly, not able to make it to Canada this year, but for the last week = or so since your announce I've been nudging along builds of OPNSense on = ARMv8, via beaglebone boards, building from FreeBSD 11-ALPHA2 images. = Nothing special since the base ARM work comes from stock FreeBSD, I'm = just compiling it. >>=20 >> My last build started yesterday, which apparently incorporates your = HardenedBSD work as well, exciting to see all this work coming together! >>=20 >> So far so good, burning some micro-SD media to get the job done, so = it just takes *time* ;) >> Will happily give a shout when I have successful serial images built. >>=20 >> Best, >> .ike >>=20 >>=20 >>=20 >>> On Jun 8, 2016, at 1:01 PM, Shawn Webb = wrote: >>>=20 >>> It's available for free from ARM, but you have to sign up for an >>> account. Due to having to sign up, I'm unsure I can share the >>> documentation myself. It's the ARMv8 reference documentation. >>>=20 >>> On Wed, Jun 08, 2016 at 04:58:56PM +0000, Manas Bhatnagar wrote: >>>> Share the reference documentation and I'm sure more folks would = take a look >>>> at it. Sorry if you've sent it before, I must have missed it. >>>>=20 >>>> On Wed, Jun 8, 2016, 12:57 Shawn Webb = wrote: >>>>=20 >>>>> I've talked with Andrew Turner, who gave me a little bit of info = to use >>>>> as a starting point. We need to get U-Boot EFI working on the RPI3 >>>>> first. Luiz Otavio O Souza is the current U-Boot expert in = FreeBSD, so >>>>> I'm CC'ing him here. He's here at the Dev Summit, so I'm hoping he = might >>>>> have time to help out. >>>>>=20 >>>>> If I can't get the right knowledgeable people involved, I'm going = to >>>>> cancel the hackathon. I simply lack the knowledge regarding ARM64 = and >>>>> the RPI3 hardware to do anything myself over the course of the = next four >>>>> days. The ARM64 reference documentation is several thousands of = pages, >>>>> and I'm only a few hundred pages in. I'll continue on, but I still = have >>>>> a ways to go. ;) >>>>>=20 >>>>> I'm really hoping to get some help from the FreeBSD community. >>>>>=20 >>>>> Thanks, >>>>>=20 >>>>> Shawn >>>>>=20 >>>>> On Tue, Jun 07, 2016 at 08:34:50AM -0400, Shawn Webb wrote: >>>>>> Hey, >>>>>>=20 >>>>>> I'm hoping we can convince Andrew Turner to help us out. He has >>>>>> existing code at = https://github.com/zxombie/freebsd/tree/arm64-rpi3 but >>>>>> that hasn't been updated for a while now. FreeBSD HEAD has = diverged >>>>>> enough to cause merge conflicts, some of which I think I might've = fixed >>>>>> in my own code repo, but I don't know jack about that code so I = probably >>>>>> made mistakes. >>>>>>=20 >>>>>> The RPI3 devices we're bringing all have SD cards in them along = with >>>>>> serial cables that can also power the device. We're also bringing >>>>>> somewhere around 5-7 SD card readers. So we'll have plenty of = devices to >>>>>> hack and test on. >>>>>>=20 >>>>>> I can help coordinate the work, but we really need help from = those who >>>>>> understand arm64 and the chips in the RPI3. >>>>>>=20 >>>>>> Thanks, >>>>>>=20 >>>>>> Shawn >>>>>>=20 >>>>>> On Tue, Jun 07, 2016 at 08:26:20AM -0400, Manas Bhatnagar wrote: >>>>>>> Hello, >>>>>>>=20 >>>>>>> I am interested, but I really do not know much about programming = for >>>>>>> the FreeBSD kernel. Still, I'm happy to help in any way that I = can :) >>>>>>>=20 >>>>>>> Manas >>>>>>>=20 >>>>>>> On Tue, Jun 7, 2016 at 12:31 AM, Shawn Webb < >>>>> shawn.webb@hardenedbsd.org> wrote: >>>>>>>> Hey All, >>>>>>>>=20 >>>>>>>> HardenedBSD is bringing 10+ RPI3 devices to hack on during the = Dev >>>>>>>> Summit and during BSDCan. I'm really hoping that we can get = RPI3 >>>>> support >>>>>>>> with latest HEAD by the end of BSDCan. >>>>>>>>=20 >>>>>>>> I'm reading through the ARM64/AArch64 reference docs myself and = have >>>>> a >>>>>>>> long ways to go. I would still consider myself a complete newb = in >>>>> ARM64. >>>>>>>> So, in order to make my hope a reality, I'm going to need a bit = of >>>>> help. >>>>>>>>=20 >>>>>>>> Who's interested in participating in the hackathon? >>>>>>>>=20 >>>>>>>> Thanks, >>>>>>>>=20 >>>>>>>> -- >>>>>>>> Shawn Webb >>>>>>>> Cofounder and Security Engineer >>>>>>>> HardenedBSD >>>>>>>>=20 >>>>>>>> GPG Key ID: 0x6A84658F52456EEE >>>>>>>> GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F = 5245 >>>>> 6EEE >>>>>>=20 >>>>>> -- >>>>>> Shawn Webb >>>>>> Cofounder and Security Engineer >>>>>> HardenedBSD >>>>>>=20 >>>>>> GPG Key ID: 0x6A84658F52456EEE >>>>>> GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F = 5245 6EEE >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> Shawn Webb >>>>> Cofounder and Security Engineer >>>>> HardenedBSD >>>>>=20 >>>>> GPG Key ID: 0x6A84658F52456EEE >>>>> GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 = 6EEE >>>>>=20 >>>=20 >>> --=20 >>> Shawn Webb >>> Cofounder and Security Engineer >>> HardenedBSD >>>=20 >>> GPG Key ID: 0x6A84658F52456EEE >>> GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 = 6EEE >>=20 >=20 > --=20 > Shawn Webb > Cofounder and Security Engineer > HardenedBSD >=20 > GPG Key ID: 0x6A84658F52456EEE > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 = 6EEE