From owner-freebsd-arm@FreeBSD.ORG Tue Mar 17 15:52:05 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1240FF for ; Tue, 17 Mar 2015 15:52:05 +0000 (UTC) Received: from relay.mailchannels.net (si-002-i157.relay.mailchannels.net [108.178.49.169]) by mx1.freebsd.org (Postfix) with ESMTP id E3E0BB4 for ; Tue, 17 Mar 2015 15:52:04 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (ip-10-237-13-110.us-west-2.compute.internal [10.237.13.110]) by relay.mailchannels.net (Postfix) with ESMTPA id B4B89120552; Tue, 17 Mar 2015 15:51:56 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (smtp7.ore.mailhop.org [10.45.8.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Tue, 17 Mar 2015 15:51:57 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426607516896:3989054219 X-MC-Ingress-Time: 1426607516896 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp7.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YXtmc-0000Tn-Jy; Tue, 17 Mar 2015 15:51:54 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2HFpoT2025870; Tue, 17 Mar 2015 09:51:50 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX18ml4Qcu9zuDfFU91royBkU Message-ID: <1426607510.25614.3.camel@freebsd.org> Subject: Re: How to use u-boot-beaglebone port? From: Ian Lepore To: Warner Losh Date: Tue, 17 Mar 2015 09:51:50 -0600 In-Reply-To: References: <17B779D7-2962-4455-9062-51411F316648@gromit.dlib.vt.edu> <986F5E5D-C784-4BEF-81E3-49A9F27C0E8F@kientzle.com> <1426534773.95554.15.camel@freebsd.org> Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 X-AuthUser: hippie Content-Transfer-Encoding: quoted-printable Cc: Tim Kientzle , freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 15:52:05 -0000 On Tue, 2015-03-17 at 08:16 +0900, Warner Losh wrote: > > On Mar 17, 2015, at 4:39 AM, Ian Lepore wrote: > >=20 > > [*] Because armv6 !=3D armv7 in this case. While armv6 is synonymous= with > > armv7 for most purposes in freebsd, the rpi is the exception to that = in > > that it really IS armv6, and that leads to the kernel being built wit= h > > different cache maintenance routines that don't work on armv7. >=20 > I thought all that was handled through a separate vector so we could, > in theory, do that. All of it is conditional, but that vectors back via= a table. > It=A2s been like that on arm since day one, though maybe that got broke= n > somewhere. >=20 > Warner >=20 Not broken, but rather "undone, by design." We now pass the proper arch on the command line so that v7 stuff gets built using v7 opcodes and with the right ACLE stuff defined. (This is actually all still in progress, some stuff still vectors through the old cpufuncs table.) We support RPi but we no longer let it cripple the newer boards/socs in pursuit of a mythical unified kernel that's never going to happen (at least, it's not going to happen in the form of v6+v7 in the same kernel). -- Ian