From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9F68513A869 for ; Wed, 17 Apr 2024 14:09:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713362999; cv=none; b=EfGIlyjm+FgdleykIM7TwodkGUwF3MzIaQfUDdvNKh08ACwrYTgmStRRMW2kNKL4dj2dRpR+duWDqG53/uxrPvqmJ4jf8/Z7FPGGxDSbuGBU6/Tw9XLPcHI++GdA4jX77YGC1T2WuEDZaYV40vHAkq20W1j2kVxHi8ZkbtOUkB0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713362999; c=relaxed/simple; bh=x5Uz3gRgyxT1+IqFsdR7wre3wK47p8rTToCNr6IsUm4=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=bX/eR2pbxnPUshS7WETM9Nb+6u5zV0lPpF+1Lgfyq6pZTC1ujOlHRdQqsIHaQdcOi4eAbtuli6yMHRVnVzIi+PNw29lEkinaWQ2Z4yh9xE12PUN/430xifKYg5Mm6oZ+LWhoR/bgSS6TzpKXJsJXy7hfPELFQfypt17XRmhK0OQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=q4vG7qCd; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="q4vG7qCd" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=4wcEcjDMioCJvdEJBFh4Rw7VmBBlM0ZDq9pyplVl+bw=; t=1713362997; x=1714572597; b=q4vG7qCdB+oBBCjgtDWLpaGwZfUY+MLHMAT9qMlBlSbQCMe w4kjRF5vwL8sOZWo6mNQ+2izQHPK5cplFPGq5VF9v98iw1eVcE0Q4inK4Y9m6pxPyS3AXdF9A2Nz9 hu/rGe+fmBXElgV62nLBimofgNTm/WPv+h8fxcEwbtDDbjJhNKin72YfIE6DthjucyRvwuXuFl4wk aGwssDo9qIieVpicYoqZiYMeYin2wMYwNDjrDp3UodkyyShRRjkieEGtNYAgw0DXi5NmOfez/kE8o lzPV4Igti6lJstJ157PQxAXVx3qPIHS7VtOfggiXj84yyfGqXBgOcZ2S9c2+a50A==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rx5yz-0000000B0LN-3rBN; Wed, 17 Apr 2024 16:09:54 +0200 Message-ID: <2278e0d1026ed336559adbc9ffbf6e945eba422e.camel@sipsolutions.net> Subject: Re: putting future iwlwifi firmware into intel/ ? From: Johannes Berg To: Mario Limonciello , linux-firmware@kernel.org Cc: linux-wireless@vger.kernel.org, miriam.rachel.korenblit@intel.com Date: Wed, 17 Apr 2024 16:09:52 +0200 In-Reply-To: References: <9aa64d50-cb4d-4118-bc27-86c23410ff8b@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Wed, 2024-04-17 at 08:58 -0500, Mario Limonciello wrote: > >=20 > > Yeah, I guess. Though not actually sure, do we need to support new > > kernel + old firmware install? >=20 > I'd say you should. Here's a few examples of why: Right, agree. > So yes; do the symlinks when you move directories. It's one line in=20 > WHENCE per file that you want a symlink. >=20 That doesn't achieve it though. It means the driver needs to try for the file in intel/ and then fall back without the intel/ if it's not found. Or just look for new files in intel/ and old files without intel/, but then you don't really need the file move/symlinks? johannes