From owner-freebsd-arm@freebsd.org Mon Oct 29 19:38:10 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C86FF10E8413 for ; Mon, 29 Oct 2018 19:38:10 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55F3D7F961 for ; Mon, 29 Oct 2018 19:38:09 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Mon, 29 Oct 2018 19:38:01 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id FB272CAF-CA5F-4A96-8324-AFAB8ED4D332.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Mon, 29 Oct 2018 19:38:01 +0000 Date: Mon, 29 Oct 2018 22:37:59 +0300 From: Greg V Subject: Re: MACCHIATObin To: freebsd-arm Cc: Marcin Wojtas , marklmi@yahoo.com Message-Id: <1540841879.1781.1@smtp.migadu.com> In-Reply-To: References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=Rr/9xfo4P5dIM6HH++Zi2FMQEpCoNMVYBSZDvUW9C7s=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=cC0UeAi4BwyavGG9y5vqXQxfjEgLmfEd6cbsrYGsdT/qzGo5jq4T/wB+hd1wajuW70ZevXPvAMDfzmT7qqJvMX2jkLvVAJxso2qCkPC25FZgCbwMyNGmXVe5jrBwWj7z/ia7vnHBtHJ5zMJJ+pncONn1/v63/QLbKy+JffoPWuc= X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2018 19:38:11 -0000 On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas wrote: > sob., 18 sie 2018 o 08:43 Marcin Wojtas napisa=C5=82(a)= : >>=20 >> sob., 18 sie 2018 o 01:10 Jim Thompson =20 >> napisa=C5=82(a): >> > >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm=20 >> wrote: >> > >> > > Marcin Wojtas mw at semihalf.com wrote on >> > > Fri May 11 07:55:40 UTC 2018 : >> > > >> > >> Short status of the support - last year we enabled most of the >> > >> platform functionalities (core support, USB, AHCI, RTC). Three=20 >> big >> > >> items remained left: >> > >> - PCIE root complex (this should work soon with the work done=20 >> for >> > >> another SoC, not merged yet) >> > >> - Network PPv2 >> > >> - Xenon SD/MMC controller >> > > >> > > >> > > I noticed a check in that deals with that "Xenon" >> > > SD/MMC controller: >> > > >> > > Author: loos >> > > Date: Tue Aug 14 16:33:30 2018 >> > > New Revision: 337772 >> > > URL: >> > > https://svnweb.freebsd.org/changeset/base/337772 >>=20 [=E2=80=A6] >> > > >> > > But I've not noticed check-ins for the other of the "big >> > > items" going by. (Though they may have.) >> > > >> > > Care to comment-on/update-the actual status for the >> > > Macchiato.bin(s)? >> > >> > >> > tl;dr: It=E2=80=99s not =E2=80=98there=E2=80=99 yet. >> > >> > Specifics: >> > >> > - loos@ has done a lot of work to get the espresso.bin working,=20 >> and some of this carries over to the 8k/7k. >> > - We have another internal developer working on an EIP-97 driver=20 >> for crypto offload. This should be a foundation for the EIP-197 in=20 >> the 8K. >> > - I know manu@is working on pin controllers and clocks specific=20 >> to Machiatto.bin (80x0/70x0). >> > - Getting the NICs, PCIe, etc working still remains to be done. >> > >>=20 >> About the latter - the NIC is pretty complex, however we (Semihalf) >> have really huge experience with all its support implementations and >> the platform itself. I'll put it straightforward - it's only a=20 >> matter >> of development funding, if it's guaranteed, we will do it with >> pleasure :) As well as the NIC support (DW Synopsys driver for DT=20 >> and >> verify/improve on pcie-host-generic with ACPI). >=20 > "As well as PCIE support..." of course. >=20 > Marcin Hi, I've noticed that people successfully use ACPI-PCIe on the MACCHIATObin=20 with Linux, so=E2=80=A6 has anyone tested FreeBSD pcie-host-generic there? I'm considering buying a MACCHIATObin board to test my drm-next build=20 for aarch64 ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd like to=20 first know if PCIe actually works :) Also, about the NIC =E2=80=94 is the 1GbE port attached to the same=20 new/complex NIC as the 10GbE ports? = From owner-freebsd-arm@freebsd.org Mon Oct 29 19:53:41 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A53010E8925 for ; Mon, 29 Oct 2018 19:53:41 +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 D69EA800C2 for ; Mon, 29 Oct 2018 19:53:40 +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 87e72d5a; Mon, 29 Oct 2018 20:46:58 +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=Z9VcV4PhUw4tDlEYJc2tYR9pEi0=; b=Ru/j0jkMv7DMxSWod2Hvt0+Z6K9E hSdLw1RTVTzyJrghaXJQSvwo4DYFFMp+AOZspFWxs6w0IIqh4Y64TnBHWnxoedtK yC/xXlLYEcVKU1KP1XX8LksfR0wI3h/iBNnnER1oi0YB9EOsDzfwKmoXYVhEB3e1 f9tlnUxm3ZGUaBE= 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=GMiLHf2C2uXEa1XDry0Y2Q8Fl+4XsrpaktMcvembruNJZjWdlFJgao2D xODKkbhyWEoS/cRHGdu9DZw4dNTx3k5o9XjwlPyS2FOLQ1tNfdvj9rtv9aU+xL/T RhM7Ev+y7oy922sp0CbvgK9+YzJNlEaUCPQKkSEKJU/XfaZJWqg= Received: from knuckles.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 995c5315 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 29 Oct 2018 20:46:58 +0100 (CET) Date: Mon, 29 Oct 2018 20:46:55 +0100 From: Emmanuel Vadot To: Greg V Cc: freebsd-arm , Marcin Wojtas Subject: Re: MACCHIATObin Message-Id: <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> In-Reply-To: <1540841879.1781.1@smtp.migadu.com> References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> <1540841879.1781.1@smtp.migadu.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2018 19:53:41 -0000 On Mon, 29 Oct 2018 22:37:59 +0300 Greg V wrote: >=20 >=20 > On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas wrote: > > sob., 18 sie 2018 o 08:43 Marcin Wojtas napisa?(a): > >>=20 > >> sob., 18 sie 2018 o 01:10 Jim Thompson =20 > >> napisa?(a): > >> > > >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm=20 > >> wrote: > >> > > >> > > Marcin Wojtas mw at semihalf.com wrote on > >> > > Fri May 11 07:55:40 UTC 2018 : > >> > > > >> > >> Short status of the support - last year we enabled most of the > >> > >> platform functionalities (core support, USB, AHCI, RTC). Three=20 > >> big > >> > >> items remained left: > >> > >> - PCIE root complex (this should work soon with the work done=20 > >> for > >> > >> another SoC, not merged yet) > >> > >> - Network PPv2 > >> > >> - Xenon SD/MMC controller > >> > > > >> > > > >> > > I noticed a check in that deals with that "Xenon" > >> > > SD/MMC controller: > >> > > > >> > > Author: loos > >> > > Date: Tue Aug 14 16:33:30 2018 > >> > > New Revision: 337772 > >> > > URL: > >> > > https://svnweb.freebsd.org/changeset/base/337772 > >>=20 > [?] > >> > > > >> > > But I've not noticed check-ins for the other of the "big > >> > > items" going by. (Though they may have.) > >> > > > >> > > Care to comment-on/update-the actual status for the > >> > > Macchiato.bin(s)? > >> > > >> > > >> > tl;dr: It?s not ?there? yet. > >> > > >> > Specifics: > >> > > >> > - loos@ has done a lot of work to get the espresso.bin working,=20 > >> and some of this carries over to the 8k/7k. > >> > - We have another internal developer working on an EIP-97 driver=20 > >> for crypto offload. This should be a foundation for the EIP-197 in=20 > >> the 8K. > >> > - I know manu@is working on pin controllers and clocks specific=20 > >> to Machiatto.bin (80x0/70x0). > >> > - Getting the NICs, PCIe, etc working still remains to be done. > >> > > >>=20 > >> About the latter - the NIC is pretty complex, however we (Semihalf) > >> have really huge experience with all its support implementations and > >> the platform itself. I'll put it straightforward - it's only a=20 > >> matter > >> of development funding, if it's guaranteed, we will do it with > >> pleasure :) As well as the NIC support (DW Synopsys driver for DT=20 > >> and > >> verify/improve on pcie-host-generic with ACPI). > >=20 > > "As well as PCIE support..." of course. > >=20 > > Marcin >=20 > Hi, >=20 > I've noticed that people successfully use ACPI-PCIe on the MACCHIATObin=20 > with Linux, > so? has anyone tested FreeBSD pcie-host-generic there? >=20 > I'm considering buying a MACCHIATObin board to test my drm-next build=20 > for aarch64 > ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd like to=20 > first know if PCIe actually works :) I'll will push support for mcbin soon in the tree (with PCI support). I don't know what ACPI-PCIe is exactly but I don't see how it can work without a dedicated driver for the armada 8K. > Also, about the NIC ? is the 1GbE port attached to the same=20 > new/complex NIC as the 10GbE ports? Yes. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --=20 Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 29 20:05:36 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59BF810E8B89 for ; Mon, 29 Oct 2018 20:05:36 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DAEA9805AD for ; Mon, 29 Oct 2018 20:05:35 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Mon, 29 Oct 2018 20:05:34 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 14671E19-642E-43BB-BEDF-2B479C899ACE.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Mon, 29 Oct 2018 20:05:33 +0000 Date: Mon, 29 Oct 2018 23:05:31 +0300 From: Greg V Subject: Re: MACCHIATObin To: Emmanuel Vadot Cc: freebsd-arm , Marcin Wojtas Message-Id: <1540843531.1781.2@smtp.migadu.com> In-Reply-To: <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> <1540841879.1781.1@smtp.migadu.com> <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=cbvVRow0SwjmCz9H4ZGV772I0JfrH20GrFDWgH+EX6A=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=AJaDq+GyBt0KEibl860sLXgHDP3h2peurcGv5QCw2wrHGexEg0z1Er1giv/Zn0V7dJhuskglnsC06y+zT8zD0YJ9wDYXFiNcfCCeVbmpVfGqhMWvLMxqXSS2deLmEiwwbadsTzUwa727wwp9fVTDazaoh9hDyZq61JHV0cbANYQ= X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2018 20:05:36 -0000 On Mon, Oct 29, 2018 at 10:46 PM, Emmanuel Vadot=20 wrote: > On Mon, 29 Oct 2018 22:37:59 +0300 > Greg V wrote: >=20 >>=20 >>=20 >> On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas =20 >> wrote: >> > sob., 18 sie 2018 o 08:43 Marcin Wojtas =20 >> napisa?(a): >> >> >> >> sob., 18 sie 2018 o 01:10 Jim Thompson >> >> napisa?(a): >> >> > >> >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm >> >> wrote: >> >> > >> >> > > Marcin Wojtas mw at semihalf.com wrote on >> >> > > Fri May 11 07:55:40 UTC 2018 : >> >> > > >> >> > >> Short status of the support - last year we enabled most of=20 >> the >> >> > >> platform functionalities (core support, USB, AHCI, RTC).=20 >> Three >> >> big >> >> > >> items remained left: >> >> > >> - PCIE root complex (this should work soon with the work=20 >> done >> >> for >> >> > >> another SoC, not merged yet) >> >> > >> - Network PPv2 >> >> > >> - Xenon SD/MMC controller >> >> > > >> >> > > >> >> > > I noticed a check in that deals with that "Xenon" >> >> > > SD/MMC controller: >> >> > > >> >> > > Author: loos >> >> > > Date: Tue Aug 14 16:33:30 2018 >> >> > > New Revision: 337772 >> >> > > URL: >> >> > > https://svnweb.freebsd.org/changeset/base/337772 >> >> >> [?] >> >> > > >> >> > > But I've not noticed check-ins for the other of the "big >> >> > > items" going by. (Though they may have.) >> >> > > >> >> > > Care to comment-on/update-the actual status for the >> >> > > Macchiato.bin(s)? >> >> > >> >> > >> >> > tl;dr: It?s not ?there? yet. >> >> > >> >> > Specifics: >> >> > >> >> > - loos@ has done a lot of work to get the espresso.bin=20 >> working, >> >> and some of this carries over to the 8k/7k. >> >> > - We have another internal developer working on an EIP-97=20 >> driver >> >> for crypto offload. This should be a foundation for the EIP-197=20 >> in >> >> the 8K. >> >> > - I know manu@is working on pin controllers and clocks=20 >> specific >> >> to Machiatto.bin (80x0/70x0). >> >> > - Getting the NICs, PCIe, etc working still remains to be=20 >> done. >> >> > >> >> >> >> About the latter - the NIC is pretty complex, however we=20 >> (Semihalf) >> >> have really huge experience with all its support=20 >> implementations and >> >> the platform itself. I'll put it straightforward - it's only a >> >> matter >> >> of development funding, if it's guaranteed, we will do it with >> >> pleasure :) As well as the NIC support (DW Synopsys driver for=20 >> DT >> >> and >> >> verify/improve on pcie-host-generic with ACPI). >> > >> > "As well as PCIE support..." of course. >> > >> > Marcin >>=20 >> Hi, >>=20 >> I've noticed that people successfully use ACPI-PCIe on the=20 >> MACCHIATObin >> with Linux, >> so? has anyone tested FreeBSD pcie-host-generic there? >>=20 >> I'm considering buying a MACCHIATObin board to test my drm-next=20 >> build >> for aarch64 >> ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd like=20 >> to >> first know if PCIe actually works :) >=20 > I'll will push support for mcbin soon in the tree (with PCI support). > I don't know what ACPI-PCIe is exactly but I don't see how it can=20 > work > without a dedicated driver for the armada 8K. dev/pci/pci_host_generic_acpi.c =97 generic ECAM PCIe driver. I think ThunderX2 uses it (2018 Cavium copyright in the file), probably=20 Ampere eMAG (haven't seen anything about that here, but the vendor=20 lists FreeBSD in their OS compatibility list), should be possible to=20 use on the SoftIron Overdrives (NetBSD just added ACPI/aarch64 and they=20 tested on the Overdrive:=20 https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4526 =97 but all=20 FreeBSD+SoftIron dmesgs on dmesgd.nycbug so far are in FDT mode, not=20 ACPI)=85 And the EDK2 firmware for the Armada8k does have an ACPI mode=85 = From owner-freebsd-arm@freebsd.org Mon Oct 29 21:48:41 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 192D610EB2CF for ; Mon, 29 Oct 2018 21:48:41 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A307850DE for ; Mon, 29 Oct 2018 21:48:40 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-it1-x134.google.com with SMTP id t4-v6so3074881itf.1 for ; Mon, 29 Oct 2018 14:48:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Mib87tbYKQMcB/2NmnJnrSWNKlSQH4Kufw/GO6sFfto=; b=IQY4oP2Go2JbSNIyAabRBF+5OMfNnkxgf2R5/uSpBQRbr67OtWZYA2TLC5MEdI/oDj MnmgALuRjeSi2mOp4+pCcYBPS/a23RWCEBJkZ+9TG8sfF+Rg27HZ7n+ynvlLBidL4bJS lksbntHT61zVfrE9oTfg6xKHZiwAhVPufRI5ee0eqj7JVikTQCGlDhq5lU9ZFGb5FJfP wNd2T5n93UYbC3PDKAhTTla65iam1GEu0XLBXr3tGuJ3Y1PhYgGGku4i+B8MRiXjEiyB xwfst1liAFkLwybp1QlZO+2l+ZdoNGoP/WAsoD+JoboiA9sEnUmZWBkktYSOMMLKiwrv yCog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Mib87tbYKQMcB/2NmnJnrSWNKlSQH4Kufw/GO6sFfto=; b=tJEa/BggNOC2HyRGFKgv2zifozEIX95D2sFgRs3x7LjxMNLGY5+F9Iit9r2hUTmWjv OtnmkFz2mEpJv35OTspmDSCjEkxuVMTmG9OJmbaiP9f7+2giNojbCO4rZOOMdXpp1dx2 xnQL17tI/NnKZUkyBa2i5QMXrhLulX8b7VVwoDrKdhHwmi0rpC/P6kSvBqct//VwR/e9 eXn/h7uHpBNvAE2rBIikUKbZOlhOwMGqYffjyAusWfep7riWgV8XbQOGw5TtDhnnLfUe l9ygqAqgxAl6ZawIDWddIliwWe14yLKM9uQT2yO/ZBAgFWzQBMWY69Z6A/szD46pFPWI YqLA== X-Gm-Message-State: AGRZ1gIoGrbbDkCy6Ecbuqwipv4owSnwRWd+gg4vZmZ+qc0pghZm9Evm GWHejaBCVcohylzZtyo3vBW/dAld7CTSnVPCFhQoX0ClpJc= X-Google-Smtp-Source: AJdET5dAsqLxT+jjTSVeXLgTMFPTMXNeO07NJta2sYgGAf3kKryRbDZcnzHjkluVhDbeStJAzgEHIAhKWYpq8gFccJQ= X-Received: by 2002:a24:c647:: with SMTP id j68-v6mr11522542itg.138.1540849719485; Mon, 29 Oct 2018 14:48:39 -0700 (PDT) MIME-Version: 1.0 References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> <1540841879.1781.1@smtp.migadu.com> <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> <1540843531.1781.2@smtp.migadu.com> In-Reply-To: <1540843531.1781.2@smtp.migadu.com> From: Marcin Wojtas Date: Mon, 29 Oct 2018 22:48:27 +0100 Message-ID: Subject: Re: MACCHIATObin To: greg@unrelenting.technology Cc: Emmanuel Vadot , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2018 21:48:41 -0000 Hi, pon., 29 pa=C5=BA 2018 o 21:05 Greg V napisa= =C5=82(a): > > > > On Mon, Oct 29, 2018 at 10:46 PM, Emmanuel Vadot > wrote: > > On Mon, 29 Oct 2018 22:37:59 +0300 > > Greg V wrote: > > > >> > >> > >> On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas > >> wrote: > >> > sob., 18 sie 2018 o 08:43 Marcin Wojtas > >> napisa?(a): > >> >> > >> >> sob., 18 sie 2018 o 01:10 Jim Thompson > >> >> napisa?(a): > >> >> > > >> >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm > >> >> wrote: > >> >> > > >> >> > > Marcin Wojtas mw at semihalf.com wrote on > >> >> > > Fri May 11 07:55:40 UTC 2018 : > >> >> > > > >> >> > >> Short status of the support - last year we enabled most of > >> the > >> >> > >> platform functionalities (core support, USB, AHCI, RTC). > >> Three > >> >> big > >> >> > >> items remained left: > >> >> > >> - PCIE root complex (this should work soon with the work > >> done > >> >> for > >> >> > >> another SoC, not merged yet) > >> >> > >> - Network PPv2 > >> >> > >> - Xenon SD/MMC controller > >> >> > > > >> >> > > > >> >> > > I noticed a check in that deals with that "Xenon" > >> >> > > SD/MMC controller: > >> >> > > > >> >> > > Author: loos > >> >> > > Date: Tue Aug 14 16:33:30 2018 > >> >> > > New Revision: 337772 > >> >> > > URL: > >> >> > > https://svnweb.freebsd.org/changeset/base/337772 > >> >> > >> [?] > >> >> > > > >> >> > > But I've not noticed check-ins for the other of the "big > >> >> > > items" going by. (Though they may have.) > >> >> > > > >> >> > > Care to comment-on/update-the actual status for the > >> >> > > Macchiato.bin(s)? > >> >> > > >> >> > > >> >> > tl;dr: It?s not ?there? yet. > >> >> > > >> >> > Specifics: > >> >> > > >> >> > - loos@ has done a lot of work to get the espresso.bin > >> working, > >> >> and some of this carries over to the 8k/7k. > >> >> > - We have another internal developer working on an EIP-97 > >> driver > >> >> for crypto offload. This should be a foundation for the EIP-197 > >> in > >> >> the 8K. > >> >> > - I know manu@is working on pin controllers and clocks > >> specific > >> >> to Machiatto.bin (80x0/70x0). > >> >> > - Getting the NICs, PCIe, etc working still remains to be > >> done. > >> >> > > >> >> > >> >> About the latter - the NIC is pretty complex, however we > >> (Semihalf) > >> >> have really huge experience with all its support > >> implementations and > >> >> the platform itself. I'll put it straightforward - it's only a > >> >> matter > >> >> of development funding, if it's guaranteed, we will do it with > >> >> pleasure :) As well as the NIC support (DW Synopsys driver for > >> DT > >> >> and > >> >> verify/improve on pcie-host-generic with ACPI). > >> > > >> > "As well as PCIE support..." of course. > >> > > >> > Marcin > >> > >> Hi, > >> > >> I've noticed that people successfully use ACPI-PCIe on the > >> MACCHIATObin > >> with Linux, > >> so? has anyone tested FreeBSD pcie-host-generic there? > >> > >> I'm considering buying a MACCHIATObin board to test my drm-next > >> build > >> for aarch64 > >> ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd like > >> to > >> first know if PCIe actually works :) > > > > I'll will push support for mcbin soon in the tree (with PCI support). > > I don't know what ACPI-PCIe is exactly but I don't see how it can > > work > > without a dedicated driver for the armada 8K. > > dev/pci/pci_host_generic_acpi.c =E2=80=94 generic ECAM PCIe driver. > > I think ThunderX2 uses it (2018 Cavium copyright in the file), probably > Ampere eMAG (haven't seen anything about that here, but the vendor > lists FreeBSD in their OS compatibility list), should be possible to > use on the SoftIron Overdrives (NetBSD just added ACPI/aarch64 and they > tested on the Overdrive: > https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4526 =E2=80=94 but all > FreeBSD+SoftIron dmesgs on dmesgd.nycbug so far are in FDT mode, not > ACPI)=E2=80=A6 > > And the EDK2 firmware for the Armada8k does have an ACPI mode=E2=80=A6 > I confirm - thanks to the initial configuration in UEFI, ACPI tables support PCI, which OS can use with the pure ECAM pci-host-generic driver. Here's also the latest Centos7 bootlog, where you can see it: https://pastebin.com/Aa2NvDnM Marcin From owner-freebsd-arm@freebsd.org Tue Oct 30 22:46:14 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D3E3103629F for ; Tue, 30 Oct 2018 22:46:14 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B08E77DFAD for ; Tue, 30 Oct 2018 22:46:13 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Tue, 30 Oct 2018 22:46:05 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id E3FE5920-9E20-47F7-A0FD-484681690126.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Tue, 30 Oct 2018 22:46:05 +0000 Date: Wed, 31 Oct 2018 01:46:00 +0300 From: Greg V Subject: Re: MACCHIATObin To: Marcin Wojtas Cc: Emmanuel Vadot , freebsd-arm Message-Id: <1540939560.20404.0@smtp.migadu.com> In-Reply-To: References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> <1540841879.1781.1@smtp.migadu.com> <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> <1540843531.1781.2@smtp.migadu.com> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=w3EzRUfH4IGARrnlWaHreAnBvSeK9HRSY/KdTJwipmo=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=N24IY/pxl81KW5pAHNU3DfV4wsPnyA5lKZlGcRT5Rz3USD6ZQFQrb9FRVwwvjRiPQ9+6WveusrUcindxubcyvEcvAIHvWuPRhn5Y7E5zDTTKfWt83o2PFHTmear6SIT3K+EiZkF6E2eo5ZZ5otzDDgmh67XHWJpU64x8/0mHPuE= X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2018 22:46:14 -0000 On Tue, Oct 30, 2018 at 12:48 AM, Marcin Wojtas wrote: > Hi, >=20 > pon., 29 pa=C5=BA 2018 o 21:05 Greg V =20 > napisa=C5=82(a): >>=20 >>=20 >>=20 >> On Mon, Oct 29, 2018 at 10:46 PM, Emmanuel Vadot >> wrote: >> > On Mon, 29 Oct 2018 22:37:59 +0300 >> > Greg V wrote: >> > >> >> >> >> >> >> On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas=20 >> >> >> wrote: >> >> > sob., 18 sie 2018 o 08:43 Marcin Wojtas >> >> napisa?(a): >> >> >> >> >> >> sob., 18 sie 2018 o 01:10 Jim Thompson >> >> >> napisa?(a): >> >> >> > >> >> >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm >> >> >> wrote: >> >> >> > >> >> >> > > Marcin Wojtas mw at semihalf.com wrote on >> >> >> > > Fri May 11 07:55:40 UTC 2018 : >> >> >> > > >> >> >> > >> Short status of the support - last year we enabled=20 >> most of >> >> the >> >> >> > >> platform functionalities (core support, USB, AHCI,=20 >> RTC). >> >> Three >> >> >> big >> >> >> > >> items remained left: >> >> >> > >> - PCIE root complex (this should work soon with the=20 >> work >> >> done >> >> >> for >> >> >> > >> another SoC, not merged yet) >> >> >> > >> - Network PPv2 >> >> >> > >> - Xenon SD/MMC controller >> >> >> > > >> >> >> > > >> >> >> > > I noticed a check in that deals with that "Xenon" >> >> >> > > SD/MMC controller: >> >> >> > > >> >> >> > > Author: loos >> >> >> > > Date: Tue Aug 14 16:33:30 2018 >> >> >> > > New Revision: 337772 >> >> >> > > URL: >> >> >> > > https://svnweb.freebsd.org/changeset/base/337772 >> >> >> >> >> [?] >> >> >> > > >> >> >> > > But I've not noticed check-ins for the other of the "big >> >> >> > > items" going by. (Though they may have.) >> >> >> > > >> >> >> > > Care to comment-on/update-the actual status for the >> >> >> > > Macchiato.bin(s)? >> >> >> > >> >> >> > >> >> >> > tl;dr: It?s not ?there? yet. >> >> >> > >> >> >> > Specifics: >> >> >> > >> >> >> > - loos@ has done a lot of work to get the espresso.bin >> >> working, >> >> >> and some of this carries over to the 8k/7k. >> >> >> > - We have another internal developer working on an EIP-97 >> >> driver >> >> >> for crypto offload. This should be a foundation for the=20 >> EIP-197 >> >> in >> >> >> the 8K. >> >> >> > - I know manu@is working on pin controllers and clocks >> >> specific >> >> >> to Machiatto.bin (80x0/70x0). >> >> >> > - Getting the NICs, PCIe, etc working still remains to be >> >> done. >> >> >> > >> >> >> >> >> >> About the latter - the NIC is pretty complex, however we >> >> (Semihalf) >> >> >> have really huge experience with all its support >> >> implementations and >> >> >> the platform itself. I'll put it straightforward - it's=20 >> only a >> >> >> matter >> >> >> of development funding, if it's guaranteed, we will do it=20 >> with >> >> >> pleasure :) As well as the NIC support (DW Synopsys driver=20 >> for >> >> DT >> >> >> and >> >> >> verify/improve on pcie-host-generic with ACPI). >> >> > >> >> > "As well as PCIE support..." of course. >> >> > >> >> > Marcin >> >> >> >> Hi, >> >> >> >> I've noticed that people successfully use ACPI-PCIe on the >> >> MACCHIATObin >> >> with Linux, >> >> so? has anyone tested FreeBSD pcie-host-generic there? >> >> >> >> I'm considering buying a MACCHIATObin board to test my drm-next >> >> build >> >> for aarch64 >> >> ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd=20 >> like >> >> to >> >> first know if PCIe actually works :) >> > >> > I'll will push support for mcbin soon in the tree (with PCI=20 >> support). >> > I don't know what ACPI-PCIe is exactly but I don't see how it can >> > work >> > without a dedicated driver for the armada 8K. >>=20 >> dev/pci/pci_host_generic_acpi.c =E2=80=94 generic ECAM PCIe driver. >>=20 >> I think ThunderX2 uses it (2018 Cavium copyright in the file),=20 >> probably >> Ampere eMAG (haven't seen anything about that here, but the vendor >> lists FreeBSD in their OS compatibility list), should be possible to >> use on the SoftIron Overdrives (NetBSD just added ACPI/aarch64 and=20 >> they >> tested on the Overdrive: >> https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4526 =E2=80=94 but a= ll >> FreeBSD+SoftIron dmesgs on dmesgd.nycbug so far are in FDT mode, not >> ACPI)=E2=80=A6 >>=20 >> And the EDK2 firmware for the Armada8k does have an ACPI mode=E2=80=A6 >>=20 >=20 > I confirm - thanks to the initial configuration in UEFI, ACPI tables > support PCI, which OS can use with the pure ECAM pci-host-generic > driver. Here's also the latest Centos7 bootlog, where you can see it: > https://pastebin.com/Aa2NvDnM >=20 > Marcin So you haven't tried booting *FreeBSD* in ACPI mode on the 8k yet? Would be great to see a FreeBSD dmesg from that configuration on=20 https://dmesgd.nycbug.org :) = From owner-freebsd-arm@freebsd.org Thu Nov 1 01:30:08 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F103F10DA693 for ; Thu, 1 Nov 2018 01:30:07 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85E217622F for ; Thu, 1 Nov 2018 01:30:07 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-io1-xd2b.google.com with SMTP id d80-v6so11147752iof.1 for ; Wed, 31 Oct 2018 18:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=s9KN1mDIMCyko1i26rj/SKPVcyRf44Cvf+euX9t3Mdc=; b=Iv0NlxOm0u0w5oshog0l6PdhMosQq7kKf7oHhh1HSKH7yRTKvhs3IqhYedBe7swAWV L1MlOeU9ghVvYR2PkE6bh4VF3csSDbD5/AztCr4k7jTva5+uKJztSg09vdEBVNziVqLK DCQjG1DUKrjMEFuJWuIhuqx/p+pFEt5Ys1OhtjfPdDatavxIW62WwYgzFZWGf+eAEAGJ KGChVU6zlLgZqLjX0bXJahuxm410vnIytQ8ufOFyK2rtUFAaPikNnMeRZWOjZGDzesIK 4z5y+Wr2/FPhAeEomB8i8Kh27pKVrPyDWTnOXUYiKkPXuJ7qiN+668b51LraM9HFK6q8 iFjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=s9KN1mDIMCyko1i26rj/SKPVcyRf44Cvf+euX9t3Mdc=; b=q5HQ4yt/mWJFuSc3ilqS0/MBPwesueu/ycmyY7z10yULQUZaNo4M/XujOFibBZW3lT 9Ams87unwEbo3jEJI4Sbfys3Hsz3L+rxfm9bOHxmhqI1to/j5N90o5EL0Ot22UHHXDmt wrmY9Lydmc/eMelxv7oujdXE6S1KgmjvxUl0/u1MmSoCYEyka4HwPqtqfqKIXpgMYqum QS2eVfGH9NucJAkSknnKv1r2vrZT9KPPGO+KuUkKjILMQtfclT79RG0rni1qd3Pjnunn T7kamDFIwr+jwEbFz+xqR1WUfur2RCNurJ3c0Gcld0rliIjE0iz33L79MufZ2xgUxVG+ ph3A== X-Gm-Message-State: AGRZ1gJsH7lfd5u6MhubMcEOFGQ/pBBMdsCA9F/BHMaVC1QhiyWnCmrq NoatrfhZV+MgEXu6L39xj3P/ukrcJ5OTx1xJXssdbIIx X-Google-Smtp-Source: AJdET5edA+ENn3PLM5goBLkkOikC0sIc5+ErRJb8C+kfdQy617HPc4bzrhscr85102xhfL4XhH0e4b1G2kSqTQoMDZw= X-Received: by 2002:a6b:8ec9:: with SMTP id q192-v6mr3743785iod.248.1541035806770; Wed, 31 Oct 2018 18:30:06 -0700 (PDT) MIME-Version: 1.0 References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> <1540841879.1781.1@smtp.migadu.com> <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> <1540843531.1781.2@smtp.migadu.com> <1540939560.20404.0@smtp.migadu.com> In-Reply-To: From: Marcin Wojtas Date: Thu, 1 Nov 2018 02:29:56 +0100 Message-ID: Subject: Re: MACCHIATObin To: greg@unrelenting.technology Cc: Emmanuel Vadot , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 01:30:08 -0000 czw., 1 lis 2018 o 02:27 Marcin Wojtas napisa=C5=82(a): > > wt., 30 pa=C5=BA 2018 o 23:46 Greg V napisa= =C5=82(a): > > > > > > > > On Tue, Oct 30, 2018 at 12:48 AM, Marcin Wojtas wrote= : > > > Hi, > > > > > > pon., 29 pa=C5=BA 2018 o 21:05 Greg V > > > napisa=C5=82(a): > > >> > > >> > > >> > > >> On Mon, Oct 29, 2018 at 10:46 PM, Emmanuel Vadot > > >> wrote: > > >> > On Mon, 29 Oct 2018 22:37:59 +0300 > > >> > Greg V wrote: > > >> > > > >> >> > > >> >> > > >> >> On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas > > >> > > >> >> wrote: > > >> >> > sob., 18 sie 2018 o 08:43 Marcin Wojtas > > >> >> napisa?(a): > > >> >> >> > > >> >> >> sob., 18 sie 2018 o 01:10 Jim Thompson > > >> >> >> napisa?(a): > > >> >> >> > > > >> >> >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm > > >> >> >> wrote: > > >> >> >> > > > >> >> >> > > Marcin Wojtas mw at semihalf.com wrote on > > >> >> >> > > Fri May 11 07:55:40 UTC 2018 : > > >> >> >> > > > > >> >> >> > >> Short status of the support - last year we enabled > > >> most of > > >> >> the > > >> >> >> > >> platform functionalities (core support, USB, AHCI, > > >> RTC). > > >> >> Three > > >> >> >> big > > >> >> >> > >> items remained left: > > >> >> >> > >> - PCIE root complex (this should work soon with the > > >> work > > >> >> done > > >> >> >> for > > >> >> >> > >> another SoC, not merged yet) > > >> >> >> > >> - Network PPv2 > > >> >> >> > >> - Xenon SD/MMC controller > > >> >> >> > > > > >> >> >> > > > > >> >> >> > > I noticed a check in that deals with that "Xenon" > > >> >> >> > > SD/MMC controller: > > >> >> >> > > > > >> >> >> > > Author: loos > > >> >> >> > > Date: Tue Aug 14 16:33:30 2018 > > >> >> >> > > New Revision: 337772 > > >> >> >> > > URL: > > >> >> >> > > https://svnweb.freebsd.org/changeset/base/337772 > > >> >> >> > > >> >> [?] > > >> >> >> > > > > >> >> >> > > But I've not noticed check-ins for the other of the "bi= g > > >> >> >> > > items" going by. (Though they may have.) > > >> >> >> > > > > >> >> >> > > Care to comment-on/update-the actual status for the > > >> >> >> > > Macchiato.bin(s)? > > >> >> >> > > > >> >> >> > > > >> >> >> > tl;dr: It?s not ?there? yet. > > >> >> >> > > > >> >> >> > Specifics: > > >> >> >> > > > >> >> >> > - loos@ has done a lot of work to get the espresso.bin > > >> >> working, > > >> >> >> and some of this carries over to the 8k/7k. > > >> >> >> > - We have another internal developer working on an EIP-97 > > >> >> driver > > >> >> >> for crypto offload. This should be a foundation for the > > >> EIP-197 > > >> >> in > > >> >> >> the 8K. > > >> >> >> > - I know manu@is working on pin controllers and clocks > > >> >> specific > > >> >> >> to Machiatto.bin (80x0/70x0). > > >> >> >> > - Getting the NICs, PCIe, etc working still remains to be > > >> >> done. > > >> >> >> > > > >> >> >> > > >> >> >> About the latter - the NIC is pretty complex, however we > > >> >> (Semihalf) > > >> >> >> have really huge experience with all its support > > >> >> implementations and > > >> >> >> the platform itself. I'll put it straightforward - it's > > >> only a > > >> >> >> matter > > >> >> >> of development funding, if it's guaranteed, we will do it > > >> with > > >> >> >> pleasure :) As well as the NIC support (DW Synopsys driver > > >> for > > >> >> DT > > >> >> >> and > > >> >> >> verify/improve on pcie-host-generic with ACPI). > > >> >> > > > >> >> > "As well as PCIE support..." of course. > > >> >> > > > >> >> > Marcin > > >> >> > > >> >> Hi, > > >> >> > > >> >> I've noticed that people successfully use ACPI-PCIe on the > > >> >> MACCHIATObin > > >> >> with Linux, > > >> >> so? has anyone tested FreeBSD pcie-host-generic there? > > >> >> > > >> >> I'm considering buying a MACCHIATObin board to test my drm-next > > >> >> build > > >> >> for aarch64 > > >> >> ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd > > >> like > > >> >> to > > >> >> first know if PCIe actually works :) > > >> > > > >> > I'll will push support for mcbin soon in the tree (with PCI > > >> support). > > >> > I don't know what ACPI-PCIe is exactly but I don't see how it ca= n > > >> > work > > >> > without a dedicated driver for the armada 8K. > > >> > > >> dev/pci/pci_host_generic_acpi.c =E2=80=94 generic ECAM PCIe driver. > > >> > > >> I think ThunderX2 uses it (2018 Cavium copyright in the file), > > >> probably > > >> Ampere eMAG (haven't seen anything about that here, but the vendor > > >> lists FreeBSD in their OS compatibility list), should be possible t= o > > >> use on the SoftIron Overdrives (NetBSD just added ACPI/aarch64 and > > >> they > > >> tested on the Overdrive: > > >> https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4526 =E2=80=94 b= ut all > > >> FreeBSD+SoftIron dmesgs on dmesgd.nycbug so far are in FDT mode, no= t > > >> ACPI)=E2=80=A6 > > >> > > >> And the EDK2 firmware for the Armada8k does have an ACPI mode=E2=80= =A6 > > >> > > > > > > I confirm - thanks to the initial configuration in UEFI, ACPI tables > > > support PCI, which OS can use with the pure ECAM pci-host-generic > > > driver. Here's also the latest Centos7 bootlog, where you can see it: > > > https://pastebin.com/Aa2NvDnM > > > > > > Marcin > > > > So you haven't tried booting *FreeBSD* in ACPI mode on the 8k yet? And I tried such boot but a year ago, before adding PCIE support to the UEF= I :) > > > > Would be great to see a FreeBSD dmesg from that configuration on > > https://dmesgd.nycbug.org :) > > > > Good idea, however I won't be able to do it in coming days. If anyone > would like to try it out before, below is my latest built of EDK2 > firmware for the MacchiatoBin board: > https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/wiki/file= s/flash-image-18.09.4.bin > > Best regards, > Marcin From owner-freebsd-arm@freebsd.org Thu Nov 1 01:28:03 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2255D10DA27A for ; Thu, 1 Nov 2018 01:28:03 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B395276158 for ; Thu, 1 Nov 2018 01:28:02 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-it1-x12a.google.com with SMTP id s16so96337itj.1 for ; Wed, 31 Oct 2018 18:28:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=n2HzkSSYuD3u+R183MgzmTRKZT0sE5J6bgS5YAdgvew=; b=cRv4KBrVq0LY61NZiXR6GQ9lk9kwzyoVIfn04h7v72zBbQzr6945QS1x+yC7W+T/qo 9U2RuPwKFqGlbcK+hTHIpQiM8uYIrOPFnilq5ZqsPbCYWZuMxMIIiOlc1jyFM05hbcEI 8W/IfHkqCoGABzmrhpi+zx97kS1iSyWNyy4syB1XGh+v/ozbr1VWPZwQbKGY2oIbM2ve gRBc7bfLLScatcjYcNpkFMl578MflVPN8TOLTfAlH8rP8Iaad0p+M0wqZwY8d+0T6FzE Go8K1kBAfhZV/Pj8hiJXvYkG0FB7iaK+TtKx4DulCJsseOkusTeGTh2CHZ9O+bPJ91AM UXnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=n2HzkSSYuD3u+R183MgzmTRKZT0sE5J6bgS5YAdgvew=; b=A0ig4+4LeDZesOoK3rmL6wZDnJKER17c4AkIdqY9H5MBVNyGeBFY/UXuqXvf15YvEA tfI6llaj68km3ZtPT3SvCWMMkoCGBqmm6f8z1FbNlEohaCBaRhNzBprSDRpB1AasnfjR MqE9WFjF2ixXslHBPibGracdC9Tkdeogc0aRyflqxcWrjyiOY/bJpFMWEmACI3WQg/22 pAIFe3hPvfDGwKkVJ32IcNNsC1YVwDgBFU6X7y31ObBfqJj7E+kuGKSi7uELMH3jtDa5 iRlSFean9u+2ZMGjopuo1hBKu9j0dz/QpkfeQfaokbZsm6PhrFbK695MUjq+rF6Mhl85 ihZw== X-Gm-Message-State: AGRZ1gIWxplyGQvlwafpIfipC9Gd/ThIV5y8uv82mUz1iwd13Prxe/9E dn2/eed6lmUTrjw0ze1JwcPmrV180wHIeoiOGozGiezIrvk= X-Google-Smtp-Source: AJdET5c5eaIyS6o9JILpcIgIs865ZkAxs4QseNsSgToNsonTzUO/ia0QLfcUKhfsFsTkvWXMiIt58TwuKvhVw2b4NPg= X-Received: by 2002:a24:c647:: with SMTP id j68-v6mr4007133itg.138.1541035681934; Wed, 31 Oct 2018 18:28:01 -0700 (PDT) MIME-Version: 1.0 References: <4DCCA5C9-C156-4080-A8F9-035478AC2FF7@yahoo.com> <1540841879.1781.1@smtp.migadu.com> <20181029204655.73c0895cf2df7245769590fe@bidouilliste.com> <1540843531.1781.2@smtp.migadu.com> <1540939560.20404.0@smtp.migadu.com> In-Reply-To: <1540939560.20404.0@smtp.migadu.com> From: Marcin Wojtas Date: Thu, 1 Nov 2018 02:27:51 +0100 Message-ID: Subject: Re: MACCHIATObin To: greg@unrelenting.technology Cc: Emmanuel Vadot , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 01:28:03 -0000 wt., 30 pa=C5=BA 2018 o 23:46 Greg V napisa= =C5=82(a): > > > > On Tue, Oct 30, 2018 at 12:48 AM, Marcin Wojtas wrote: > > Hi, > > > > pon., 29 pa=C5=BA 2018 o 21:05 Greg V > > napisa=C5=82(a): > >> > >> > >> > >> On Mon, Oct 29, 2018 at 10:46 PM, Emmanuel Vadot > >> wrote: > >> > On Mon, 29 Oct 2018 22:37:59 +0300 > >> > Greg V wrote: > >> > > >> >> > >> >> > >> >> On Sat, Aug 18, 2018 at 10:07 AM, Marcin Wojtas > >> > >> >> wrote: > >> >> > sob., 18 sie 2018 o 08:43 Marcin Wojtas > >> >> napisa?(a): > >> >> >> > >> >> >> sob., 18 sie 2018 o 01:10 Jim Thompson > >> >> >> napisa?(a): > >> >> >> > > >> >> >> > On Aug 17, 2018, at 5:42 PM, Mark Millard via freebsd-arm > >> >> >> wrote: > >> >> >> > > >> >> >> > > Marcin Wojtas mw at semihalf.com wrote on > >> >> >> > > Fri May 11 07:55:40 UTC 2018 : > >> >> >> > > > >> >> >> > >> Short status of the support - last year we enabled > >> most of > >> >> the > >> >> >> > >> platform functionalities (core support, USB, AHCI, > >> RTC). > >> >> Three > >> >> >> big > >> >> >> > >> items remained left: > >> >> >> > >> - PCIE root complex (this should work soon with the > >> work > >> >> done > >> >> >> for > >> >> >> > >> another SoC, not merged yet) > >> >> >> > >> - Network PPv2 > >> >> >> > >> - Xenon SD/MMC controller > >> >> >> > > > >> >> >> > > > >> >> >> > > I noticed a check in that deals with that "Xenon" > >> >> >> > > SD/MMC controller: > >> >> >> > > > >> >> >> > > Author: loos > >> >> >> > > Date: Tue Aug 14 16:33:30 2018 > >> >> >> > > New Revision: 337772 > >> >> >> > > URL: > >> >> >> > > https://svnweb.freebsd.org/changeset/base/337772 > >> >> >> > >> >> [?] > >> >> >> > > > >> >> >> > > But I've not noticed check-ins for the other of the "big > >> >> >> > > items" going by. (Though they may have.) > >> >> >> > > > >> >> >> > > Care to comment-on/update-the actual status for the > >> >> >> > > Macchiato.bin(s)? > >> >> >> > > >> >> >> > > >> >> >> > tl;dr: It?s not ?there? yet. > >> >> >> > > >> >> >> > Specifics: > >> >> >> > > >> >> >> > - loos@ has done a lot of work to get the espresso.bin > >> >> working, > >> >> >> and some of this carries over to the 8k/7k. > >> >> >> > - We have another internal developer working on an EIP-97 > >> >> driver > >> >> >> for crypto offload. This should be a foundation for the > >> EIP-197 > >> >> in > >> >> >> the 8K. > >> >> >> > - I know manu@is working on pin controllers and clocks > >> >> specific > >> >> >> to Machiatto.bin (80x0/70x0). > >> >> >> > - Getting the NICs, PCIe, etc working still remains to be > >> >> done. > >> >> >> > > >> >> >> > >> >> >> About the latter - the NIC is pretty complex, however we > >> >> (Semihalf) > >> >> >> have really huge experience with all its support > >> >> implementations and > >> >> >> the platform itself. I'll put it straightforward - it's > >> only a > >> >> >> matter > >> >> >> of development funding, if it's guaranteed, we will do it > >> with > >> >> >> pleasure :) As well as the NIC support (DW Synopsys driver > >> for > >> >> DT > >> >> >> and > >> >> >> verify/improve on pcie-host-generic with ACPI). > >> >> > > >> >> > "As well as PCIE support..." of course. > >> >> > > >> >> > Marcin > >> >> > >> >> Hi, > >> >> > >> >> I've noticed that people successfully use ACPI-PCIe on the > >> >> MACCHIATObin > >> >> with Linux, > >> >> so? has anyone tested FreeBSD pcie-host-generic there? > >> >> > >> >> I'm considering buying a MACCHIATObin board to test my drm-next > >> >> build > >> >> for aarch64 > >> >> ( https://github.com/FreeBSDDesktop/kms-drm/pull/89 ), but I'd > >> like > >> >> to > >> >> first know if PCIe actually works :) > >> > > >> > I'll will push support for mcbin soon in the tree (with PCI > >> support). > >> > I don't know what ACPI-PCIe is exactly but I don't see how it can > >> > work > >> > without a dedicated driver for the armada 8K. > >> > >> dev/pci/pci_host_generic_acpi.c =E2=80=94 generic ECAM PCIe driver. > >> > >> I think ThunderX2 uses it (2018 Cavium copyright in the file), > >> probably > >> Ampere eMAG (haven't seen anything about that here, but the vendor > >> lists FreeBSD in their OS compatibility list), should be possible to > >> use on the SoftIron Overdrives (NetBSD just added ACPI/aarch64 and > >> they > >> tested on the Overdrive: > >> https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4526 =E2=80=94 but= all > >> FreeBSD+SoftIron dmesgs on dmesgd.nycbug so far are in FDT mode, not > >> ACPI)=E2=80=A6 > >> > >> And the EDK2 firmware for the Armada8k does have an ACPI mode=E2=80= =A6 > >> > > > > I confirm - thanks to the initial configuration in UEFI, ACPI tables > > support PCI, which OS can use with the pure ECAM pci-host-generic > > driver. Here's also the latest Centos7 bootlog, where you can see it: > > https://pastebin.com/Aa2NvDnM > > > > Marcin > > So you haven't tried booting *FreeBSD* in ACPI mode on the 8k yet? > > Would be great to see a FreeBSD dmesg from that configuration on > https://dmesgd.nycbug.org :) > Good idea, however I won't be able to do it in coming days. If anyone would like to try it out before, below is my latest built of EDK2 firmware for the MacchiatoBin board: https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/wiki/files/= flash-image-18.09.4.bin Best regards, Marcin From owner-freebsd-arm@freebsd.org Thu Nov 1 22:53:03 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC10010DBDE8 for ; Thu, 1 Nov 2018 22:53:03 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh601-vm11.bullet.mail.ssk.yahoo.co.jp (nh601-vm11.bullet.mail.ssk.yahoo.co.jp [182.22.90.20]) by mx1.freebsd.org (Postfix) with SMTP id D02356A019 for ; Thu, 1 Nov 2018 22:53:02 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.103] by nh601.bullet.mail.ssk.yahoo.co.jp with NNFMP; 01 Nov 2018 22:50:54 -0000 Received: from [182.22.91.206] by t601.bullet.mail.ssk.yahoo.co.jp with NNFMP; 01 Nov 2018 22:50:54 -0000 Received: from [127.0.0.1] by omp609.mail.ssk.yahoo.co.jp with NNFMP; 01 Nov 2018 22:50:54 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 700147.79940.bm@omp609.mail.ssk.yahoo.co.jp Received: (qmail 75985 invoked by uid 60001); 1 Nov 2018 22:50:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1541112654; bh=VLt1v3/LWerW//BiwDW3bL8JTbGCUgML0uf7UZAXxIk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vzBiiYO0bG10wStToJ7eSGULvmFYRESkgLOXyxIRdIhh2r5cwDeatqrB7V5vnitSFksbbkAIZf2rVpHl9cmIAOyGoIAbZjJMURYrBV8SnIK0+G+rH8icwBUTr8zp2poWKEADUwBtkSgSgIrenYFSC05JiFPgLruzddavSKiuWrc= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MKw6JEsrF67mjdwz4YWIdEvdvvzG4l8LhkZ9/VHDco/jlPqMDsz1J4sYIK0Pj+ERFVPg0DslcUaIstva5MRiSN3T52zHyYj4cCowLOHbcYikIQGfzxJRPgWatqwBpA+MrUWTvsofZ6pl+0/FKrxqe6L3fJzbc8cXvI6Jxyl5UFo=; Message-ID: <605941.47343.qm@web103905.mail.ssk.yahoo.co.jp> X-YMail-OSG: YjtMta4VM1kvCvJ91JkLbcANgwHU3xKt_3bY1GEl.VcMDj0maq_qVxrd3SSfGfrvB.lj8xXTWU7.YBeKy.upHXTJHbb2qjwtBojUyIrelLXXcjuCguUXcaF82L6K9gqEhYVbXIQLMs1z2vt6CC50TOaRe.6vKY9tRdS6Q2w9nNCkEOfw4RQ_NIgCqNpLMJUZYZDVRx8PCqqA7bOwyGCd_BY0l2y_SDq_NiEpwwYr6GdedIq8DkgdNhnDLTKW5s9DZl9R7LZS1ZWP4MDz3Uq44sJX5ZON4Un0lAwbBvXaW0E3JQ0F2ny.wH3hrCYmnoHae6va1gcKsxIfvSRtz5Fe1zvDMbWiNlTqnYzY_2UTClzA3QWrb8.yaBCwzq9EfOxitHbokVBFd_YUDtV2Iyljt1WS0X2AQiaiclBjKFpUTw0UeG9IbjqrCMqoYT.i0uvJALCjXgUhXYhBVjP2ACIyoL3YY7LK.g0VY48GQwbtB.MqkEpgUzLB.tM2ei.xxTq.RLaJKC6hMo_NWFscLKtbaTF6jagxK.Rz6NNr.ujAwNzCGqU5ouM8a.sGy6MIkV.O7MKQjrVuaA3iQk9Q8RoSVk6hCFQMET.gH6bwfietq5lPOS8US7ldnHjf7jriviY- Received: from [203.165.243.65] by web103905.mail.ssk.yahoo.co.jp via HTTP; Fri, 02 Nov 2018 07:50:53 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: WXRWi_gVM1lps51CpwCaw1mIWF07bGK_uJtZu2iWC_Q5nUM_aWWcepasSUkutpGYGH9OlO1dFK3E92J1m50SuImPB3csWHCmnvv1Nzh7QuDpZHkZceX0TbAhSPQaa0yatBp0 Date: Fri, 2 Nov 2018 07:50:53 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: elfcopy make corrupt binary on armv7 To: "freebsd-arm@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2018 22:53:03 -0000 Hi=0A=0AI try pcDuino by ZRouter build system.=0A=0AI found elfcopy(objcopy= ) bug.=0A=0Aelfcopy make=A0corrupt file by -O binary.=0A=0AI seem data sect= ion is wrong position at elfcopy.=A0=0A=0AThis is files.=0A=0Ahttps://www.d= ropbox.com/s/xtw7jlc5kpiyd91/armv7kernel.tar.xz?dl=3D0=0A=0A=0APcduino_Lite= _kernel - original elf file=0A=0APcduino_Lite_kernel.elfcopy.ng - corrupt f= ile by FreeBSD elfcopy=0A=A0=0APcduino_Lite_kernel.objcopy.ok - good file b= y binutil objcopy=0A=0ARegards=0A=0AHroki Mori From owner-freebsd-arm@freebsd.org Sat Nov 3 00:23:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8458010E0345 for ; Sat, 3 Nov 2018 00:23:26 +0000 (UTC) (envelope-from neerajpal09@gmail.com) Received: from mail-ot1-x341.google.com (mail-ot1-x341.google.com [IPv6:2607:f8b0:4864:20::341]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 10EE886373 for ; Sat, 3 Nov 2018 00:23:26 +0000 (UTC) (envelope-from neerajpal09@gmail.com) Received: by mail-ot1-x341.google.com with SMTP id e9so3227063oti.1 for ; Fri, 02 Nov 2018 17:23:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+vawxrYgTXRbq5Phejnr0kZ2PdnDHzlyaomvB+DSO98=; b=kcs2RbiUEBHmQLl85hik9Rm4j2usv05cMtZ8jMgXxbKktbirXcWC4u9EC828wbp12T D8Fm/tmenSdRBZeiE/ykYe9weEpjx9LTDn97g9wZkYCZkpGzxRgoM1uWasEkQc4N3Ud5 F/01twAntGr0dq6c4+yNwhmSo+MCAsYwwLFrikL90CJb86jRBElTIO02DWioVjLOsP/R E3+0Hgqd4ZHanytlQWuvYdq3MwTsMahUdI+hcrbS2TUupmL7IqXfd6AI0q8DhXcsNogG 8cHfPnKXlyGiYhs5C1gMLhmhYblQeNMPm2Mi2tyEULrZ8l0IpOsbtqTbeQXwqZR2K9PH eJYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+vawxrYgTXRbq5Phejnr0kZ2PdnDHzlyaomvB+DSO98=; b=npWVzbD49otOU12hD0+nDUevRlqIdpIJsvV6cj1e9MZvlVkxmur1t1VfYhMwdMDj5n LoD8HZsn1Ks3pGGJfSUgV7vtES4UNBfUaBnYbC+IZ8TeuMT//rc7TYKVrBAVR/Mzg0v/ rStMqhACOK841yGH+pQf94vDMdpm1uFpJx1wCoeLx1VuJekEeNINj8jRkRN3o7mKxMiB cEulgQNyU836tuc/dWrFH5iGa/k98uj82bIvFIbovgWofV5r7ZMXDXRuiPLiz++TLkrA 16j95k/s+z+ShsFI72ZDYWHn6dX6o34S2sSbO5gPV8r6Dwt1IqzeCY00E5d4FNRs0LTq RCKA== X-Gm-Message-State: AGRZ1gLaLH1i1kSvK11pPEuwNwZcHgVOS68Vr3tsCa2BolvYYtH1tSi8 C2J/JaugXPLApgTj0xC1OI2u/qsDG/0gcOs0Dfxp6TFQ/CI= X-Google-Smtp-Source: AJdET5fGMMsE/U5f6EZs6tjfZY/BstSwVrE6M9sJ31ISBwTfRDvFW5LcjBhU7AtaEGwo2f+zO4EV3DbE7UDKyhnKa1M= X-Received: by 2002:a9d:2a26:: with SMTP id t35mr8929650ota.16.1541204604848; Fri, 02 Nov 2018 17:23:24 -0700 (PDT) MIME-Version: 1.0 From: Neeraj Pal Date: Sat, 3 Nov 2018 05:53:13 +0530 Message-ID: Subject: FreeBSD-13.0-current not booting/hang in BeagleBone Black To: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 00:23:26 -0000 Hi there, I have written the FreeBSD-13.0-current snapshot BeagleBone image file into sd card (16gb) using dd. Then, trying to load the image file into BeagleBone Black Rev. C but it seems it is not working. And, after that, I have tried FreeBSD-12.0-ALPHA10 image and it is working fine and below is the dmesg (after log of FreeBSD-13.0-current). Maybe there is something wrong with the FreeBSD-13.0-current snapshot, although I am not sure. Here, is the log: FreeBSD-13.0-current: U-Boot SPL 2018.09 (Nov 01 2018 - 03:26:04 +0000) Trying to boot from MMC1 Loading Environment from FAT... *** Warning - bad CRC, using default environment Loading Environment from MMC... *** Warning - bad CRC, using default environment U-Boot 2018.09 (Nov 01 2018 - 03:26:04 +0000) CPU : AM335X-GP rev 2.1 I2C: ready DRAM: 512 MiB No match for driver 'omap_hsmmc' No match for driver 'omap_hsmmc' Some drivers were not found MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment Loading Environment from MMC... *** Warning - bad CRC, using default environment not set. Validating first E-fuse MAC Net: cpsw, usb_ether Press SPACE to abort autoboot in 2 seconds switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 51500 bytes read in 6 ms (8.2 MiB/s) Found EFI removable media binary efi/boot/bootarm.efi Scanning disks on usb... Disk usb0 not ready Disk usb1 not ready Disk usb2 not ready Disk usb3 not ready Loading kernel... /boot/kernel/kernel text=0x860500 data=0xb5d28+0x24cdd8 syms=[0x4+0xa91d0+0x4+]- Loading configured modules... can't find '/boot/entropy' /boot/kernel/umodem.ko text=0x1bf4 text=0x1320 data=0x1080+0xf88 syms=[0x4+0x10] loading required module 'ucom' /boot/kernel/ucom.ko text=0x1f8c text=0x2e90 data=0x1080+0x17bc syms=[0x4+0x14f] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Using DTB provided by EFI at 0x87ff1000. Kernel entry at 0x95000180... Kernel args: (null) modulep: 0xc0d3b000 relocation_offset 0 ---<>--- ARM Debug Architecture not supported KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-CURRENT r339979 GENERIC arm FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. module_register: cannot register ofwbus/pcib from kernel; already loaded from kl Module ofwbus/pcib failed to register: 17 module_register: cannot register simplebus/pcib from kernel; already loaded frol Module simplebus/pcib failed to register: 17 CPU: ARM Cortex-A8 r3p2 (ECO: 0x00000000) CPU Features: Thumb2, Security, VMSAv7 Optional instructions: UMULL, SMULL, SIMD(ext) LoUU:2 LoC:3 LoUIS:1 Cache level 1: 32KB/64B 4-way data cache WT WB Read-Alloc 32KB/64B 4-way instruction cache Read-Alloc Cache level 2: 256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc real memory = 0 (0 MB) avail memory = 505835520 (482 MB) No PSCI/SMCCC call function found Texas Instruments AM335x Processor, Revision ES2.1 arc4random: no preloaded entropy cache random: entropy device external interface kbd0 at kbdmux0 ofwbus0: simplebus0: on ofwbus0 simplebus1: on simplebus0 am335x_prcm0: mem 0x200000-0x203fff on simp1 simplebus2: mem 0x210000-0x211fff on simpleb1 ti_scm0: mem 0-0x7ff on simplebus2 regfix0: on ofwbus0 clk_fixed0: on ofwbus0 ti_aintc0: mem 0x48200000-0x48200fff on simpleb0 ti_aintc0: Revision 5.0 am335x_prcm0: Clocks: System 24.0 MHz, CPU 1000 MHz cpulist0: on ofwbus0 cpu0: on cpulist0 pmu0: mem 0x4b000000-0x4bffffff irq 0 on ofwbus0 ti_pinmux0: mem 0x800-0xa37 on simplebus2 am335x_scm0: on ti_scm0 gpio0: mem 0x44e07000-0x44e07fff irq 7 o0 gpiobus0: on gpio0 gpioc0: on gpio0 gpio1: mem 0x4804c000-0x4804cfff irq 8 o0 gpiobus1: on gpio1 gpioc1: on gpio1 gpio2: mem 0x481ac000-0x481acfff irq 9 o0 gpiobus2: on gpio2 gpioc2: on gpio2 gpio3: mem 0x481ae000-0x481aefff irq 10 0 gpiobus3: on gpio3 gpioc3: on gpio3 uart0: console (115384,n,8,1)atible)> mem 0x44e09000-0x44e0afff irq 11 on simpl0 iichb0: mem 0x44e0b000-0x44e0bfff irq 17 on simplebus0 iichb0: I2C revision 4.0 FIFO size: 32 bytes iichb1: mem 0x4819c000-0x4819cfff irq 19 on simplebus0 iichb1: I2C revision 4.0 FIFO size: 32 bytes sdhci_ti0: mem 0x48060000-0x48060fff irq 20 on simplebus0 mmc0: on sdhci_ti0 sdhci_ti1: mem 0x481d8000-0x481d8fff irq 21 on simplebus0 mmc1: on sdhci_ti1 ti_wdt0: mem 0x44e35000-0x44e35fff irq 23 on simplebus0 ti_mbox0: mem 0x480c8000-0x480c81ff irq 26 on simplebus0 ti_mbox0: revision 4.0 am335x_dmtimer0: mem 0x48040000-0x480403ff irq 28 on simplebu0 Event timer "DMTimer2" frequency 24000000 Hz quality 500 am335x_dmtimer1: mem 0x48042000-0x480423ff irq 29 on simplebu0 Timecounter "DMTimer3" frequency 24000000 Hz quality 500 am335x_rtc0: mem 0x44e3e000-0x44e3efff irq0 am335x_rtc0: AM335X RTC v1.0.6 usbss0: mem 0x47400000-0x47400fff on 0 usbss0: TI AM335X USBSS v0.0.13 musbotg0: mem 0x47401400-0x474017ff,00 usbus0: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM usbus0 on musbotg0 musbotg1: mem 0x47401c00-0x47401fff,00 usbus1: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM usbus1 on musbotg1 cpswss0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a1007ff,0x4a101200 cpswss0: CPSW SS Version 1.12 (0) cpswss0: Initial queue size TX=128 RX=384 cpsw0: on cpswss0 miibus0: on cpsw0 smscphy0: PHY 0 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cpsw0: Ethernet address: 88:c2:55:8d:ec:f6 fb0: mem 0x4830e000-0x4830efff irq 43 on simplebus0 ti_adc0: mem 0x44e0d000-0x44e0dfff irq 44 disabled on simpl0 ti_adc0: scheme: 0x1 func: 0x730 rtl: 0 rev: 0.1 custom rev: 0 gpioled0: on ofwbus0 cryptosoft0: Timecounters tick every 1.000 msec usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 iicbus0: on iichb0 iic0: on iicbus0 am335x_pmic0: at addr 0x48 irq 59 on iicbus0 icee0: at addr 0xa0 on iicbus0 tda0 at addr 0xe0 on iicbus0 iicbus1: on iichb1 iic1: on iicbus1 icee1: at addr 0xa8 on iicbus1 icee2: at addr 0xaa on iicbus1 icee3: at addr 0xac on iicbus1 icee4: at addr 0xae on iicbus1 ugen1.1: at usbus1 uhub0: on usbu1 ugen0.1: at usbus0 uhub1: on usbu0 mmcsd0: 16GB at mmc0 48.0MHz/4k uhub1: 1 port with 1 removable, self powered uhub0: 1 port with 1 removable, self powered ugen0.2: at0 ugen0.2: at) ugen0.2: at0 umodem0 on uhub1 umodem0: on usbus0 umodem0: data interface 1, has CM over data, has break mmcsd1: 4GB at mmc1 48k mmcsd1boot0: 4MB partion 1 at mmcsd1 mmcsd1boot1: 4MB partion 2 at mmcsd1 mmcsd1rpmb: 4MB partion 3 at mmcsd1 am335x_pmic0: TPS65217C ver 1.2 powered by USB tda0: TDA19988 GEOM_PART: integrity check failed (mmcsd1s4, BSD) GEOM_PART: integrity check failed (diskid/DISK-4EDE5FD4s4, BSD) tda0: failed to read EDID WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ufs/rootfs [rw]... Warning: no time-of-day clock registered, system time will not be set accurately random: unblocking device. FreeBSD-12.0-ALPHA10 freebsd@generic:~ % dmesg ---<>--- ARM Debug Architecture not supported KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-ALPHA10 r339377 GENERIC arm FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. module_register: cannot register ofwbus/pcib from kernel; already loaded from kernel Module ofwbus/pcib failed to register: 17 module_register: cannot register simplebus/pcib from kernel; already loaded from kernel Module simplebus/pcib failed to register: 17 CPU: ARM Cortex-A8 r3p2 (ECO: 0x00000000) CPU Features: Thumb2, Security, VMSAv7 Optional instructions: UMULL, SMULL, SIMD(ext) LoUU:2 LoC:3 LoUIS:1 Cache level 1: 32KB/64B 4-way data cache WT WB Read-Alloc 32KB/64B 4-way instruction cache Read-Alloc Cache level 2: 256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc real memory = 0 (0 MB) avail memory = 505872384 (482 MB) No PSCI/SMCCC call function found Texas Instruments AM335x Processor, Revision ES2.1 arc4random: no preloaded entropy cache random: entropy device external interface kbd0 at kbdmux0 ofwbus0: simplebus0: on ofwbus0 simplebus1: on simplebus0 am335x_prcm0: mem 0x200000-0x203fff on simplebus1 simplebus2: mem 0x210000-0x211fff on simplebus1 ti_scm0: mem 0-0x7ff on simplebus2 regfix0: on ofwbus0 clk_fixed0: on ofwbus0 ti_aintc0: mem 0x48200000-0x48200fff on simplebus0 ti_aintc0: Revision 5.0 am335x_prcm0: Clocks: System 24.0 MHz, CPU 1000 MHz cpulist0: on ofwbus0 cpu0: on cpulist0 pmu0: mem 0x4b000000-0x4bffffff irq 0 on ofwbus0 ti_pinmux0: mem 0x800-0xa37 on simplebus2 am335x_scm0: on ti_scm0 gpio0: mem 0x44e07000-0x44e07fff irq 7 on simplebus0 gpiobus0: on gpio0 gpioc0: on gpio0 gpio1: mem 0x4804c000-0x4804cfff irq 8 on simplebus0 gpiobus1: on gpio1 gpioc1: on gpio1 gpio2: mem 0x481ac000-0x481acfff irq 9 on simplebus0 gpiobus2: on gpio2 gpioc2: on gpio2 gpio3: mem 0x481ae000-0x481aefff irq 10 on simplebus0 gpiobus3: on gpio3 gpioc3: on gpio3 uart0: mem 0x44e09000-0x44e0afff irq 11 on simplebus0 uart0: console (115384,n,8,1) iichb0: mem 0x44e0b000-0x44e0bfff irq 17 on simplebus0 iichb0: I2C revision 4.0 FIFO size: 32 bytes iichb1: mem 0x4819c000-0x4819cfff irq 19 on simplebus0 iichb1: I2C revision 4.0 FIFO size: 32 bytes sdhci_ti0: mem 0x48060000-0x48060fff irq 20 on simplebus0 mmc0: on sdhci_ti0 sdhci_ti1: mem 0x481d8000-0x481d8fff irq 21 on simplebus0 mmc1: on sdhci_ti1 ti_wdt0: mem 0x44e35000-0x44e35fff irq 23 on simplebus0 ti_mbox0: mem 0x480c8000-0x480c81ff irq 26 on simplebus0 ti_mbox0: revision 4.0 am335x_dmtimer0: mem 0x48040000-0x480403ff irq 28 on simplebus0 Event timer "DMTimer2" frequency 24000000 Hz quality 500 am335x_dmtimer1: mem 0x48042000-0x480423ff irq 29 on simplebus0 Timecounter "DMTimer3" frequency 24000000 Hz quality 500 am335x_rtc0: mem 0x44e3e000-0x44e3efff irq 34,35 on simplebus0 am335x_rtc0: AM335X RTC v1.0.6 usbss0: mem 0x47400000-0x47400fff on simplebus0 usbss0: TI AM335X USBSS v0.0.13 musbotg0: mem 0x47401400-0x474017ff,0x47401000-0x474011ff irq 56 on usbss0 usbus0: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM usbus0 on musbotg0 musbotg1: mem 0x47401c00-0x47401fff,0x47401800-0x474019ff irq 57 on usbss0 usbus1: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM usbus1 on musbotg1 cpswss0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a1007ff,0x4a101200-0x4a1012ff irq 38,39,40,41 on simplebus0 cpswss0: CPSW SS Version 1.12 (0) cpswss0: Initial queue size TX=128 RX=384 cpsw0: on cpswss0 miibus0: on cpsw0 smscphy0: PHY 0 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cpsw0: Ethernet address: 88:c2:55:8d:ec:f6 fb0: mem 0x4830e000-0x4830efff irq 43 on simplebus0 ti_adc0: mem 0x44e0d000-0x44e0dfff irq 44 disabled on simplebus0 ti_adc0: scheme: 0x1 func: 0x730 rtl: 0 rev: 0.1 custom rev: 0 gpioled0: on ofwbus0 cryptosoft0: Timecounters tick every 1.000 msec usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 iicbus0: on iichb0 iic0: on iicbus0 am335x_pmic0: at addr 0x48 irq 59 on iicbus0 icee0: at addr 0xa0 on iicbus0 tda0 at addr 0xe0 on iicbus0 iicbus1: on iichb1 iic1: on iicbus1 icee1: at addr 0xa8 on iicbus1 icee2: at addr 0xaa on iicbus1 icee3: at addr 0xac on iicbus1 icee4: at addr 0xae on iicbus1 ugen1.1: at usbus1 uhub0: on usbus1 ugen0.1: at usbus0 uhub1: on usbus0 mmcsd0: 16GB at mmc0 48.0MHz/4bit/65535-block uhub1: 1 port with 1 removable, self powered uhub0: 1 port with 1 removable, self powered ugen0.2: at usbus0 ugen0.2: at usbus0 (disconnected) ugen0.2: at usbus0 umodem0 on uhub1 umodem0: on usbus0 umodem0: data interface 1, has CM over data, has break mmcsd1: 4GB at mmc1 48.0MHz/8bit/65535-block mmcsd1boot0: 4MB partion 1 at mmcsd1 mmcsd1boot1: 4MB partion 2 at mmcsd1 mmcsd1rpmb: 4MB partion 3 at mmcsd1 am335x_pmic0: TPS65217C ver 1.2 powered by USB tda0: TDA19988 GEOM_PART: integrity check failed (mmcsd1s4, BSD) GEOM_PART: integrity check failed (diskid/DISK-4EDE5FD4s4, BSD) tda0: failed to read EDID WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ufs/rootfs [rw]... Warning: no time-of-day clock registered, system time will not be set accurately GEOM_PART: mmcsd0s2 was automatically resized. Use `gpart commit mmcsd0s2` to save changes or `gpart undo mmcsd0s2` to revert them. random: unblocking device. lock order reversal: 1st 0xc2415b10 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3916 2nd 0xd37dcc00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:289 stack backtrace: lo0: link state changed to UP cpsw0: link state changed to DOWN cpsw0: link state changed to UP -- Thank you! Sincere regards; Neeraj Pal From owner-freebsd-arm@freebsd.org Sat Nov 3 00:45:21 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6B2410E1179 for ; Sat, 3 Nov 2018 00:45:21 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-f176.google.com (mail-it1-f176.google.com [209.85.166.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7BE0187103 for ; Sat, 3 Nov 2018 00:45:21 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-f176.google.com with SMTP id h13so5561748itl.1 for ; Fri, 02 Nov 2018 17:45:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=76inY5OvsnguynualWZ1M704Zqf366rHGjQYycUdIIw=; b=av4va0sRHi+9VU89in8kZx3QpI3/kJ+NVSkBM4VoEiH9fnrac5DcRweenXFdvj9l66 Az5Z1qZ5Hhf/StPzGvQuBG/vhM/1fJuhSY6XA29gmyoPqRziYWeFRKpkO5VrP08Umq/l gcU3INZp4Unc3rPCcFNmAvpzRhGauPwl1/0pa6xYB/a5lWjNdrjyRIb+2kqfWYn4OWa0 KCAP1imfa/thlj9Q7mJ4FS/wwkvWXHwlDMLGtMvJQAoOyHqR9PPaBy2ZS2NDTZsIOVRz z3GidEq1TpKauvQpbzUQPrhuSHT/oKbJsTNkmYs0XHfbiJxLi7sIlphy2gtFnanvsIRJ jA0Q== X-Gm-Message-State: AGRZ1gIPvhiL6dgXbe6b3ojdXJ0xPZQc5cTWJNCburOJStFeSlmH5AGM aznMIPBP+FsJwbigbmUROHP3ZgsEZhl6rD4hkEs= X-Google-Smtp-Source: AJdET5fCbGVERfiGpK8aw2ePHwYiNM/DB7uj+NUjmKREliS31Ryo1DFmL5943WZ1TmkEZAittdj398KMwr4hdUoAuOw= X-Received: by 2002:a02:5998:: with SMTP id v24-v6mr10546663jad.129.1541205415695; Fri, 02 Nov 2018 17:36:55 -0700 (PDT) MIME-Version: 1.0 References: <605941.47343.qm@web103905.mail.ssk.yahoo.co.jp> In-Reply-To: <605941.47343.qm@web103905.mail.ssk.yahoo.co.jp> From: Ed Maste Date: Fri, 2 Nov 2018 20:36:40 -0400 Message-ID: Subject: Re: elfcopy make corrupt binary on armv7 To: Mori Hiroki Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 00:45:22 -0000 On Thu, 1 Nov 2018 at 18:53, Mori Hiroki wrote: > > Hi > > I try pcDuino by ZRouter build system. > > I found elfcopy(objcopy) bug. Would you submit a PR to track this? From owner-freebsd-arm@freebsd.org Sat Nov 3 02:12:06 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFE9410E9488 for ; Sat, 3 Nov 2018 02:12:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6ED1D6C93A for ; Sat, 3 Nov 2018 02:12:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B5337BB6 for ; Sat, 3 Nov 2018 02:12:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wA32C5ZL000299 for ; Sat, 3 Nov 2018 02:12:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wA32C5j7000296 for freebsd-arm@FreeBSD.org; Sat, 3 Nov 2018 02:12:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 232922] elfcopy make corrupt binary on armv7 Date: Sat, 03 Nov 2018 02:12:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yamori813@yahoo.co.jp X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 02:12:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232922 Bug ID: 232922 Summary: elfcopy make corrupt binary on armv7 Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: yamori813@yahoo.co.jp I try pcDuino(Allwinner A10) by ZRouter build system. I do cross build for armv7 kernel on FreeBSD 10.4R amd64. I do convert ELF kernel to binary then u-boot image. I found FreeBSD elfcopy(objcopy) bug at armv7. elfcopy make corrupt file by -O binary. I seem data section is wrong position at elfcopy.=20 This is files. https://www.dropbox.com/s/xtw7jlc5kpiyd91/armv7kernel.tar.xz?dl=3D0 Pcduino_Lite_kernel - original elf file Pcduino_Lite_kernel.elfcopy.ng - corrupt file by FreeBSD elfcopy Pcduino_Lite_kernel.objcopy.ok - good file by binutil objcopy --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Sat Nov 3 15:27:58 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A85B10D4C34 for ; Sat, 3 Nov 2018 15:27:58 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97832863FF for ; Sat, 3 Nov 2018 15:27:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3FJNi0078915 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 3 Nov 2018 16:19:24 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541258364; bh=fNsgE0+dczN6bXCAjfVFMwCisaEXPsGV5MKVOzNMK00=; h=Date:From:To:Cc:Subject:Reply-To; b=VUDO9s7DBZSecejtaP4OCre7O+kyjrDRq8MFzSYZT7aUGiXok0mOYQ2rtgw7H/T7T e9mpCRyORjJuZ2US9TOfIhD+JT5FIqaYTjNRfmgSOIJi6RlZ3EweGSDGX9mhqBYD2G mMX4+D6rvr83/gW+qvHLeupGf7It2jpll92zU1og= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3FJK0o099623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 16:19:20 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3FJKjD036937; Sat, 3 Nov 2018 16:19:20 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3FJKMd036936; Sat, 3 Nov 2018 16:19:20 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 16:19:20 +0100 From: Bernd Walter To: freebsd-arm@freebsd.org Cc: Bernd Walter Subject: GENERICSD images? Message-ID: <20181103151920.GZ79858@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 15:27:58 -0000 When and how would you use the GENERICSD images? I assume they have a generic kernel, but do they need a specific u-boot installed before they can get used? What systems are supported? -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 18:51:46 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87D1F10E15B8 for ; Sat, 3 Nov 2018 18:51:46 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21E9D8D778 for ; Sat, 3 Nov 2018 18:51:46 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-it1-x12d.google.com with SMTP id v11so1343870itj.0 for ; Sat, 03 Nov 2018 11:51:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q97sTEvzaRW+f2MPd3LFmVU5l/fi2o29JkdIrW8H7jk=; b=guXXKqMdg3Z+F2sAXm9IQ2lokmPzYAkI2rX70xWeJhb6Eenuie4+iY26QqREedhmk8 rRIN6gWn/71iadkWcy015ttT1gX3J5w6C4iMrRFDqFF3PPrwC1ZBiYk3/NmTCmPrT5x/ EdnYbyLf+n1am2P26qAp8pYCu9mwBfzhEhSpE42wjtco/0E3C1R/PMS7I5yhRr+35E7w MQlb+HlX0v3bq81Q2sRxGdLE8t0fW5B+eXV2pwwhg/z1ZJqZ6hEjSVlYTMtxIkaQLNjZ e0IIxx0PBtqNAlQ/JOmr0IKjIcDvra66PWzG+a48TKvOqWD/42+ufGg39u8/iomIz4dS YPhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q97sTEvzaRW+f2MPd3LFmVU5l/fi2o29JkdIrW8H7jk=; b=Fgmmi9pc4UtMCNfuj7ldXI6NjmH87L/ISUj4Dmx8o9gorezVhiGfi/jsUfPIeDu0LY 2dLq5kEl/ibOjtXaz8WwJlAn9gky6Zb5o50PJnjh6z6yYa+W/BGM7dzcngujW0wFBve9 jQqnLjE4ATT7heIDl4djfXbizwX5UbulBDzHbr5i1BoRcP2xD8LPV3p+urKfjbsxkPT5 i/1PFR4YHc1uhMF2mlyC4qQdClGGho4DR8wBCf5agWRWU8HMBbDtAck7AHKwZGP3VFjk 3JFLd3NMNYXIYi9G2AO4bg8vEJTKtfPYiMVdAFG1LgvSNWR66sTliSuSzLk56zyg0/ap Y50w== X-Gm-Message-State: AGRZ1gINpZv29KYYxQUN50yrmQLqpbnBC3M3z7yCW/MzkdN5l4KrppW3 mcmQEu7IjYofc8WAbMXyoRPTU4i7qBVJEycCNyawDufF X-Google-Smtp-Source: AJdET5eHjvbvOJiA9F+D0MGGmQEBhHamaBxBAIs5YPQstnMtb/lovk9DOr9Ex38e6BXwxMREqePJIQw95ZHjWwm7Wxk= X-Received: by 2002:a24:5452:: with SMTP id t79-v6mr1683532ita.144.1541271105367; Sat, 03 Nov 2018 11:51:45 -0700 (PDT) MIME-Version: 1.0 References: <20181103151920.GZ79858@cicely7.cicely.de> In-Reply-To: <20181103151920.GZ79858@cicely7.cicely.de> From: Russell Haley Date: Sat, 3 Nov 2018 11:51:38 -0700 Message-ID: Subject: Re: GENERICSD images? To: ticso@cicely.de Cc: freebsd-arm , ticso@cicely7.cicely.de Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 18:51:46 -0000 On Sat, Nov 3, 2018 at 8:28 AM Bernd Walter wrote: > When and how would you use the GENERICSD images? > I assume they have a generic kernel, but do they need a specific u-boot > installed before they can get used? > What systems are supported? > Hi Bernd, I could be mistaken, but I think you are referring to the SD images that can be downloaded for various Arm boards found here: https://www.freebsd.org/where.html See the SD Image column for each currently supported FreeBSD version. These images are for "well supported" Arm boards and are an easy way to get up and running. To apply an image to an SD card, I typically use xzcat .img.xz | dd of=/dev/da0 bs=1M where ./dev/da0 is whatever device your SD card is found at (check dmesg if you're not sure. "geom part list /dev/da0" can also be helpful ) UFS will automatically grow the partition to the size of the SD card on first boot. If you wish to create your own image, you can look at crochet (a build too written in bash) or there is an excellent write up by Udit on building custom images here: http://uditagarwal.in/index.php/2018/04/17/building-freebsds-sdio-driver-for-beaglebone-black/ Hope that helps? Russ > > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Sat Nov 3 19:10:39 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8713710E1B1E for ; Sat, 3 Nov 2018 19:10:39 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 122B78DDC8 for ; Sat, 3 Nov 2018 19:10:38 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3JAZaH084472 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 3 Nov 2018 20:10:36 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541272237; bh=zjJ71RfgZYpPrY0WQjT4WOAZ/c9+nZSUAR5LX5De44I=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=pTQHSiOtUg+O+bsmL5kV337fEH0yYIXljwbM+XLkrH/CsJ4DRu1ufUrbtfqmF6yXY uIYMpatirZxQpwrDaciA8u6hHPbvwAO3MIa7qA841eLrIXwEy38GFG4o4/CuV3B2H8 I/3uivSabJv94nwedQzbZ4bnl7IE6FKWbOgsProY= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3JAXEJ002948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 20:10:33 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3JAXsW037993; Sat, 3 Nov 2018 20:10:33 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3JAWDm037992; Sat, 3 Nov 2018 20:10:32 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 20:10:32 +0100 From: Bernd Walter To: Russell Haley Cc: ticso@cicely.de, freebsd-arm , ticso@cicely7.cicely.de Subject: Re: GENERICSD images? Message-ID: <20181103191032.GA79858@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20181103151920.GZ79858@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 19:10:39 -0000 On Sat, Nov 03, 2018 at 11:51:38AM -0700, Russell Haley wrote: > On Sat, Nov 3, 2018 at 8:28 AM Bernd Walter wrote: > > > When and how would you use the GENERICSD images? > > I assume they have a generic kernel, but do they need a specific u-boot > > installed before they can get used? > > What systems are supported? > > > > Hi Bernd, > > I could be mistaken, but I think you are referring to the SD images that > can be downloaded for various Arm boards found here: > https://www.freebsd.org/where.html > > See the SD Image column for each currently supported FreeBSD version. These > images are for "well supported" Arm boards and are an easy way to get up > and running. To apply an image to an SD card, I typically use > xzcat .img.xz | dd of=/dev/da0 bs=1M > > where ./dev/da0 is whatever device your SD card is found at (check dmesg if > you're not sure. "geom part list /dev/da0" can also be helpful ) > > UFS will automatically grow the partition to the size of the SD card on > first boot. > > If you wish to create your own image, you can look at crochet (a build too > written in bash) or there is an excellent write up by Udit on building > custom images here: > http://uditagarwal.in/index.php/2018/04/17/building-freebsds-sdio-driver-for-beaglebone-black/ > > Hope that helps? No, I didn't ask about those images in general, I specifically asked about the use case of the GENERICSD image. AFAIK crochet isn't advised anymore. But the link is interesting, although unrelated to my question and it is specifically about beaglebones - Allwinner based boards have to be handled differently as they expect their bootcode at a specific media location. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 20:07:15 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E6EA10E2B49 for ; Sat, 3 Nov 2018 20:07:15 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 154E08F581 for ; Sat, 3 Nov 2018 20:07:14 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3K7BGc085962 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 3 Nov 2018 21:07:12 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541275633; bh=k2rm1RuskOH94FwquzgVL1SUNvJS6JyEzjt5h4EOTX4=; h=Date:From:To:Cc:Subject:Reply-To; b=pcVy5VdHmO+pDNkWOF4iK12zri94yisw6w8xHM1SSCQz1UUx42pyP4FA/q37+Y7uY m7ZkjUqIpiOHiHVqSHyLj3BPiIGaB4yNsmhntqxPrTNKFnyFdL0ZSlk9jAa3UnkhFd QzNbLAfw/D8gjAt58IenfLSDWWD0Ywn2GfsOkTqQ= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3K79rR004111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 21:07:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3K793F038257; Sat, 3 Nov 2018 21:07:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3K79X8038256; Sat, 3 Nov 2018 21:07:09 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 21:07:09 +0100 From: Bernd Walter To: freebsd-arm@freebsd.org Cc: Bernd Walter Subject: How to add custom dts entries Message-ID: <20181103200709.GB79858@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 20:07:15 -0000 For a raspberry (1B modell) I have the following patches: [92]cicely7> cat rpi.ds18b20.dts.patch Index: boot/fdt/dts/arm/rpi.dts =================================================================== --- boot/fdt/dts/arm/rpi.dts (revision 303469) +++ boot/fdt/dts/arm/rpi.dts (working copy) @@ -340,6 +348,11 @@ }; }; + onewire { + compatible = "w1-gpio"; + gpios = <&gpio 4 1>; + }; + power: regulator { compatible = "broadcom,bcm2835-power-mgr", "broadcom,bcm2708-power-mgr", [93]cicely7> cat rpi.apa102.dts.patch Index: boot/fdt/dts/arm/rpi.dts =================================================================== --- boot/fdt/dts/arm/rpi.dts (revision 303469) +++ boot/fdt/dts/arm/rpi.dts (working copy) @@ -292,6 +292,14 @@ broadcom,function = "ALT3"; }; }; + + spi0 { + apa102led0 { + compatible = "led,apa102"; + spi-chipselect = <0>; + }; + }; + usb { hub { compatible = "usb,hub", "usb,device"; And to install cd /usr/src/sys/modules/dtb/rpi make all install Obviously a few things have changed since then. We don't have overlay support yet, don't we? System is: # uname -a FreeBSD rpi-b 12.0-BETA3 FreeBSD 12.0-BETA3 r340039 RPI-B arm /usr/src is populated and my kernel driver itself build fine: # ls -la /boot/modules/ total 20 drwxr-xr-x 2 root wheel 512 Nov 3 20:54 . drwxr-xr-x 10 root wheel 1024 Nov 3 20:54 .. -r-xr-xr-x 1 root wheel 7080 Nov 3 20:54 apa102.ko -rw-r--r-- 1 root wheel 36 Nov 3 20:54 linker.hints -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 20:46:41 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9355710E3B30 for ; Sat, 3 Nov 2018 20:46:41 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2r.ore.mailhop.org (outbound2r.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 1714F6A2C1 for ; Sat, 3 Nov 2018 20:46:40 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1541277994; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=Tr6FkRr/8xwxdPF7vykgTiDgTcpDbPeQBV2mbBJKL7z4m+SPjiDuEVwIn72k8s2u50I4h1MQkWCQw 8+Npb+2o5hjmCZCGXsULHevufLyBR/QKkkjwCDREyz7EyxqJGkFi1PILamzPl1HaKtT9al1iiY6io3 kUFRLuvLI7S0ag5FKjMNzFu/oL+PFitz0S3ob85yZSiSndFL75mMSzei25L3FV1G4jZ4T6InQ8P/HO Nbfg/fymqUNY6hwsps5f0hgrmgEs24cS//GFhLmemeoZcV+1CECOUABv3msvkBv78Po3VTR/IvwLKi 76atSctCKsyrYXlJm9ibZtA6f4jreXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=ijmhEzbFc1hnWE3F+JuWsrvjszk22oZfHQ8uzYjf7Ls=; b=l6Cn0RaQY3lZXz0VOZjuMX09Euby46BRJksHKpyFUHjsS/QCfzryGxIywxV11T2VIPV1EYdw3Fgeh ilhuGkyWmof8UkEe1wX224tUBkrdZHKtX6k6uiLGzyXnYwy7g++VHvVdKkCzXIDpiXNSUN2PBkqHkL DZhKcyWYxqt76nK+Wm9Z3qUiAtmEJEbxXPSmKR0wHYpLmpbi1huozX5s0Wea9r7RmfF6R92w0Lsin8 xykq70XVARoSIV9R/6KX07MtjnWq1nb7KOCOi0kHzF0do27rjdXC8fnHTg/CAXEKhsLIBH7NkhfRYs Qj1u8VUG7iIN/1H1G4apZANAOo1QGgg== ARC-Authentication-Results: i=1; outbound2.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=ijmhEzbFc1hnWE3F+JuWsrvjszk22oZfHQ8uzYjf7Ls=; b=QdsmDUxSqVSCQc2zr+f0PIzpKlAwnJ3764N+IBDFGWdnw81SXBSS8cRiawPhNM9Q01KN1UAl7aJQT pXjSzU7XT/llnhpGJPMU0OwacjvZYBC7yjTdZ+9SsnvozVBcCkenDOs6L6DIAlnMamVH8/CqVzr9x9 oG6aeMgLGC1JxmBr2iGi4AAzQwBWlnqCM7+E8slslmlPxJwQa93Z4IzLC0K4mKI3nBUFOMp2nQOGUS 5QEa5bcs7ciTtXRXmhT4bJUtmBLyAPdEKjoPi5ATNZ2kQT0Jl77+nRVzBj0wOOeoytNFcw0kniSuNd yDxidZiJfCrTgu3LjBnAkJDe+2vxhpw== X-MHO-RoutePath: aGlwcGll X-MHO-User: 8ab07dd4-dfa9-11e8-a630-335f030b21f2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 8ab07dd4-dfa9-11e8-a630-335f030b21f2; Sat, 03 Nov 2018 20:46:32 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wA3KkUAq074741; Sat, 3 Nov 2018 14:46:30 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1541277990.52306.4.camel@freebsd.org> Subject: Re: How to add custom dts entries From: Ian Lepore To: ticso@cicely.de, freebsd-arm@freebsd.org Cc: Bernd Walter Date: Sat, 03 Nov 2018 14:46:30 -0600 In-Reply-To: <20181103200709.GB79858@cicely7.cicely.de> References: <20181103200709.GB79858@cicely7.cicely.de> 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.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 20:46:41 -0000 On Sat, 2018-11-03 at 21:07 +0100, Bernd Walter wrote: > For a raspberry (1B modell) I have the following patches: > [92]cicely7> cat rpi.ds18b20.dts.patch  > Index: boot/fdt/dts/arm/rpi.dts > =================================================================== > --- boot/fdt/dts/arm/rpi.dts    (revision 303469) > +++ boot/fdt/dts/arm/rpi.dts    (working copy) > @@ -340,6 +348,11 @@ >                 }; >         }; >   > +       onewire { > +               compatible = "w1-gpio"; > +               gpios = <&gpio 4 1>; > +       }; > + >         power: regulator { >                 compatible = "broadcom,bcm2835-power-mgr", >                              "broadcom,bcm2708-power-mgr", > [93]cicely7> cat rpi.apa102.dts.patch  > Index: boot/fdt/dts/arm/rpi.dts > =================================================================== > --- boot/fdt/dts/arm/rpi.dts    (revision 303469) > +++ boot/fdt/dts/arm/rpi.dts    (working copy) > @@ -292,6 +292,14 @@ >                                 broadcom,function = "ALT3"; >                         }; >                 }; > + > +               spi0 { > +                       apa102led0 { > +                               compatible = "led,apa102"; > +                               spi-chipselect = <0>; > +                       }; > +               }; > + >                 usb { >                         hub { >                                 compatible = "usb,hub", "usb,device"; > > And to install > cd /usr/src/sys/modules/dtb/rpi > make all install > > Obviously a few things have changed since then. > We don't have overlay support yet, don't we? > > System is: > # uname -a > FreeBSD rpi-b 12.0-BETA3 FreeBSD 12.0-BETA3 r340039 RPI-B  arm > /usr/src is populated and my kernel driver itself build fine: > # ls -la /boot/modules/ > total 20 > drwxr-xr-x   2 root  wheel   512 Nov  3 20:54 . > drwxr-xr-x  10 root  wheel  1024 Nov  3 20:54 .. > -r-xr-xr-x   1 root  wheel  7080 Nov  3 20:54 apa102.ko > -rw-r--r--   1 root  wheel    36 Nov  3 20:54 linker.hints > We do have overlay support now. I don't know much about using it, hopefully those who do will reply with details. There have also been updates to the SPI world. Your apa102led0 fdt node now requires a "spi-max-frequency" property, the value is the bus speed to use when communicating with that device, in Hz (different devices on the same bus can now have different speeds, and there is no concept of a default speed). Also, the chipsel number should be in a reg= property, but we still support spi-chipselect= too for backwards compatibility.  -- Ian From owner-freebsd-arm@freebsd.org Sat Nov 3 20:55:04 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2BB810E3DAA for ; Sat, 3 Nov 2018 20:55:03 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1EB6A68D; Sat, 3 Nov 2018 20:55:03 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3Ksxem086848 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 3 Nov 2018 21:55:00 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541278501; bh=7Ym40ZhGpZ+ngkwwDkXKaTRSlOBdgDM8IXETQj3B4yw=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=ZwWTKyL9blMHBQKonqlqDN2Q5S/I4fak0krtGRmQ37OHkEcJi09d4WHH6galBNOAv sXFH7vIPsvf1LQbTbZTz9RdU/uhnGyO+cx5dsDcs8aDm3vTgItOwr0z7m5oMkSAfol rAAZgvCKvbHNYFAQBXIwg7GPmAr7fibbCCbiip6k= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3KsuH3004643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 21:54:56 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3KsuEW038442; Sat, 3 Nov 2018 21:54:56 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3KstEu038441; Sat, 3 Nov 2018 21:54:55 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 21:54:55 +0100 From: Bernd Walter To: Ian Lepore Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: How to add custom dts entries Message-ID: <20181103205455.GD79858@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20181103200709.GB79858@cicely7.cicely.de> <1541277990.52306.4.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1541277990.52306.4.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 20:55:04 -0000 On Sat, Nov 03, 2018 at 02:46:30PM -0600, Ian Lepore wrote: > We do have overlay support now. I don't know much about using it, > hopefully those who do will reply with details. That's good to know. Hope for an answer too ;-) > There have also been updates to the SPI world. Your apa102led0 fdt node > now requires a "spi-max-frequency" property, the value is the bus speed > to use when communicating with that device, in Hz (different devices on > the same bus can now have different speeds, and there is no concept of > a default speed). Also, the chipsel number should be in a reg= > property, but we still support spi-chipselect= too for backwards > compatibility.  Ah, important information. I had been using dev.spi.0.clock to increase speed. Obviously dev.spi doesn't even exists anymore. Have to check about the CS, technically it is a dummy value anyway, since the APA102 LEDs don't have a chip select and are the only device connected to the SPI. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 21:02:04 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84A7710E8039 for ; Sat, 3 Nov 2018 21:02:04 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F1A886A966; Sat, 3 Nov 2018 21:02:03 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3L20hJ087044 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 3 Nov 2018 22:02:01 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541278922; bh=nwPO2g+QioEFqEp1AxCp14/XL+BvF14RLzWJ19kqQC8=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=P03dZntMn8cfGiS5XRr+o5PgBhdBBo/YhR88VklUd9o6Ku/xkbJrdUbIir29SSO9M G2l7pNVEn1mJYMgjFVXjyKkTqoXQpoACnZX5wI+Zklw0cZ4eN8rs/6aVXQB/9vo6Zj IQa6PIUVeIFubHQf1E1knFVl67oKIggOGfIdklCc= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3L1uUB004790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 22:01:56 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3L1uKL038522; Sat, 3 Nov 2018 22:01:56 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3L1ulQ038521; Sat, 3 Nov 2018 22:01:56 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 22:01:56 +0100 From: Bernd Walter To: Ian Lepore Cc: freebsd-arm@freebsd.org, Bernd Walter , ticso@cicely.de Subject: Re: How to add custom dts entries Message-ID: <20181103210156.GE79858@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20181103200709.GB79858@cicely7.cicely.de> <1541277990.52306.4.camel@freebsd.org> <20181103205455.GD79858@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20181103205455.GD79858@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 21:02:04 -0000 On Sat, Nov 03, 2018 at 09:54:55PM +0100, Bernd Walter wrote: > On Sat, Nov 03, 2018 at 02:46:30PM -0600, Ian Lepore wrote: > > We do have overlay support now. I don't know much about using it, > > hopefully those who do will reply with details. > > That's good to know. > Hope for an answer too ;-) > > > There have also been updates to the SPI world. Your apa102led0 fdt node > > now requires a "spi-max-frequency" property, the value is the bus speed > > to use when communicating with that device, in Hz (different devices on > > the same bus can now have different speeds, and there is no concept of > > a default speed). Also, the chipsel number should be in a reg= > > property, but we still support spi-chipselect= too for backwards > > compatibility.  > > Ah, important information. > I had been using dev.spi.0.clock to increase speed. > Obviously dev.spi doesn't even exists anymore. > Have to check about the CS, technically it is a dummy value anyway, > since the APA102 LEDs don't have a chip select and are the only > device connected to the SPI. I see, there is some overlay setup done for spigen(4). Didn't know we have userland spi support already. Nice addition. However, the DS18B20/ow_temp(4) still needs the onewire setup. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 21:04:49 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A49010E813A for ; Sat, 3 Nov 2018 21:04:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 1C9E06AA6B for ; Sat, 3 Nov 2018 21:04:48 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1541279081; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=UiKIedxjYILs6nk0if2sxLtXSwIbkNjbatUW8vS2AR2fzVilqM0Zo7uO2JqjkP/Cbtf+EIen0mbqh y9gpmMzsQtefxVvCasrsKo2+RcFH0dJA08Xi5M4bV8545lvEHvIcOiPF5AJqZDwK2ZvhsDJz1lPj6e 8Yzft5Uy0R8BD4K59cU7wSY/gNLAfNtVEriHf15Uk3BR6K5EtGfGE0pkeyatvIkUkDadIOfAS3ItJ1 SCIsTFKYX8nN4N+11eQhOKGc/ivRPdk76Vr3ifGzktC3m4D0lARlXlrYIBwvYyfZAEQu+zYNrCPLtM vSAWP2q/PyzUEHdlw+smOKH+dc33fWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=bQGvS7IAeoZuei/ihpVxgTwYGUdScQeYcKbJtg8facs=; b=qWp3Q1zGKjT14ybJMpeyUOY0bt13CMmBG3hNtgptt2WDnzVyCuJoqAzvHib3bcKPTbzpLXgPZB2Fu ixubUXSf8b8Vve0hG7dVhYQGtOJcf6hAt6PaScW4V25GLrV4775CG6ARshXf443A3DKkuMXtFl126B J4Aon07L2kPWzpagN9crg3Bd7ls/0mky2CUN8fi0EOUsox0qOGoSF2rb1J8Kf0XTVgb79b4ZBWvhpi uEMuLML9ViDhA+YWBsvf0BL32hxAn0nm7PFjXgJ0l37kYcZefun/croHUD1v9wghjQu8Omlf6N+I0v OvxQKJMDRCLeYRxVI2Wn7cXZUHLbhlA== ARC-Authentication-Results: i=1; outbound1.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=bQGvS7IAeoZuei/ihpVxgTwYGUdScQeYcKbJtg8facs=; b=kElH9eRAcVY8KBqn/+hxZglIrd2W7lc/zVqEOUyW3GQJHuXv/RGIgZGXu0z+JYlKjkzfIeTQhC2rP FFlIm1teemxsCtqRpKt6GBAotMC/JZOcc/4sRuCFGRdIPW0GrOJLJyIbkZiDJqed61Y/CqRhTDXq/k FR+/U0jxKBUHtqkGVnImspwX+HAcdmFEjq9W2+w+gyMyIFM1D03fRuOEn3HNTS1FV8IoNJMBDjPZgo dZUInrpQk3lFo+HoAt80h0NAxV0vUT9G3ZihD3zZBxgnBDGvjiUkdDTj+VQdIG36ZEqvA2mYCNunbp iHcTmPdFq0eQOXfGpzCW7AILj0zbFLg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 13d9247d-dfac-11e8-a93b-310333596487 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 13d9247d-dfac-11e8-a93b-310333596487; Sat, 03 Nov 2018 21:04:40 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wA3L4dm1074798; Sat, 3 Nov 2018 15:04:39 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1541279079.52306.8.camel@freebsd.org> Subject: Re: How to add custom dts entries From: Ian Lepore To: ticso@cicely.de Cc: freebsd-arm@freebsd.org, Bernd Walter Date: Sat, 03 Nov 2018 15:04:39 -0600 In-Reply-To: <20181103205455.GD79858@cicely7.cicely.de> References: <20181103200709.GB79858@cicely7.cicely.de> <1541277990.52306.4.camel@freebsd.org> <20181103205455.GD79858@cicely7.cicely.de> 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.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 21:04:49 -0000 On Sat, 2018-11-03 at 21:54 +0100, Bernd Walter wrote: > On Sat, Nov 03, 2018 at 02:46:30PM -0600, Ian Lepore wrote: > > > > We do have overlay support now. I don't know much about using it, > > hopefully those who do will reply with details. > That's good to know. > Hope for an answer too ;-) > > > > > There have also been updates to the SPI world. Your apa102led0 fdt > > node > > now requires a "spi-max-frequency" property, the value is the bus > > speed > > to use when communicating with that device, in Hz (different > > devices on > > the same bus can now have different speeds, and there is no concept > > of > > a default speed). Also, the chipsel number should be in a reg= > > property, but we still support spi-chipselect= too for backwards > > compatibility.  > Ah, important information. > I had been using dev.spi.0.clock to increase speed. > Obviously dev.spi doesn't even exists anymore. > Have to check about the CS, technically it is a dummy value anyway, > since the APA102 LEDs don't have a chip select and are the only > device connected to the SPI. > The sysctl nodes should still exist, but now they're all read-only values that just tell you about the current transfer (or the last one to complete), since all those values can change on each transfer now depending on how individual devices are configured. Also, there is now a spi(8) program that lets you do spi transfers and to some degree manipulate the transfer properties (bus polarity/phase, speed, etc) from the command line. -- Ian From owner-freebsd-arm@freebsd.org Sat Nov 3 21:18:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3FE510E8643 for ; Sat, 3 Nov 2018 21:18:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 346ED6AFCE for ; Sat, 3 Nov 2018 21:18:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io1-xd31.google.com with SMTP id p83-v6so3830819iod.12 for ; Sat, 03 Nov 2018 14:18:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k27mcfGENl4+t9VQnUHbVZiHY2YxfuUc2qDyBqYxh2s=; b=tVWPILNeUFTWViGQqN9kk4XKAkd3ROjWcNb5Sawwo4qVozGaBrWmF35Y5PTHu6WUBP pKGntqQgHKLPedG7PPnjpRxNR/Qy2/I8e4U/yNF0ehH9VZZjkcwRd+DBikMA1Qb6Zwu8 8lmWCztsIiNqsdsQWQfDPbmFSWrNrYfEKWd2aQiXq3SU/rlxcotXsaRtCejhcw1L5ojU 842t5P+DdSR9kFeup1IBl4VsX4SSU/sjcjGb2D7m8Twp7pKLlvoOWaEjDzeNQu7Z3E4g uFUmNJwl2/Nlxs9HxC7M3bn4yWKW/aFfZWoBTgZ9sBIAplG59ru+ySEtlR7sPbcvVDsn QYmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k27mcfGENl4+t9VQnUHbVZiHY2YxfuUc2qDyBqYxh2s=; b=O/C7uMl0ze+yL0xRUI2RspvbMn/e1yj01V5S3johZ5suHXdia2na8QSsk1BNpB/DKl +TGqQ/FkCDkKuqy/44+QKNpaQv11RQSrgqubjZej366l+uFCyyBHL14FZ1IH24qaeCay m1gMGJFtxSmo9TzH7ne2yUnnwKW45xoBAxMSYaPFiQrSNgFrK9UvtknMxVHIjHjZvtv2 /yXHJSBmqACzFD5XPVorCag5fIq430KtDFKPf9BxOU2Vh7HYAFO9G1/lmTKI7izH7zOa SDl5AUch74vzs06iMVIeAf+HjA2NTzDV7w9I25X+OuwBlD0Ir0YIIPZt/rZt9rfqQGEU c1Yg== X-Gm-Message-State: AGRZ1gKw0Pv4wTFkPsyBRWZpUluZTgeD95a+fYMutWm0/85sdt84s7pe EOB9IKdExecF8dD/scdtZyFv/BUvi0p8NXc9G4fUhg== X-Google-Smtp-Source: AJdET5dCL+p0o4nbkPQyQ4yJJwchuEhxi8osBs56GEYTV4JsX5qwCCtRjtmhTcIXHC/RPBb0clj/8Emh3cgfA1QcbXU= X-Received: by 2002:a6b:7809:: with SMTP id j9-v6mr6324810iom.299.1541279912140; Sat, 03 Nov 2018 14:18:32 -0700 (PDT) MIME-Version: 1.0 References: <20181103151920.GZ79858@cicely7.cicely.de> <20181103191032.GA79858@cicely7.cicely.de> In-Reply-To: <20181103191032.GA79858@cicely7.cicely.de> From: Warner Losh Date: Sat, 3 Nov 2018 15:18:21 -0600 Message-ID: Subject: Re: GENERICSD images? To: ticso@cicely.de Cc: Russell Haley , "freebsd-arm@freebsd.org" , Bernd Walter Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 21:18:33 -0000 On Sat, Nov 3, 2018 at 1:11 PM Bernd Walter wrote: > On Sat, Nov 03, 2018 at 11:51:38AM -0700, Russell Haley wrote: > > On Sat, Nov 3, 2018 at 8:28 AM Bernd Walter > wrote: > > > > > When and how would you use the GENERICSD images? > > > I assume they have a generic kernel, but do they need a specific u-boot > > > installed before they can get used? > > > What systems are supported? > > > > > > > Hi Bernd, > > > > I could be mistaken, but I think you are referring to the SD images that > > can be downloaded for various Arm boards found here: > > https://www.freebsd.org/where.html > > > > See the SD Image column for each currently supported FreeBSD version. > These > > images are for "well supported" Arm boards and are an easy way to get up > > and running. To apply an image to an SD card, I typically use > > xzcat .img.xz | dd of=/dev/da0 bs=1M > > > > where ./dev/da0 is whatever device your SD card is found at (check dmesg > if > > you're not sure. "geom part list /dev/da0" can also be helpful ) > > > > UFS will automatically grow the partition to the size of the SD card on > > first boot. > > > > If you wish to create your own image, you can look at crochet (a build > too > > written in bash) or there is an excellent write up by Udit on building > > custom images here: > > > http://uditagarwal.in/index.php/2018/04/17/building-freebsds-sdio-driver-for-beaglebone-black/ > > > > Hope that helps? > > No, I didn't ask about those images in general, I specifically asked about > the use case of the GENERICSD image. > AFAIK crochet isn't advised anymore. > But the link is interesting, although unrelated to my question and it is > specifically about beaglebones - Allwinner based boards have to be handled > differently as they expect their bootcode at a specific media location. > We now have a GENERIC kernel. This image is built with that kernel. You're expected to roll your own u-boot into this image for the board you are using. There are several u-boot ports that are known to work (or worked at one time). There's a script that will add u-boot for the board based on metadata the port installs, but I'm having trouble finding it at the moment to give you more specifics... Warner From owner-freebsd-arm@freebsd.org Sat Nov 3 21:20:38 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37A4510E8715 for ; Sat, 3 Nov 2018 21:20:38 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B7A3C6B08B; Sat, 3 Nov 2018 21:20:37 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3LKY66087382 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 3 Nov 2018 22:20:35 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541280036; bh=qsygN95FhoEY5x5BWLe5Sanp6OyhRR4cAmlPrYEGEmU=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=PZoO6m3BXj75dbFik2c1gq4gcVo4SnlBwWI/b+YPIaJuQ1VMjN2vVnSmInoptt64Q Z++jkJm3KfkZnE/teesMd5VMVwROo0JLfu6RaeOC06Zuzh+xcWvTsXsxid9qHnBldA ZiZVBgQabc0yxmrZyr/YJ0QmJv5YLnPKLR8Lqusk= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3LKWRd005050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 22:20:32 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3LKVCZ038585; Sat, 3 Nov 2018 22:20:31 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3LKVwm038584; Sat, 3 Nov 2018 22:20:31 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 22:20:31 +0100 From: Bernd Walter To: Ian Lepore Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: How to add custom dts entries Message-ID: <20181103212031.GF79858@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20181103200709.GB79858@cicely7.cicely.de> <1541277990.52306.4.camel@freebsd.org> <20181103205455.GD79858@cicely7.cicely.de> <1541279079.52306.8.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1541279079.52306.8.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 21:20:38 -0000 On Sat, Nov 03, 2018 at 03:04:39PM -0600, Ian Lepore wrote: > On Sat, 2018-11-03 at 21:54 +0100, Bernd Walter wrote: > > On Sat, Nov 03, 2018 at 02:46:30PM -0600, Ian Lepore wrote: > > > > > > We do have overlay support now. I don't know much about using it, > > > hopefully those who do will reply with details. > > That's good to know. > > Hope for an answer too ;-) > > > > > > > > There have also been updates to the SPI world. Your apa102led0 fdt > > > node > > > now requires a "spi-max-frequency" property, the value is the bus > > > speed > > > to use when communicating with that device, in Hz (different > > > devices on > > > the same bus can now have different speeds, and there is no concept > > > of > > > a default speed). Also, the chipsel number should be in a reg= > > > property, but we still support spi-chipselect= too for backwards > > > compatibility.  > > Ah, important information. > > I had been using dev.spi.0.clock to increase speed. > > Obviously dev.spi doesn't even exists anymore. > > Have to check about the CS, technically it is a dummy value anyway, > > since the APA102 LEDs don't have a chip select and are the only > > device connected to the SPI. > > > > The sysctl nodes should still exist, but now they're all read-only > values that just tell you about the current transfer (or the last one > to complete), since all those values can change on each transfer now > depending on how individual devices are configured. At least not for me. > Also, there is now a spi(8) program that lets you do spi transfers and > to some degree manipulate the transfer properties (bus polarity/phase, > speed, etc) from the command line. Saw that - very nice. I should use spigen, as my kernel driver is nothing more than a wrapper to a devicenode. However loading the spigen module won't create any /dev/spigen* nodes. spi drivers are all loaded: [60]rpi-b# kldstat -v | grep spi 43 spi/spibus 123 simplebus/bcm2835_spi 42 spi/ofw_spibus 4 1 0xd2f00000 a000 spigen.ko (/boot/kernel/spigen.ko) 129 spibus/spigen But there is no mention of any spi in dmesg and devinfo. [68]rpi-b# devinfo nexus0 ofwbus0 simplebus0 systimer0 bcm_dma0 intc0 bcmwd0 bcmrng0 mbox0 gpio0 gpiobus0 gpioc0 uart0 bcm283x_dwcotg0 usbus0 uhub0 uhub1 smsc0 miibus0 ukphy0 sdhci_bcm0 mmc0 mmcsd0 fb0 fbd0 vchiq0 pcm0 gpioled0 cryptosoft0 And I still need to setup the onewire bus. This is for a LED matrix and I really need the temperature sensors to protect the LEDs from damage. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 21:41:59 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E68910E91F8 for ; Sat, 3 Nov 2018 21:41:59 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 D6BB06BB35 for ; Sat, 3 Nov 2018 21:41:58 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1541280347; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=tP2FKbOzfaD7X8Q7gLCAixkFKhYa9E9Y+6A6FQeCxOwUH8mXB7ktDq1JjKqIZZJdGvQK/278y0d1F ejHXHaH7eC6ECQsRBiYFfxdRw14R1PSCJI02UfaBwL8yLH03U746s5VI80XXnNrJ99ACtUdQVsAHIL 0VWD6Chj3ikpbb8v98gbNy/TYKYtwt4D1Ue+LeSQjsRkNALpXoe14Ra9vIq0ITwHYQe9Eq8Ovb+qjc Wf2GG1sRRH0C1Dxj/f0MdLMZE1GdOAgjJ2bXXTRh1durwP93AiABOw//73SsjxGRS0sgQKwyGuY+11 sZb7BnbQ34Kq/qnQSkbPqg+3YNSPxcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=AWOEOMko73breKowaTRboMLcWP2x48GEX2IhlKfFoOY=; b=INP5r1ZO8lxNCHM7a2R6Yl1MhNiAo6xZFzVALbEug+9tVBGyO3uULyuo44Ogt/Nt5tKy59MtPNEXr ecC+wwdXvBimnrEqYrjEgnLl1go0mFDRf6u2AXNH5Q5kuwmq/Xt6wlsi18yKrcY2jm6JSoRr0/6tFJ 8vPqJKA/qHPp+olFge+Pdyawti7IM3l8YF0OdMpeby77tQbxfmkjoRcSHxurFpDchdnmSukZ76rcJs RxMDINGkktk9XodXm58AApm+Y8izhaDlI6sJ0sI2KSrf3aFW5VmzNHXJgmNCVXpHjCtXPK96SoNIHL kWoa15Jkmmb7FFcQ0KPgK3q92XLzCuQ== ARC-Authentication-Results: i=1; outbound1.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=AWOEOMko73breKowaTRboMLcWP2x48GEX2IhlKfFoOY=; b=ui1LCqzYjwMHcIazOUuxt0beFQ5hZq8ae1gBAyi+dHNxjkVoEoMwlLAa3pmoqrW3ph7xZ6o7H4t2/ JvEsED3ktfHDKMqor+A0jujd3KF6khby2jw1f4nTquB5VHrQBcAbC2u7qlLyHwX/Aw4tUZ/FOLShGg ew1na33HGRRKsXnuKSfiSiGD1Lh6A87Oh1vIc+mgEi8JI6zglijnJaNyTqNCphFw1wonk9iSac2sx8 Y3MZpvbMO0TBjs0fusnuAQQpDDndD25O/97aqJFTjd+f8sxwSK8ZmZFhIU3EbMh6b+3YAbroXw11Rp 686O48aCqVPMS0chBxIPiQ7oOl4BmRQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: 027a5644-dfaf-11e8-9048-075f73944867 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 027a5644-dfaf-11e8-9048-075f73944867; Sat, 03 Nov 2018 21:25:42 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wA3LPc3T074830; Sat, 3 Nov 2018 15:25:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1541280338.52306.9.camel@freebsd.org> Subject: Re: How to add custom dts entries From: Ian Lepore To: ticso@cicely.de Cc: freebsd-arm@freebsd.org, Bernd Walter Date: Sat, 03 Nov 2018 15:25:38 -0600 In-Reply-To: <20181103212031.GF79858@cicely7.cicely.de> References: <20181103200709.GB79858@cicely7.cicely.de> <1541277990.52306.4.camel@freebsd.org> <20181103205455.GD79858@cicely7.cicely.de> <1541279079.52306.8.camel@freebsd.org> <20181103212031.GF79858@cicely7.cicely.de> 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.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 21:41:59 -0000 On Sat, 2018-11-03 at 22:20 +0100, Bernd Walter wrote: > On Sat, Nov 03, 2018 at 03:04:39PM -0600, Ian Lepore wrote: > > > > On Sat, 2018-11-03 at 21:54 +0100, Bernd Walter wrote: > > > > > > On Sat, Nov 03, 2018 at 02:46:30PM -0600, Ian Lepore wrote: > > > > > > > > > > > > We do have overlay support now. I don't know much about using > > > > it, > > > > hopefully those who do will reply with details. > > > That's good to know. > > > Hope for an answer too ;-) > > > > > > > > > > > > > > > There have also been updates to the SPI world. Your apa102led0 > > > > fdt > > > > node > > > > now requires a "spi-max-frequency" property, the value is the > > > > bus > > > > speed > > > > to use when communicating with that device, in Hz (different > > > > devices on > > > > the same bus can now have different speeds, and there is no > > > > concept > > > > of > > > > a default speed). Also, the chipsel number should be in a reg= > > > > property, but we still support spi-chipselect= too for > > > > backwards > > > > compatibility.  > > > Ah, important information. > > > I had been using dev.spi.0.clock to increase speed. > > > Obviously dev.spi doesn't even exists anymore. > > > Have to check about the CS, technically it is a dummy value > > > anyway, > > > since the APA102 LEDs don't have a chip select and are the only > > > device connected to the SPI. > > > > > The sysctl nodes should still exist, but now they're all read-only > > values that just tell you about the current transfer (or the last > > one > > to complete), since all those values can change on each transfer > > now > > depending on how individual devices are configured. > At least not for me. > > > > > Also, there is now a spi(8) program that lets you do spi transfers > > and > > to some degree manipulate the transfer properties (bus > > polarity/phase, > > speed, etc) from the command line. > Saw that - very nice. > I should use spigen, as my kernel driver is nothing more than a > wrapper > to a devicenode. > However loading the spigen module won't create any /dev/spigen* > nodes. > spi drivers are all loaded: > [60]rpi-b# kldstat -v | grep spi >                  43 spi/spibus >                 123 simplebus/bcm2835_spi >                  42 spi/ofw_spibus >  4    1 0xd2f00000     a000 spigen.ko (/boot/kernel/spigen.ko) >                 129 spibus/spigen > But there is no mention of any spi in dmesg and devinfo. > [68]rpi-b# devinfo > nexus0 >   ofwbus0 >     simplebus0 >       systimer0 >       bcm_dma0 >       intc0 >       bcmwd0 >       bcmrng0 >       mbox0 >       gpio0 >         gpiobus0 >         gpioc0 >       uart0 >       bcm283x_dwcotg0 >         usbus0 >           uhub0 >             uhub1 >               smsc0 >                 miibus0 >                   ukphy0 >       sdhci_bcm0 >         mmc0 >           mmcsd0 >       fb0 >         fbd0 >       vchiq0 >         pcm0 >     gpioled0 >   cryptosoft0 > > And I still need to setup the onewire bus. > This is for a LED matrix and I really need the temperature sensors to > protect the LEDs from damage. > Add a status = "okay" to the spi node in your patch/overlay. -- Ian From owner-freebsd-arm@freebsd.org Sat Nov 3 22:55:52 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7478110EB769 for ; Sat, 3 Nov 2018 22:55:52 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B31B6FD6F for ; Sat, 3 Nov 2018 22:55:50 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id wA3MtlBt089178 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 3 Nov 2018 23:55:48 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1541285748; bh=KyZQaaN09m1bC/pVzeOAuq2W+/VWmVG2RrqqaxbO1to=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=ve3WXL/tReDJLyrEQFqL+7ReXzGUJeMVn8FS/h4DwguAN6o8OzfCSCZZb6MXHVTE1 9QH/x9mIJOHbSJ3VMQMgvzWri6fnGbDjYI7MT5jJ6+QFmvhMJcXzV3JkZoWVdCbREo gIJE7uZ+LkAbox1+JltT+4olzdh/kSJ1TLM7/W1w= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id wA3Mtitb006471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2018 23:55:44 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id wA3Mti98039012; Sat, 3 Nov 2018 23:55:44 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id wA3Mth2U039011; Sat, 3 Nov 2018 23:55:43 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Nov 2018 23:55:43 +0100 From: Bernd Walter To: Warner Losh Cc: ticso@cicely.de, Russell Haley , "freebsd-arm@freebsd.org" , Bernd Walter Subject: Re: GENERICSD images? Message-ID: <20181103225543.GH79858@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20181103151920.GZ79858@cicely7.cicely.de> <20181103191032.GA79858@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 1B31B6FD6F X-Spamd-Result: default: False [1.19 / 200.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[cicely.de]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; MX_GOOD(-0.01)[mx1.bwct.de]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_SPF_NA(0.00)[]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.02)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 22:55:52 -0000 On Sat, Nov 03, 2018 at 03:18:21PM -0600, Warner Losh wrote: > On Sat, Nov 3, 2018 at 1:11 PM Bernd Walter wrote: > > > On Sat, Nov 03, 2018 at 11:51:38AM -0700, Russell Haley wrote: > > > On Sat, Nov 3, 2018 at 8:28 AM Bernd Walter > > wrote: > > > > > > > When and how would you use the GENERICSD images? > > > > I assume they have a generic kernel, but do they need a specific u-boot > > > > installed before they can get used? > > > > What systems are supported? > > > > > > > > > > Hi Bernd, > > > > > > I could be mistaken, but I think you are referring to the SD images that > > > can be downloaded for various Arm boards found here: > > > https://www.freebsd.org/where.html > > > > > > See the SD Image column for each currently supported FreeBSD version. > > These > > > images are for "well supported" Arm boards and are an easy way to get up > > > and running. To apply an image to an SD card, I typically use > > > xzcat .img.xz | dd of=/dev/da0 bs=1M > > > > > > where ./dev/da0 is whatever device your SD card is found at (check dmesg > > if > > > you're not sure. "geom part list /dev/da0" can also be helpful ) > > > > > > UFS will automatically grow the partition to the size of the SD card on > > > first boot. > > > > > > If you wish to create your own image, you can look at crochet (a build > > too > > > written in bash) or there is an excellent write up by Udit on building > > > custom images here: > > > > > http://uditagarwal.in/index.php/2018/04/17/building-freebsds-sdio-driver-for-beaglebone-black/ > > > > > > Hope that helps? > > > > No, I didn't ask about those images in general, I specifically asked about > > the use case of the GENERICSD image. > > AFAIK crochet isn't advised anymore. > > But the link is interesting, although unrelated to my question and it is > > specifically about beaglebones - Allwinner based boards have to be handled > > differently as they expect their bootcode at a specific media location. > > > > We now have a GENERIC kernel. This image is built with that kernel. You're > expected to roll your own u-boot into this image for the board you are > using. There are several u-boot ports that are known to work (or worked at > one time). That's a good simplification. I already had known about the GENERIC kernel, but this image was new for me as I wondered how it is handling the board specific boot code. > There's a script that will add u-boot for the board based on metadata the > port installs, but I'm having trouble finding it at the moment to give you > more specifics... Would be cool to know when you or someone else find it. So far searching for GENERICSD only showed several fileservers. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Sat Nov 3 23:24:24 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EED1710EC306 for ; Sat, 3 Nov 2018 23:24:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2r.ore.mailhop.org (outbound2r.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 F3E4670A03 for ; Sat, 3 Nov 2018 23:24:22 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1541287461; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=sRMB5IczsNyTkLUxmfxsTMCJLFNrOnqnw9vzhPQ1ASv5skQimCYaBo/XWjfL6TbruClA0jWMdiy1M Y2IwnkMXDHIKhx5pKgcYSZiqrmfclGlsOcJjJMgDi3i+vxLdkcswh1vcGuRIgpQSe9n8+0r3aAopQF YClJfa+7xhtbqjgOU2q6lqBdb2B57dcfkY1TnCtA7NeCDO5U+birxML3Q3T/09qVAJKX55As11i9U3 hPU3svetzGmRwJDGS6MQ6V2CURg4gFFaDi6APq1BnkwXhirlI7XMupvK1budt4H27l1Jx9HlpAknQX dX/kNhLjbKGbP4AecgqfGbfy97dWxPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=bXa6wshKCU9nfGjFs5Xp1rJKAIBU+IP0mMYX6tLInd8=; b=ngWfZn2z/kyAA+ewT8Bcr8X9U0rixbq/uxWFss9NiZUVttWHu+L9n1Qd+YC3LrPls2Lucpz6jGh82 JjffOt72Gl3zVeUvfdclXd2Vm7ZUE4pyHCAVDj1xjGYuZUGLGZ7WIKyA0IckedE7O3sA8PPyS2I9YY hSfqQesmguvlJ7FKIrO/NRa8J61QMs7+7RuLMcGsEXX6PBiS70PW4q9Q6+U/ZNtQhH3eN5SFh7nBT4 2+0IjFUE67sciJJ3Lx/Kze1YmpjZ8pXjferJlTcQ1ENUodhPgzl+lDZiQ63H15DAHOSB5uSbqdKGuj PuaSohmWmH5DUrYAKvTxbmV6ceUUMDg== ARC-Authentication-Results: i=1; outbound2.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=bXa6wshKCU9nfGjFs5Xp1rJKAIBU+IP0mMYX6tLInd8=; b=Bl7+cZyRFhoeadPLQAA+dwvwfG8kdXCH6uZNDQYMtV/1Xfw4irwFUVCYSBlckc5a/MdMsz+SXti4E Ui9UL/XzdRn8X+dupwhjZKolpWAUWV+a3k2u6zRbtSJFG7CLmBj20zy0S+r/y8WILXw9VJbWI5R/vl zw3D12hQW5VOhFYHH1u6y6wLikDR2352ecGlTGq0EccRR4mj7/lA/CZGpIZEAtZ5SX2dvRhIdh1UWE g+vwreeL1k5Iq4d8oJFFjh+kCGhImphm0dQ0MmMAggS6ztdFI4qpsxMvxLpnEpFEvJXdb3eoBNRlmS 7PxN0vYv3cvo/vQp/9ZyAiUEI7WuYEw== X-MHO-RoutePath: aGlwcGll X-MHO-User: 9598efb6-dfbf-11e8-a630-335f030b21f2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 9598efb6-dfbf-11e8-a630-335f030b21f2; Sat, 03 Nov 2018 23:24:20 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wA3NOHQn074972; Sat, 3 Nov 2018 17:24:17 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1541287457.52306.13.camel@freebsd.org> Subject: Re: GENERICSD images? From: Ian Lepore To: ticso@cicely.de, Warner Losh Cc: "freebsd-arm@freebsd.org" , Bernd Walter Date: Sat, 03 Nov 2018 17:24:17 -0600 In-Reply-To: <20181103225543.GH79858@cicely7.cicely.de> References: <20181103151920.GZ79858@cicely7.cicely.de> <20181103191032.GA79858@cicely7.cicely.de> <20181103225543.GH79858@cicely7.cicely.de> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: F3E4670A03 X-Spamd-Result: default: False [0.25 / 200.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[outbound.mailhop.org]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; R_SPF_SOFTFAIL(0.00)[~all]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mx66.freebsd.org]; DKIM_TRACE(0.00)[outbound.mailhop.org:+]; RCVD_IN_DNSWL_NONE(0.00)[228.129.200.54.list.dnswl.org : 127.0.20.0]; RECEIVED_SPAMHAUS_PBL(0.00)[60.211.177.67.zen.spamhaus.org : 127.0.0.10]; IP_SCORE(0.06)[asn: 16509(0.38), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:16509, ipnet:54.200.0.0/15, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_ALLOW(-1.00)[i=1] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2018 23:24:24 -0000 On Sat, 2018-11-03 at 23:55 +0100, Bernd Walter wrote: > On Sat, Nov 03, 2018 at 03:18:21PM -0600, Warner Losh wrote: > > > > On Sat, Nov 3, 2018 at 1:11 PM Bernd Walter > e> wrote: > > > > > > > > On Sat, Nov 03, 2018 at 11:51:38AM -0700, Russell Haley wrote: > > > > > > > > On Sat, Nov 3, 2018 at 8:28 AM Bernd Walter > > > ly.de> > > > wrote: > > > > > > > > > > > > > > > > > > When and how would you use the GENERICSD images? > > > > > I assume they have a generic kernel, but do they need a > > > > > specific u-boot > > > > > installed before they can get used? > > > > > What systems are supported? > > > > > > > > > Hi Bernd, > > > > > > > > I could be mistaken, but I think you are referring to the SD > > > > images that > > > > can be downloaded for various Arm boards found here: > > > > https://www.freebsd.org/where.html > > > > > > > > See the SD Image column for each currently supported FreeBSD > > > > version. > > > These > > > > > > > > images are for "well supported" Arm boards and are an easy way > > > > to get up > > > > and running. To apply an image to an SD card, I typically use > > > > xzcat .img.xz | dd of=/dev/da0 bs=1M > > > > > > > > where ./dev/da0 is whatever device your SD card is found at > > > > (check dmesg > > > if > > > > > > > > you're not sure. "geom part list /dev/da0" can also be helpful > > > > ) > > > > > > > > UFS will automatically grow the partition to the size of the SD > > > > card on > > > > first boot. > > > > > > > > If you wish to create your own image, you can look at crochet > > > > (a build > > > too > > > > > > > > written in bash) or there is an excellent write up by Udit on > > > > building > > > > custom images here: > > > > > > > http://uditagarwal.in/index.php/2018/04/17/building-freebsds-sdio > > > -driver-for-beaglebone-black/ > > > > > > > > > > > > Hope that helps? > > > No, I didn't ask about those images in general, I specifically > > > asked about > > > the use case of the GENERICSD image. > > > AFAIK crochet isn't advised anymore. > > > But the link is interesting, although unrelated to my question > > > and it is > > > specifically about beaglebones - Allwinner based boards have to > > > be handled > > > differently as they expect their bootcode at a specific media > > > location. > > > > > We now have a GENERIC kernel. This image is built with that kernel. > > You're > > expected to roll your own u-boot into this image for the board you > > are > > using. There are several u-boot ports that are known to work (or > > worked at > > one time). > That's a good simplification. > I already had known about the GENERIC kernel, but this image was new > for > me as I wondered how it is handling the board specific boot code. > > > > > There's a script that will add u-boot for the board based on > > metadata the > > port installs, but I'm having trouble finding it at the moment to > > give you > > more specifics... > Would be cool to know when you or someone else find it. > So far searching for GENERICSD only showed several fileservers. > A cool thing that could come of this is a website where you choose your board type and it creates on the fly a burnable image for you to download from the GENERICSD plus the board-specific boot stuff. -- Ian