From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 34631388E7A for ; Mon, 1 Jun 2026 08:26:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780302403; cv=none; b=enMek3l3w85UYZkdqzxwTh/gh1wv2ASJOr/5R7fOppsxFR4AeBOr2yB+OL6TO42hikUUpv/uVkcLDjcq4cKNSp7FlutfXZxPhguzf0wzsSwOz9m5AKynftU3/NMhNOlkJVb/sz6kNNXs1sPhLWsMRlgxALBV3M0VPZAagfj89N8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780302403; c=relaxed/simple; bh=ZnBL8c3Fosuccw3/yCWY9wS1O+3elQnCWd96ulX8Q1w=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=JfumdNo5SI++dopD4uUqpOGi+rhIprAb4eK3CTfceArZKATulEW3d8hDm1mm9+WTqjFZTxlvqC7C3h0k+1XWhcuZOJTyHfWev3QAaVZOAqtzkgYfld/Su4lJSblvJ7xF9obfRkOtnghx6TqDP35X2aWqT6UPxT+7FyYmLgfnJ4Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=oo2RK4Al; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=YcvtwXJi; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="oo2RK4Al"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="YcvtwXJi" From: Nam Cao DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1780302400; 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=ZnBL8c3Fosuccw3/yCWY9wS1O+3elQnCWd96ulX8Q1w=; b=oo2RK4AlbXrHv1sAjqck0swz56b4O0k6mI94Zcj2TEu4VFn3KdphfJRiB5pfF+wWEfrdgj tNpkg/+I91YSxGx9schTSAvPX9AuTySMqXHTtfRcQ22AWdJSE8lnQ7IwyTi443GsKt9WUK 9hnI4jD05y+bCOHRFGeTvXA4Yr7BZTo+niyhvRBAdF1Ps5mXT0svGuhpvKfVT97gwH6Lhs 8Fccdyr75ZbVlAeXc0uhWQW5pAYWCdve/A8v1ye5RK7KwxP9YSsXEo4W29r+Syn21c6gqg VjL6JsEc8uJsDkhpUzSCntDWlsL+rTqzLK+YFr2RFOU254ElFGqwvkvnO3em+Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1780302400; 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=ZnBL8c3Fosuccw3/yCWY9wS1O+3elQnCWd96ulX8Q1w=; b=YcvtwXJicJP5nKdWELv75z4AI/R4MJ9Qehb15so7UwW7Au8sSoiCA+Pm5a1j/ZAKe+D5wz xFrBPXTXQ1oX8fDg== To: CABe3_aH6jYyoC=Jx91qATP2kOoY42NUtesyZpGbWGoQTw75OAA@mail.gmail.com, cmirabil@redhat.com Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, haxel@fzi.de, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, palmer@dabbelt.com, pjw@kernel.org, vitaly.wool@konsulko.com, Kunwu Chan , Zhouyi Zhou zhou , igor.b@beldev.am, Jisheng Zhang , Albert Ou , Frederik Haxel , charlie@rivosinc.com Subject: Re: [PATCH] riscv: Remove support for XIP kernel In-Reply-To: <05290c17-d55f-4e60-a77e-c36c3f14a89a@redhat.com> References: <05290c17-d55f-4e60-a77e-c36c3f14a89a@redhat.com> Date: Mon, 01 Jun 2026 10:26:40 +0200 Message-ID: <87pl2awtrz.fsf@yellow.woof> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Jesse Taube-Perrotta writes: > TLDR: Is re-adding XIP to no-mmu rv32 a possibility Paul explained the requirements to keep XIP: https://lore.kernel.org/linux-riscv/609b889a-8bb1-d2b5-8de6-ddeec27cac04@kernel.org/ Nam