From owner-freebsd-arm@freebsd.org Wed Jun 3 23:40:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B18292F7797 for ; Wed, 3 Jun 2020 23:40:56 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49cllq5X4Lz441G for ; Wed, 3 Jun 2020 23:40:55 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591227653; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=T9nOyiaNkn1sYmDNl3dyXpm9UQp29YWUIgmA2zEtgEU=; b=XjHEBV+JCVkQFM1HfRcwRX7veTDZpVfNzeI9xk9/GbOGupR9PEmvfii84+KJH3NqRPSTg9 8oyq64iBkXSB+7MUwyCYqCB8xWw7/6eJ8316VYK+9WR8wpulqqWB4QUGRcBtmq6jNvqiv4 Tbt22+9K0c1aEP4opOYW1ZzzQjOHpFQ= Date: Wed, 03 Jun 2020 23:40:52 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> References: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49cllq5X4Lz441G X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=XjHEBV+J; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.55 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.004]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.03)[-1.035]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.52)[-0.516]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2020 23:40:56 -0000 June 3, 2020 7:09 PM, "myfreeweb" wrote:=0A= =0A> On June 3, 2020 1:37:34 PM UTC, Dan Kotowski wrote:=0A> =0A>>>>> I've sent a link to a known firmware build = before:=0A>>>>> https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhA= ClJGvErK/view=0A>>>>> Have you tried it? Any difference in FreeBSD/NetBSD= , with NVMe?=0A>>>> =0A>>>> I decided to go back to the UEFI sources and = have found some differences that I think need to be=0A>>> reconciled befo= re moving forward. That said, I'm not an ACPI wizard by any means - for m= e it's=0A>>> low-level mage spells at best...=0A>>>> In https://github.co= m/SolidRun/edk2-platforms we have 2 different branches that SolidRun seem= s to=0A>>> use:=0A>>>> =0A>>>> 1. LSDK-19.09-sr=0A>>>> 2. master-lx2160a= =0A>>>> =0A>>>> I've been building from the latter branch, but found some= significant differences in the former=0A>>> that I think may be importan= t to merge in.=0A>>> =0A>>> To me it seems like 19.09 is just outdated an= d doesn't have any benefits. Ask the solidrun people=0A>>> to be sure.=0A= >>> =0A>>> Either way, nothing here would fix the interrupt bug. It's our= bug since NetBSD works fine :(=0A>> =0A>> Any chance I can get a new tes= t kernel without PCIe quirks? I just got a much more recent image=0A>> fr= om jnettlet with the following comments:=0A>> =0A>> BEGIN QUOTE=0A>> If y= ou are using that recent uefi firmware I posted then you shouldn't be usi= ng the quirks for=0A>> pcie. That has an ecam shift setup where it should= behave....relatively to SBSA standards.=0A>> it definitely won't work wi= th the quirk enabled though. I have to add an interface to edk2 to turn= =0A>> the mode on or off depending if you want access to the root bus and= have a kernel with the quirk=0A>> applied, or you want it to work with j= ust the devices exposed but in a more compliant manner=0A>> without quirk= s=0A>> END QUOTE=0A> =0A> In the last couple kernels I posted, you should= be able to set debug.acpi.disabled=3Dpci_layerscape=0A> to skip the quir= k.=0A> =0A> I'll build the next one soon though, I guess with more interr= upt debug prints lol=0A=0Ahttps://send.firefox.com/download/ae38fa3524649= 7c1/#AVSGMsnrM0YB2MSL7rRJRQ=0A=0A- customized pcie driver=0A+ https://rev= iews.freebsd.org/D25121=0A+ more interrupt debugging (stray interrupts, a= ll GIC config writes)