From owner-freebsd-arm@freebsd.org Mon Mar 28 19:35:45 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 3D2D6AE17D1 for ; Mon, 28 Mar 2016 19:35:45 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 2135D1A11; Mon, 28 Mar 2016 19:35:44 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from [208.184.220.60] (helo=r2d2.dolby.net) by id.bluezbox.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1akcwq-000AYC-V5; Mon, 28 Mar 2016 12:35:42 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: RPi 2 with 7-inch touchscreen. From: Oleksandr Tymoshenko In-Reply-To: <3995875D-D11B-426B-8D3F-8449631CFE71@FreeBSD.org> Date: Mon, 28 Mar 2016 12:28:20 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <3ACB45C6-44D4-4BB6-884E-B003F736DD1E@bluezbox.com> References: <8243E254-B30D-4C42-818C-3584D79ABC6B@FreeBSD.org> <3995875D-D11B-426B-8D3F-8449631CFE71@FreeBSD.org> To: Mark R V Murray X-Mailer: Apple Mail (2.3124) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: > On Mar 28, 2016, at 12:08 PM, Mark R V Murray wrote: > > (Sorry about the email flood in may last reply - the email client was misbehaving) > >> On 28 Mar 2016, at 19:48, Oleksandr Tymoshenko wrote: >> >> >> Try copying firmware files from raspbian image as this comment suggests: >> http://kernelnomicon.org/?p=540#comment-40186 >> >> Port may have older firmware, can't check right now. > > That worked, once I commented out the "start_x=1" :-) > > Thanks! :-) [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: github.com] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2016 19:35:45 -0000 > On Mar 28, 2016, at 12:08 PM, Mark R V Murray = wrote: >=20 > (Sorry about the email flood in may last reply - the email client was = misbehaving) >=20 >> On 28 Mar 2016, at 19:48, Oleksandr Tymoshenko = wrote: >>=20 >>=20 >> Try copying firmware files from raspbian image as this comment = suggests: >> http://kernelnomicon.org/?p=3D540#comment-40186 >>=20 >> Port may have older firmware, can't check right now. >=20 > That worked, once I commented out the "start_x=3D1" :-) >=20 > Thanks! :-) No problem :)=20 >>>> I also had touchscreen driver prototype working for it but can't = find it at the moment :( >>>> It's very simple busy read from memory window. Requires FDT = modification and >>>> interface to userland which FreeBSD does not have at the moment. >>>>=20 >>>=20 >>> That's next on my list :-) >>=20 >> I'll try to dig up the driver later today. If I haven't deleted it = during last "cleanup" that is :-/ >=20 > Yes please! https://people.freebsd.org/~gonzo/arm/bcm2835_ft5406.c It's not pretty. You can use it as a reference. It implements home-made=20= evdev-like API I used for testing with hacked-up version of tslib:=20 = https://github.com/gonzoua/experimental-freebsd-ports/tree/master/devel/ts= lib >=20 > Do you know how to make the USB keyboard work from the get-go? Mine = works, but only *after* boot, so I can't interact with the boot process. With u-boot from ports it's not possible. It has very basic USB support=20= which does not include SPLIT commands required to communicate with keyboard. There is Stephen Warren's version of u-boot, last time I checked it did support keyboard. But in order to make it work with=20 ubldr you'll need to change default configuration and add API support + some API fixes. If you don't want to go that way you have two options: - Use serial console to communicate with u-boot if you really need=20 interactive boot process. - Just put your custom logic to bootcmd in uEnv.txt if it's = once-configure run-always thing.=20=