From owner-freebsd-arm@freebsd.org Mon Jan 8 12:19:19 2018 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 06321E6883C for ; Mon, 8 Jan 2018 12:19:19 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0B17855F; Mon, 8 Jan 2018 12:19:17 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id e45a8726; Mon, 8 Jan 2018 13:19:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=gbplROJA7rdivKmdoPp/cC3d4mM=; b=ikXR7SUAK2UISOmrzQulbVRdlY5T MKnBhBnTEMY2hleV77k+Izn6cRvu+yLE8wdEwyr/Yk53/COXJUP7cJWgQebitHw3 /cd4qeE9hzJmHqm/KM9jzK6G9l2Gm45GInhVD/bjBuAr7ccsbCDNt1AF4QNZ0mKM tdiPKb6mc+a/RVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=BhPcy2klYA60k318zLrpkoxOPi72MPyNKuqK+bFlKSvGDzmh5ctOaAlb o0pc1PagxEXLi3hkpULKLwaSg/HYdVuUkyG8/iqJCcIysE2JZtkMNDbJ8VHn943z /tMGp2JY53G/dGzB8kXvJ4rDw8HIBhXdvwn+3VDVusO5FAA5SxM= Received: from arcadia (evadot.gandi.net [217.70.181.36]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 32c8f31a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 8 Jan 2018 13:19:15 +0100 (CET) Date: Mon, 8 Jan 2018 13:19:14 +0100 From: Emmanuel Vadot To: Adriaan de Groot Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD on the Pinebook Message-Id: <20180108131914.53117e4b3e61fbaed6793b5e@bidouilliste.com> In-Reply-To: <13327268.6xbMAFijLa@beastie.bionicmutton.org> References: <20180107211237.GA66684@server.rulingia.com> <13327268.6xbMAFijLa@beastie.bionicmutton.org> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 12:19:19 -0000 On Mon, 08 Jan 2018 11:49:08 +0100 Adriaan de Groot wrote: > On Sunday, 7 January 2018 22:12:37 CET Peter Jeremy wrote: > > Is any work being done to get FreeBSD running on the Pinebook? > > https://www.pine64.org/?page_id=3707 > > The hardware is pretty much interchangeable, except for the way the serial > port works over the audio jack. The Pinebook is roughly / basically the pine64 > board with some ports wired to the outside of the case. Linux images for the > Pinebook work just fine on the Pine64+ board after replacing the u-boot blocks > with Pine64+ versions thereof. Same for FreeBSD > I could borrow a Pinebook and check that the Pine64+ FreeBSD image boots on it > just to be sure; I've got an audio-to-serial-pinout cable kicking around for > this purpose, but .. > > > https://wiki.freebsd.org/FreeBSD/arm/Allwinner shows the A64 and Pine64 > > are supported but there's no framebuffer support listed so I presume it > > doesn't work (at least usefully) on the Pinebook. > > . without video output, there's not much use for the whole thing. Note > there's just been a new binary-blob MALI 400 driver published on the Pine > wiki, who knows what effect that might have. (I haven't tried latest Linux > images with that new driver, getting the DRM blob to play nice with other > kernels is quite an exercise). It has nothing to do with MALI, MALI is the gpu (discrete GPU one could say) and even with MALI support (which we don't have and, I think, never will) we still need display engine driver (which drives the framebuffer, hdmi, lcd etc ...) > Basically I'd suggest getting the Pine64 to support video first, and then > worrying about devices using it -- something similar applies to the Rock64 > mentioned here recently (although that's a MALI 450 GPU, which I think FreeBSD > supports on the ODROID C2+ .. gah, too many hardware variants running through > my head, I'll get coffee first). > > [ade] I have efifb mostly working on Pine64 but our pmap code needs some love. -- Emmanuel Vadot