From owner-freebsd-arm@freebsd.org Mon Jul 17 18:34:40 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 7DAD9D9D7E3 for ; Mon, 17 Jul 2017 18:34:40 +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 610AE6BDF9 for ; Mon, 17 Jul 2017 18:34:40 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 89c9644b-6b1e-11e7-a4a1-c9e62e5d9688 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 89c9644b-6b1e-11e7-a4a1-c9e62e5d9688; Mon, 17 Jul 2017 18:34:16 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v6HIYbj1006217; Mon, 17 Jul 2017 12:34:37 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1500316477.22314.91.camel@freebsd.org> Subject: Re: BBB & IMX6 Hummingboard SDIO driver From: Ian Lepore To: Russell Haley Cc: freebsd-arm Date: Mon, 17 Jul 2017 12:34:37 -0600 In-Reply-To: References: <1500258608.22314.63.camel@freebsd.org> 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: Mon, 17 Jul 2017 18:34:40 -0000 On Mon, 2017-07-17 at 11:32 -0700, Russell Haley wrote: > On Sun, Jul 16, 2017 at 7:30 PM, Ian Lepore wrote: > > > > On Sun, 2017-07-16 at 17:41 -0700, Russell Haley wrote: > > > > > > Hi, > > > > > > I'm building for a BBB and I think I've got almost everything but > > > I > > > er... can't find the dtb file or the uEnv.txt file. Any help > > > would be > > > grand? I have a feeling I'm going to have to beg/borrow/steal a > > > uEnv.txt file from a pre-built image. > > > > > > As I'm going through the process of re-learning the build steps, > > > i > > > thought of a couple of things that I either didn't see or > > > couldn't > > > find on the website: > > > > > > - A list of boards and their kernel config files > > > - An easy reference on where to find the bits after the build. > > > yes, > > > yes, it's in the handbook. > > > - Since u-boot has been standardised now, it would be nice to > > > have a > > > section on where to get u-boot and the other bits needed to boot. > > > > > > Anyway, I've got an unprecedented week with no work and no kids, > > > so > > > I'm going to do what any sane person would do during a beautiful > > > July > > > summer: play with FreeBSD! > > > > > > My end goal - and this is a stretch target - is to try and adopt > > > Illyia's SDIO driver. I'm not sure how far I'll get, or much time > > > I'll > > > have after my week is up, but that's what my objective is. I've > > > built > > > the system using the kernel config BEAGLEBONE-MMCCAM in the blind > > > hope > > > that it will use his drivers? Once I get that working and can > > > verify > > > it in dtrace (maybe? yet another rabbit hole!) I want to get it > > > working on my IMX6 hummingboard. > > > > > > oh, and I suppose I should open up some code, eh? > > > > > > Okay, now why isn't my PC computer seeing my sd cards? grrr... ;) > > > > > > Cheers, > > > > > > Russ > > You don't need a uenv.txt file.  It was always optional, and with > > the > > latest uboot stuff it's completely gone. > > > > -- Ian > Thanks Ian. > > DTB files are apparently generated with buildworld. > > https://wiki.freebsd.org/FlattenedDeviceTree > > I know they are generated with a specific tool (the name of which I > forget) . I'm surprised it's not it's own target or at least part of > buildkernel. > > Russ The DTB files installed on our distributed images are built from sys/modules/dtb (which makes them part of the kernel build unless you go out of your way to build them by themselves). -- Ian