From owner-freebsd-arm@FreeBSD.ORG Wed Oct 8 05:35:03 2014 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 8A9DC21C for ; Wed, 8 Oct 2014 05:35:03 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DD848DC for ; Wed, 8 Oct 2014 05:35:02 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s985YqRM035605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Oct 2014 22:34:52 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s985Yp6r035604; Tue, 7 Oct 2014 22:34:51 -0700 (PDT) (envelope-from jmg) Date: Tue, 7 Oct 2014 22:34:51 -0700 From: John-Mark Gurney To: Luiz Otavio O Souza Subject: Re: FreeBSD on BeagleBone Black Message-ID: <20141008053451.GV1852@funkthat.com> Mail-Followup-To: Luiz Otavio O Souza , ticso@cicely.de, AN , "freebsd-arm@freebsd.org" References: <20141008010436.GA12125@cicely7.cicely.de> <20141008030621.GU1852@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 07 Oct 2014 22:34:53 -0700 (PDT) Cc: "freebsd-arm@freebsd.org" , AN , ticso@cicely.de 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: Wed, 08 Oct 2014 05:35:03 -0000 Luiz Otavio O Souza wrote this message on Wed, Oct 08, 2014 at 01:07 -0300: > On 8 October 2014 00:06, John-Mark Gurney wrote: > > Bernd Walter wrote this message on Wed, Oct 08, 2014 at 03:04 +0200: > >> On Tue, Oct 07, 2014 at 05:05:10PM -0400, AN wrote: > >> > Hi List: > >> > > >> > I have been using FreeBSD current on amd64 for many years. I now have a > >> > project that I want to try to run on FreeBSD. I'm trying to boot a > >> > FreeBSD image on a BeagleBone Black Rev C without success. > >> > > >> > FreeBSD-11.0-CURRENT-arm-armv6-BEAGLEBONE-20140903-r270990.img > >> > FreeBSD-arm-10.0-BEAGLEBONE.img > >> > > >> > The above images fail to boot. > >> > >> Basicly the BBB works very well under FreeBSD. > >> Did you check the uart output? > >> I'm not sure if those images are build with grafic support and > >> there will be nothing on HDMI or attached LCD without it. > >> To be honest: I don't even know if we have support for that output > >> already with the BBB. > > > > We definately do not support output on HDMI... I'm trying to get the > > datasheet so I can get HDMI output working... > > Please, see: https://lists.freebsd.org/pipermail/freebsd-arm/2014-March/007822.html > > Gonzo did the LCD driver (which feed data into HDMI framer) and tried > to port the TDA19988 HDMI framer driver. Yeh, I got patches from him recently for this, but he said he was still having issues... I'm waiting for the Foundation to get a proper spec sheet from NXP for the TDA19988... I really don't like working blind.. > I've fixed the i2c controller issues on -head so you can skip that > part from gonzo's patch. Cool, thanks for the help.... > I also see some GPIO pins on schematics (like GPIO0_19 and GPIO1_27 on > page 3) which may need to be set for the HDMI support and i did not > check the gonzo's code to verify if they are properly set. Yeh, GPIO1_27 is the one that enables the clock to the HDMI chip and when I was looking over his patch, I didn't see anything for enabling it... This is mentioned in the SRM... Looks like GPIO0_19 isn't necessary as that is the clock for CEC, and we don't need that till later (say use the TV remote as an input device)... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."