From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3B42BEEA853 for ; Fri, 13 Feb 2026 00:17:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:Message-ID: In-Reply-To:Subject:cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=nGymrJd0hxA6WNevLPQJ304Fm7iWF0CLwJmO38HwFiE=; b=j+Y2ZrPqvuChp6 sZEsTnJaZ4YCTXI+bgp9espAep+Y8yfcxSDdlOcXGcFVr1/v/ivyGnJhshjjVX1eUcSWdbQmfEuE9 xxKzMH1mdyvQ4KcXmOVtE2anRU4/OVjmKOKnAixAkft9gVO2WkUTh4ykr+4/DifD+ZeuadW4KfhTa CP35U2ggx9qzrtvX6dyEwNuJDt8OWwrKlle7K/zJ1XGaF8WYN2rlTh95hCpgENaODUYr+ZE2Caihr j8GweABj7b7l1kA06x4ERz4LSXZsvsHMMIzopz8NlgxRIGdP2YlWjRw8wJXrn14q6tNZMU8xGcGMR 4PRsFZX7cd0dr/7aMVPA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vqgs4-00000002mGQ-0iwY; Fri, 13 Feb 2026 00:17:20 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vqgs1-00000002mG1-2WMO for linux-riscv@lists.infradead.org; Fri, 13 Feb 2026 00:17:18 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id 0EECF41A73; Fri, 13 Feb 2026 00:17:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3F294C4CEF7; Fri, 13 Feb 2026 00:17:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770941836; bh=tKPZiQZtcH1wyxqDiOlONhRaVViNUnbTOpp3beoKyMw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=pFEiFgNS1a3Jp8KAZZFB40cXhGpZr5OZmp0SHCi2QCsgwMnQrOKrmXuNMLChuJSIU fOftFJc+dXGKumGXtckhsZ2RpmdzGMfeACnuJ1lVrC0tM6O1b3SJbLWb5HjvEJKkgb 4yLhURrUeXwyQK0/JSikVDpURtwwHKXBc4swwlafnJy6O/Cnt9rF3tWTkzqosKl055 mxiaQdwCqtRhzQBpp3tpRhhNr9CST57ZKmXjpzqKeVfa7dC3UdfYnK8GqdhrlKnIJU 73phhbPX1PuNeqVJ/YPJuALmRmn1pGAiXhpCRQ5NTHZgHCUhtsZXVXbkW2lLdYM4w6 cyTt4/kU1ggBA== Date: Thu, 12 Feb 2026 17:17:15 -0700 (MST) From: Paul Walmsley To: Nam Cao cc: Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Frederik Haxel , Vitaly Wool Subject: Re: [PATCH] riscv: Remove support for XIP kernel In-Reply-To: <20260202115403.2119218-1-namcao@linutronix.de> Message-ID: <14f964c0-c4e1-c8c7-2a04-6cd5d0cee64e@kernel.org> References: <20260202115403.2119218-1-namcao@linutronix.de> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260212_161717_660048_31C401FC X-CRM114-Status: GOOD ( 10.31 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On Mon, 2 Feb 2026, Nam Cao wrote: > XIP has a history of being broken for long periods of time. In 2023, it was > broken for 18 months before getting fixed [1]. In 2024 it was 4 months [2]. > > And now it is broken again since commit a44fb5722199 ("riscv: Add runtime > constant support"), 10 months ago. > > These are clear signs that XIP feature is not being used. > > I occasionally looked after XIP, but mostly because I was bored and had > nothing better to do. > > Remove XIP support. Revert is possible if someone shows up complaining. > > Link: https://lore.kernel.org/linux-riscv/20231212-customary-hardcover-e19462bf8e75@wendy/ [1] > Link: https://lore.kernel.org/linux-riscv/20240526110104.470429-1-namcao@linutronix.de/ [2] > Signed-off-by: Nam Cao > Cc: Frederik Haxel > Cc: Vitaly Wool Thanks, queued here - first for an experimental branch, and ultimately for v7.1. - Paul _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 4B57017DFE7 for ; Fri, 13 Feb 2026 00:17:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770941837; cv=none; b=Kzyh6asa7zdkLPpDPSXyPS/5x3AFjPv7FjuogoI0RijK1L71Pw7kYgFfCLOjMVFRI66FFBqi2Rig5hxZcKhlat0QoL/Pt8qs1w1F38KIJ8UPHVlcmrnRV3PqxYpZhKEmQmhjooLAotjGl3WIM3a9jeeIVr5PZwt1OInkx/uSUNA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770941837; c=relaxed/simple; bh=tKPZiQZtcH1wyxqDiOlONhRaVViNUnbTOpp3beoKyMw=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=qeNCdLGfbajroJ/d3lDR8qLx1Mn8HujcuZSqZlE3EUXSN3WmXIkY96Vvx2yA2dZ6Y+p79+v7o3Ux5cmBuQtzahToYxrVc+45mlTBWaIVVJN9YkgM4/4ItfSyHQQev6zIouTgAf+0jwE8j8gJfg4QmE6q6Zi6nYQkoL4wjCws9rQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=pFEiFgNS; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="pFEiFgNS" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3F294C4CEF7; Fri, 13 Feb 2026 00:17:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770941836; bh=tKPZiQZtcH1wyxqDiOlONhRaVViNUnbTOpp3beoKyMw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=pFEiFgNS1a3Jp8KAZZFB40cXhGpZr5OZmp0SHCi2QCsgwMnQrOKrmXuNMLChuJSIU fOftFJc+dXGKumGXtckhsZ2RpmdzGMfeACnuJ1lVrC0tM6O1b3SJbLWb5HjvEJKkgb 4yLhURrUeXwyQK0/JSikVDpURtwwHKXBc4swwlafnJy6O/Cnt9rF3tWTkzqosKl055 mxiaQdwCqtRhzQBpp3tpRhhNr9CST57ZKmXjpzqKeVfa7dC3UdfYnK8GqdhrlKnIJU 73phhbPX1PuNeqVJ/YPJuALmRmn1pGAiXhpCRQ5NTHZgHCUhtsZXVXbkW2lLdYM4w6 cyTt4/kU1ggBA== Date: Thu, 12 Feb 2026 17:17:15 -0700 (MST) From: Paul Walmsley To: Nam Cao cc: Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Frederik Haxel , Vitaly Wool Subject: Re: [PATCH] riscv: Remove support for XIP kernel In-Reply-To: <20260202115403.2119218-1-namcao@linutronix.de> Message-ID: <14f964c0-c4e1-c8c7-2a04-6cd5d0cee64e@kernel.org> References: <20260202115403.2119218-1-namcao@linutronix.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII On Mon, 2 Feb 2026, Nam Cao wrote: > XIP has a history of being broken for long periods of time. In 2023, it was > broken for 18 months before getting fixed [1]. In 2024 it was 4 months [2]. > > And now it is broken again since commit a44fb5722199 ("riscv: Add runtime > constant support"), 10 months ago. > > These are clear signs that XIP feature is not being used. > > I occasionally looked after XIP, but mostly because I was bored and had > nothing better to do. > > Remove XIP support. Revert is possible if someone shows up complaining. > > Link: https://lore.kernel.org/linux-riscv/20231212-customary-hardcover-e19462bf8e75@wendy/ [1] > Link: https://lore.kernel.org/linux-riscv/20240526110104.470429-1-namcao@linutronix.de/ [2] > Signed-off-by: Nam Cao > Cc: Frederik Haxel > Cc: Vitaly Wool Thanks, queued here - first for an experimental branch, and ultimately for v7.1. - Paul