From owner-freebsd-arm@freebsd.org Wed Jun 3 13:37:46 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 21463337829 for ; Wed, 3 Jun 2020 13:37:46 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49cVMs0Sc7z4P3D for ; Wed, 3 Jun 2020 13:37:44 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Wed, 03 Jun 2020 13:37:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1591191462; bh=APU+28SU/am/6senfVMF3dVk+zfkneT/5q4QqA+k5tY=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=ERP0ExN5muSdqqjiQj70w/SF3ZgVc9XnGqiaXvBz94eGTkYaM8FQyzcT6qm2/IGr6 lGKxwQCuq9eK3ibeJwA0u1ucPrxbAf1qKVLcoRaAQ0guUy+H8YOJgknOVZ/6TelN+B cvZKDCjeQPETrBUZDdoUm3uzIcPIfVWpkKzmShq8= To: myfreeweb From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> References: <664db38a87ea8803be72af9738534994@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49cVMs0Sc7z4P3D X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=ERP0ExN5; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.134 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.25 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-1.04)[-1.037]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.01)[-1.015]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.134:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-1.10)[-1.096]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.134:from] 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 13:37:46 -0000 > > > I've sent a link to a known firmware build before: > > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/vie= w > > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? > > > > I decided to go back to the UEFI sources and have found some difference= s that I think need to be reconciled before moving forward. That said, I'm = not an ACPI wizard by any means - for me it's low-level mage spells at best= ... > > In https://github.com/SolidRun/edk2-platforms we have 2 different branc= hes that SolidRun seems to use: > > > > 1. LSDK-19.09-sr > > 2. master-lx2160a > > > > I've been building from the latter branch, but found some significant d= ifferences in the former that I think may be important to merge in. > > To me it seems like 19.09 is just outdated and doesn't have any benefits.= Ask the solidrun people to be sure. > > Either way, nothing here would fix the interrupt bug. It's our bug since = NetBSD works fine :( Any chance I can get a new test kernel without PCIe quirks? I just got a mu= ch 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 u= sing the quirks for pcie. That has an ecam shift setup where it should beh= ave....relatively to SBSA standards. it definitely won't work with the quirk enabled though. I have to add an i= nterface to edk2 to turn the mode on or off depending if you want access to= the root bus and have a kernel with the quirk applied, or you want it to w= ork with just the devices exposed but in a more compliant manner without qu= irks END QUOTE