From nobody Tue Apr 04 08:16:53 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PrLQm0lYtz43Bp7 for ; Tue, 4 Apr 2023 08:24:32 +0000 (UTC) (envelope-from dsl@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PrLQm0GlDz3ktR; Tue, 4 Apr 2023 08:24:32 +0000 (UTC) (envelope-from dsl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1680596672; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CKut0TCajT2ORn+jKgepyazQew0Oq0RWISjYL8WILtg=; b=B2v8J7bfmxy3BmPdDlVBTr/Q6y5PnJuKxnLVJC+N60nrYWhnoOEwpgZlOd3xVbpqxuH8c8 PCS7IbuVNxCXKN4+BDNoR0a3wRHFRBacKKq3qCsxe+SuUKrU1W65YDZ4ESh8Fs5bsQup/K XnaceWjUsdGPalYuNq+v8dfFPxFNZYkcZ7dqscHH62ZqBqHQhZX4V2eUKTHaoA/fIoEFPn TA0QswDZQ/NTXENhMxhtvcF8OlwrjUla8OVthLUQAAhX2cOgohf89coeiflXwqA1moSxai lhKVe/YHHZ20xp0G2fUjWUXU8tvH42N3F5tYABZqkkfTH15++4S7jfp9fd6bsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1680596672; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CKut0TCajT2ORn+jKgepyazQew0Oq0RWISjYL8WILtg=; b=oO1JtT7GL+S2DIvO5Uygzg7956+3vHWVu9lagawacgo8/CbambG1edYbcLX8Q1nMOpUmZL IzblMbr1VaaOQzbU8Iepaa4cOF4+N37qQoMRdHHz4WeHoc4kSgrYRN7PVTF3lyIJbMsP/K frkgswky+T1zl6U127qwt9X8c2L1y61d/skwaEEjbGIKBw/YslH3nWkzzYl7IV5BAUO+XZ hyN6Ao+YbxCuKUxq+jpv+8B/kZhIJVyqFGP6eTRp8PRfAPNpNcDKDW9HEl+H15zQC8IXDQ zcBx9hAUq8c4xdviG2cFyHwUD19U/YazJbxkJU91q2U68b4q5uFZf56GYV1xQQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1680596672; a=rsa-sha256; cv=none; b=EBecUAT+siU5b5WSegK2DJOgDEYc6Z5/qsoC/VP4HaxG7U+N59RgpsifxVzt6ZgS09vlKU ZuGZKp2Pkxn145/L/Tn6vrrK+ZQ6eWtEY4FwzgfD6c/XxCZXhNUBx9HIiieqyBq8AW7fGh yzJ7aVlgPB7VHlfTqZfvS57Or2iMp5ASr81Qbje7LG0neDbfFLh5I5RFLLtgooqSXiOC+P CTCg23B/rWkgfWAg52MQYKUyid4xKgaDvnk22Q/TxpXE/lvfcnkB6Yq4NJ7ZLFpLHWwUjz k1uKqD/q/Uf0CcX7QdI+lYlgRK67cbJw62ZydTR6yfgXCWOU4YRzOcibmVEoww== Received: from localhost (unknown [193.164.254.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: dsl) by smtp.freebsd.org (Postfix) with ESMTPSA id 4PrLQl4VSbzsnw; Tue, 4 Apr 2023 08:24:31 +0000 (UTC) (envelope-from dsl@FreeBSD.org) References: <66fee230-24eb-c7d8-fa30-4530409c0f5c@nomadlogic.org> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Marcin Cieslak Cc: Pete Wright , freebsd-arm@freebsd.org Subject: Re: Pinephone Pro Date: Tue, 04 Apr 2023 10:16:53 +0200 In-reply-to: Message-ID: <86ttxwvyv7.fsf@peasant.tower.home> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-ThisMailContainsUnwantedMimeParts: N Marcin Cieslak writes: > [[S/MIME Signed Part:Undecided]] > On Fri, 31 Mar 2023, Pete Wright wrote: > >> So my question is - is the PINE64 the right image to use?=C2=A0 Anyone >> else tried this and able to share tweaks or docs they used to get >> things moving? > > What I would do is to take the device tree used by the Linux kernel > and try to see if something very similar can be used for FreeBSD, > first and foremost if the devices listed there are supported. > > Device trees used by FreeBSD kernel are in sys/contrib/device-tree > > https://cgit.freebsd.org/src/tree/sys/contrib/device-tree > > plus some overlays in https://cgit.freebsd.org/src/tree/sys/dts > > PinePhone Pro seems to be using a variant of RockChip RK3399 > so I'd do for the "rockchip" directory to looks for similar boards. > > Pine64 uses Allwinner processors, so this is unlikely to work. > > Some notes: > > https://wiki.pine64.org/wiki/PinePhone_Pro_Development > > Their fork of the Linux kernel: > > https://github.com/megous/linux > > This seems to be the device tree: > > https://github.com/megous/linux/blob/master/arch/arm64/boot/dts/rockchip/= rk3399-pinephone-pro.dts > > (it includes also other files, like rk3399.dtsi and rk3399-opp.dtsi, > both seems to be included in the FreeBSD kernel tree). > > Seems like they are still figuring things out for Linux as well, > so you are not alone in that effort. > > I think you should be prepared to build your own image. > With FreeBSD it is not very difficult (I find it easier than in > the Linux world). > > Marcin > > [[End of S/MIME Signed Part]] I'd take their device tree and try to boot GENERIC kernel for arm64 in order to get an idea which drivers are missing: # dmesg | grep "no driver" | grep -v "disabled" Pete, are you going to keep your findings somewhere? I don't have PinePhone Pro at the moment, but would like to follow and can support with customizing your kernel. Regards, Dmitry --=20 Open source software/hardware enthusiast hackaday.io/dsl | github.com/mcusim | patreon.com/salychev