From owner-freebsd-arm@freebsd.org Sat Feb 11 19:36:19 2017 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 8E325CDB1E7 for ; Sat, 11 Feb 2017 19:36:19 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 7336D13A4 for ; Sat, 11 Feb 2017 19:36:18 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 50a572d0-f091-11e6-b3c2-c9f38144898e X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 50a572d0-f091-11e6-b3c2-c9f38144898e; Sat, 11 Feb 2017 19:36:00 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v1BJaBux001717; Sat, 11 Feb 2017 12:36:11 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1486841770.10020.287.camel@freebsd.org> Subject: Re: Questions about BBB/BBG dtb names vs. content From: Ian Lepore To: Tony Hain , "'Oleksandr Tymoshenko'" Cc: freebsd-arm@freebsd.org Date: Sat, 11 Feb 2017 12:36:10 -0700 In-Reply-To: <0f3901d2849a$3ac2ca40$b0485ec0$@tndh.net> References: <0ee901d28406$052ed070$0f8c7150$@tndh.net> <20170211015231.GA56071@bluezbox.com> <0f3901d2849a$3ac2ca40$b0485ec0$@tndh.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2017 19:36:19 -0000 On Sat, 2017-02-11 at 11:08 -0800, Tony Hain wrote: > > > > [...] > > There is still the open question about the "compatible" strings > containing > "-" while the file names do not. If that is what is coming from > upstream and > expected, fine. I just wanted to check to make sure something didn't > get > crossed up during the name changes. Hopefully I will get a green > build done > this weekend. > > Tony There is not necessarily any relationship between dts/dtb filenames and  any compat strings within the dtb.  The compat strings are defined by the bindings documentation, and are essentially a contract between the dts source and the device driver source.  The filenames are a separate contract, mostly between vendors and the u-boot source, but even those don't have to agree. Anybody can set the u-boot fdt_file env var to anything they want. IMO, that is the right way to handle all this freebsd and local user customization... if you want a uart device enabled, then create your own tony-bb.dts that includes the standard beaglebone source, then adds the few lines of code needed to enable the uart, and in u-boot just do setenv fdt_file tony-bb.dtb; saveenv.  (At least until overlay support settles down and finds its way into freebsd.) -- Ian