From owner-freebsd-arm@freebsd.org Wed Jun 3 16:09:49 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 5760E33AD0F for ; Wed, 3 Jun 2020 16:09:49 +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 49cYlH5v8wz3Tgr for ; Wed, 3 Jun 2020 16:09:47 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Wed, 03 Jun 2020 16:09:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591200579; 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=33hdMC7S1H8rjEK5ZtRigB/o9lEnPK7jqVoK0LDUcnE=; b=brEgt7WlSy51WMBsf73fwRul4CsO+K3ArRcm1HpKthb72x2aMxfXmDtxrnKSlZ5VK6C30+ MGrfqAC29LR0urxzUqyLgvTUj47YT55P1ze+7jJgP//jZZXQCCduK+AFnhxQgDA7vyMkRM UcqNdJ3iGOLk8ftfh13raVx7rjgxJOU= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Dan Kotowski CC: freebsd-arm Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X In-Reply-To: References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> Message-ID: <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49cYlH5v8wz3Tgr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=brEgt7Wl; 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.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.015]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.04)[-1.041]; 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]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.64)[-0.640]; 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 16:09:49 -0000 On June 3, 2020 1:37:34 PM UTC, Dan Kotowski wrote: >> > > I've sent a link to a known firmware build before: >> > > https://drive=2Egoogle=2Ecom/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvE= rK/view >> > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? >> > >> > I decided to go back to the UEFI sources and have found some differen= ces that I think need to be reconciled before moving forward=2E That said, = I'm not an ACPI wizard by any means - for me it's low-level mage spells at = best=2E=2E=2E >> > In https://github=2Ecom/SolidRun/edk2-platforms we have 2 different b= ranches that SolidRun seems to use: >> > >> > 1=2E LSDK-19=2E09-sr >> > 2=2E master-lx2160a >> > >> > I've been building from the latter branch, but found some significant= differences in the former that I think may be important to merge in=2E >> >> To me it seems like 19=2E09 is just outdated and doesn't have any benef= its=2E Ask the solidrun people to be sure=2E >> >> Either way, nothing here would fix the interrupt bug=2E It's our bug si= nce NetBSD works fine :( > >Any chance I can get a new test kernel without PCIe quirks? I just got a = much more recent image from jnettlet with the following comments: > >BEGIN QUOTE >If you are using that recent uefi firmware I posted then you shouldn't be= using the quirks for pcie=2E That has an ecam shift setup where it should= behave=2E=2E=2E=2Erelatively to SBSA standards=2E >it definitely won't work with the quirk enabled though=2E I have to add = an interface to edk2 to turn the mode on or off depending if you want acces= s to the root bus and have a kernel with the quirk applied, or you want it = to work with just the devices exposed but in a more compliant manner withou= t quirks >END QUOTE In the last couple kernels I posted, you should be able to set debug=2Eacp= i=2Edisabled=3Dpci_layerscape to skip the quirk=2E I'll build the next one soon though, I guess with more interrupt debug pri= nts lol