From nobody Mon Jun 03 10:56:55 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VtBFb3McWz5MLpt for ; Mon, 03 Jun 2024 11:24:19 +0000 (UTC) (envelope-from dsl@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VtBFb2RtVz4Tg8; Mon, 3 Jun 2024 11:24:19 +0000 (UTC) (envelope-from dsl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717413859; 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: in-reply-to:in-reply-to:references:references; bh=e+msoIcpy69D3iA6pEVprZkfqaqf0uf54jGj2j17+UA=; b=dux94wmLbSs3t3nBTTk9ci13orPzMcavwyQWOZUoI/EZ88PbrMB6bwTJY+/avV1XMHSOj4 0IW7Uc6NCwxmRNQlJ3uFDsqetQt+W7PmZmleQ7wGaWgta7accjXkn7XemnhozMMiQNCSZt yc4fK0xhyQwjT8ezymgwM1zJ09YZAc0VOtf6m6VHZpIASsqKn8+ZOY59pRePKvHq8C9oMo xS1MnXxLdVxAf+uh3igVrgdV+fvhaNFkMgJsnG1bjBiqmGysmFaj6gOduV5j3qTEmPBA0D QWv1F0eMlsfUui+TjHejLJAqsT0Z6IHtl59r+KLcGBvBlCHm0d9d1FBaK2Ml5g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717413859; a=rsa-sha256; cv=none; b=FSmUCSP6cJQ+dP5BiYgP7KintG7+Z6UIjscQ0T2xbuNP6DrAKYjq1Bi445vBSdiXvUTnj0 RMau3fglBAfcmyvR6PISjsnBT0iYmL3V1UIHTASbjN6r6FjKLX7H/qT3iwMRJIkWoVAUYj xC6bTHJSLR7QGOr3jWfm8SBuw5gQE2Us0lQA1OvSNVlFJuvPyXJnX33yvXgR7eEcZ4CMjX nZpDko9l+VlyrZ0CI1uL72X3T3vWj85tscy2lJBYTWalPXqQiJtcjdW+fzViimJTLOyJWp O20J0hUJH3sa/82HgdG244Kt46i4OeOEn2pafqPDaasKMkjrSy41ObeePzE0cA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717413859; 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: in-reply-to:in-reply-to:references:references; bh=e+msoIcpy69D3iA6pEVprZkfqaqf0uf54jGj2j17+UA=; b=flq+TUY10W8pi/2SvZxbBTrhLxEZ8dK//8WMMop6vjcsW0K9liFv22SFmYd7kG4K97b8t3 tuHwwmEcvKnx0Jr5RSP4Sx0JGZN7Nf0Xwr/ScmeikiYbA83Wvfl3amYvm1T4mkWUSyPewh +tfV/2PsaId2jwEAR85Ec5Ntt0LZWwUZZYnwscEZYj6dtdumYfpnjcSIdSFIW/nED0nQmV B+AYgk//y9HfDZQH/AAuqLrh/zmVZmrc7kUTlIJbn1HEAUWAwCSkEB+EyPaX0fYiHKAjKO oqPRe6iKc5rgnN8ZgdpI5U2DmSBcf9VpZy5QfAyqV/d/CzGYgcEDpQ6mXBUC9Q== Received: from localhost (unknown [91.226.51.235]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: dsl) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VtBFZ71Sdzf2T; Mon, 3 Jun 2024 11:24:18 +0000 (UTC) (envelope-from dsl@FreeBSD.org) References: <33931s3s-oss6-90q2-8pr0-2809n6r83nos@yvfgf.mnoonqbm.arg> User-agent: mu4e 1.8.13; emacs 29.3 From: Dmitry Salychev To: "Bjoern A. Zeeb" Cc: Mark Millard , freebsd-arm@freebsd.org Subject: Re: One less thing blocking UEFI+FDT support for HoneyComb Date: Mon, 03 Jun 2024 12:56:55 +0200 In-reply-to: <33931s3s-oss6-90q2-8pr0-2809n6r83nos@yvfgf.mnoonqbm.arg> Message-ID: <86bk4imfqa.fsf@peasant.tower.home> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain "Bjoern A. Zeeb" writes: > On Thu, 30 May 2024, Mark Millard wrote: > >> (B) could well involve things not involving dpaa2 usage >> via FDT. > > Is there's a problem with that please email dsl@ and bz@ and we can have > a look. In general dpaa2 workes with both ACPI and FDT so... I asked about UEFI images on the unofficial solidrun channel [1] recently: dsl: btw, https://images.solid-run.com/LX2k/lx2160a_uefi seems abandoned. Does anyone know why? jnettlet: There is no business use case for it. Since we were unable to get patches into mainline linux for the final devices, and fixes there was no real reason to move forward with edk2 and ACPI since u-boot and device-tree didn't have these limitations but when I tried one of the FTD-based images from [2], it didn't work because of a missing PHY for 1 Gbps port. It looks like our "glue" code in memacphy_fdt/memac_mdio_fdt didn't work in this specific case. FDT overlay for "fsl_mc: fsl-mc@80c000000" to provide correct values for the DPMAC corresponding to the 1 Gbps port (dpmac17 IIRC) would be a workaround for now, but I'll probably have to debug more. [1] https://discord.com/channels/620838168794497044/665456384971767818 [2] https://images.solid-run.com/LX2k/lx2160a_build Regards, Dmitry -- https://wiki.freebsd.org/DmitrySalychev