From nobody Mon Jan 27 04:51:41 2025 X-Original-To: freebsd-current@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 4YhGH04MmJz5mCR3 for ; Mon, 27 Jan 2025 04:51:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YhGH02Wtdz4NbW; Mon, 27 Jan 2025 04:51:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f45.google.com with SMTP id 2adb3069b0e04-5401bd6cdb4so4402868e87.2; Sun, 26 Jan 2025 20:51:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737953514; x=1738558314; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7kubJQUWKpLTrLDzcQkMbjLX6lr1PFQ2iFMMeB33QkE=; b=q7GqwDh7uZkAY7qZMyaOsL5q3SmID91fZlVVUUYCLXc/yvNJ9/itcsusAy3HJdFTqi 39aDa/+Upym/w7AsY+iZPnZ6QL0l9x1j0uPy1Ds31eUPaM4YT5wkGZx3bXZk04+KPkt/ ieHhQ4g98Da52m3zSqWKKZFnjtyE3w040YJKhgUg7OZivkfXjhMzQO5Eoc5vjQxQvuW7 nCyNiaVG81f8AIeHu2DS3Ursg7TL6vch3LjlqcDuZhS3MZ+OvAnCI6M1hxAsFmO5/zhg IwcmGaplPXYZV5Jg432O0LktKSTUAs+Pwa4h9r160UIHVsuvUFjkRLWGd/xwX9uWE7Wo D6ag== X-Forwarded-Encrypted: i=1; AJvYcCU6XkPcfz3wjAWoq+iL426KDpThjF2RPT2E30nmwU8Yy1PavzbWuu8OWnV8omaXuZi6W7KsWQ==@freebsd.org, AJvYcCUolsubJPOCIIxQKp91KpmcAGSk6chETMNcQoHPfxQ4KmV7CcPa/SdQ55oe4No+erW/iZtRFktENe7U6mzqtiQ=@freebsd.org X-Gm-Message-State: AOJu0YyKoparjnIHHwhy5bFINKnHQAz7lwA8wdLrNfnaiSm/nsJtVShA h/XSpKYsT5oAZaUfB1fokZDhUHTBw3GqyEnoJ+DU4n4++sJ8XRxud6wkjG66h3py5dP79DLsEie eb4pSD2VPxG7n/VvfvHEoz2AqfVg= X-Gm-Gg: ASbGnctpkQ+b7rJmBxp55y2r4yCkGbJ8UC2R9/4bmgCdGlq73vaZMA2vhBXhLV4GM5Z 2vm3TW0izA7nZY7BNuYykPc2UmKUZ23S0BYOZJ9t3Mi4RKs/4c9IJ4zX1gz75mbA= X-Google-Smtp-Source: AGHT+IEbEjlnjo9si8xQniYxAg5d9UVSNd4BDrXS10tz4UMBgFE/CX/IQG1d6GqFVjJtEHU0j8mOQMjYUzzCeJFIDhM= X-Received: by 2002:a05:6512:3b09:b0:542:2f0f:66d9 with SMTP id 2adb3069b0e04-5439c246297mr16126141e87.16.1737953513896; Sun, 26 Jan 2025 20:51:53 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <978176f7-270c-4603-b80a-e29c3b1b4b73@FreeBSD.org> <4FC807EC-10DD-49FD-AACE-9026B4925923@yahoo.com> <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> In-Reply-To: <1B14894C-78E3-4696-9E4F-FBA97A356BF1@yahoo.com> From: Adrian Chadd Date: Sun, 26 Jan 2025 20:51:41 -0800 X-Gm-Features: AWEUYZmc2Fc68_tpq0Wr4iaj-QGIo49nvRxL8smvFAi4fkVbvecdDLldHxc1KbE Message-ID: Subject: Re: "don't know how to make /usr/main-src/sys/contrib/dev/iwm/iwm-3160-17.fw.uu. Stop" To: Mark Millard Cc: Stefan Esser , Emmanuel Vadot , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000d507a8062ca8d5c1" X-Rspamd-Queue-Id: 4YhGH02Wtdz4NbW X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] --000000000000d507a8062ca8d5c1 Content-Type: text/plain; charset="UTF-8" Hi! So, there's no longer a build target for the firmware uuencoded files -> kernel module. Being able to build iwm in the kernel rather than a module is broken. Now, the real issue(s) are that iwm needs firmware to initialise, and the firmware needs to exist, and thus it needs access to the rootfs for firmware_get() to find the now binary files in /boot/firmware instead of the kernel module old way, and that whole pipeline is broken if it's loaded at boot time or included in the kernel directly. There isn't a nice way to defer the firmware load attempt until /after/ rootfs is up. -adrian --000000000000d507a8062ca8d5c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=
Hi!

So, there's no longer a build t= arget for the firmware uuencoded files -> kernel module.

<= /div>
Being able to build iwm in the kernel rather than a module is bro= ken.

Now, the real issue(s) are that iwm needs fir= mware to initialise, and the firmware needs to exist, and thus it needs acc= ess to the rootfs for firmware_get() to find the now binary files in /boot/= firmware instead of the kernel module old way, and that whole pipeline is b= roken if it's loaded at boot time or included in the kernel directly. T= here isn't a nice way to defer the firmware load attempt until /after/ = rootfs is up.




-adrian

=C2=A0
--000000000000d507a8062ca8d5c1--