From owner-freebsd-arm@freebsd.org Mon May 18 20:11:08 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 59FBB2DC0EF for ; Mon, 18 May 2020 20:11:08 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (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 49Qqs72ZJ2z4GtR for ; Mon, 18 May 2020 20:11:07 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Mon, 18 May 2020 20:11:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1589832664; bh=HBjVeZ8IcJOBh3+nQpBUI22VOEOZLiOj9re68Mob1+Y=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=sU+KzwljXuBCtR0W26jR93/mVD3X9TS2ghfwWX1jegO74PN2XRkgGXHqQTAVOZUJi AOKZbYPydqvW1ZaKjcYlj0blAUCBuhM6KPwa5e7wLtMTBN8zU7OhTT69E/BP6HtxNg Zib9RIGcCNhzy5RiG1u/lWCp/t+eytKdT1CowpJ0= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: John-Mark Gurney , freebsd-arm@freebsd.org Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <2053cd2299b81860deecc638ef839d1f@unrelenting.technology> References: <3nsQUg1Gm4VFYfpHVELk6PWaHyYNb3CoyoKnLV55_3VR48tr90bhaseG3sJg007L8czZ4mXUmR_YMQvYVdMbUs1bsoqGtZp5d17FqYT6b-o=@a9development.com> <7AFDA7E0-82EC-4CD2-BB03-B7E33D019EDA@unrelenting.technology> <_lvahpuNQE69s4KpHud6ANL6yzL3RCVI-MTyB0_J_ULyW-3UWsqAXnm5gfoFcOyvfRQRabZk4Z4bQgyp15a001kA-WcvsvnWcjqgMBkgGTY=@a9development.com> <7F9D7164-2C04-4E27-85F9-A495EAC8FC84@unrelenting.technology> <63b4f78ff4ee07359a345bcbc03afeaa@unrelenting.technology> <2053cd2299b81860deecc638ef839d1f@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: 49Qqs72ZJ2z4GtR X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=sU+Kzwlj; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-1.69 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.59)[-0.586]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.131:from]; 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.131: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: Mon, 18 May 2020 20:11:08 -0000 > Cool, please please please post a dmesg tohttps://dmesgd.nycbug.org :) > Done: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5490 > Created a bug for the ACPI detection issue: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246552 > Thanks! I'll keep my eyes on that as well. > > Is there a reason that we can't use on the DTBs compiled from SolidRun = and NXP's sources? > > The devicetree uses NXP specific device descriptions (for USB, SATA, PCIe= , all the things) > and FreeBSD doesn't understand them. > > ACPI tables mostly use generic devices descriptions that all operating sy= stems support > out of the box. > > It is technically possible to make a DTB that mostly uses generic nodes a= nd ACPI tables > full of custom vendor nodes, but almost nobody does this. > (Okay, actually, Qualcomm does ACPI with almost all vendor nodes on the W= indows aarch64 laptops :D) > > Generic descriptions are good. ARM systems that work in the "boring" plug= &play way (with standardized > generic devices) are the ideal we all should strive for, so ACPI should a= lways be preferred. > If you're using any DTB on a server/workstation-class system, something h= as gone wrong :) Thanks for the explanataion, it's very helpful.