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 phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 98F60C433EF for ; Tue, 18 Jan 2022 10:11:17 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id BA1DF83281; Tue, 18 Jan 2022 11:11:14 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="mYDQYmpC"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id DD395837D2; Tue, 18 Jan 2022 11:11:12 +0100 (CET) Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 7162F83102 for ; Tue, 18 Jan 2022 11:11:09 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=bmeng.cn@gmail.com Received: by mail-yb1-xb34.google.com with SMTP id e195so24048724ybb.7 for ; Tue, 18 Jan 2022 02:11:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gcTAY9QKAuI55WHLABvJWdCLDa/BT52AvA3mCL1bo4E=; b=mYDQYmpCtR2YjgrhHJWMVuqVkVe8w/NKRQrCb4q7Neq1syy7MjjEpy1N84ABlH5QnQ aiLXEQ0Jy6XjDYOFqmixHGmm7J1o3TR1dJV4o2OwlFk1xcaMcgFoANMuZTcC8UkpZewd rPd6coSwvaOd3ucDnVoUmUdNCXpgGoogD+2weD8Vz9O8alTTbJYlD5ukHNcCMgPgJiTh vRDmEgcqK4wPpMyc/esLgCsplR9JCNiSD7HIOeaWo0wQ/FCeSAPcCRL4E1ByEOhXlvpb Ydhcn6QSRSMirkHP6kr/3Y0pzb7/nybhZx2GAM4z4OsKwN9nhgwqlhI8/Lv1t2a07Yx/ s36Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gcTAY9QKAuI55WHLABvJWdCLDa/BT52AvA3mCL1bo4E=; b=VRBwpSEQHnYELvfEQwiy+Q2e4UkIJlSrnZ45YRwzMelqMiD0YwhAJP0y9U/E82VYH9 l1g51q7tyLDAPybVOQTK8Fuc29BBkOCDYYuNoQ6oCXHXWTI3QsNoi8wk7BdUv5g0MSxy y+TU5veuzZ9Cqct+g/BNko18dLF7lVSo+ok6yhrUlZUC1MOw0FLFTrKlEf1d6gyn3Wol 1LdvZG25tyUE5Nzi1BaqripcdqKwjCilpKwehBAXi60PWRmL8OKws9c+qs9qpMQEwDK7 niISQ8SDEdyDaAnE2Kq+wg6X0kq2a95b7XinON/KxxLeh8swivDQR8w1EEfetH58X9n9 XBRw== X-Gm-Message-State: AOAM531QDDwBIhNbd6oNQiUfmJ5CgCK21xLhx0DWu1ujYURWP08sxjnk YsyAEEsjHlJDP6LTPqimsmqW6SKzFawuFiHtKEQ= X-Google-Smtp-Source: ABdhPJxaVgyY3ElSFWL8n/hVDCz88xK5iRcA4N1P6A6QDa2uS+yrM4YDxsjFGcAQMkYQcimDNR+10rqYDQy2Zhoqw8k= X-Received: by 2002:a5b:3c2:: with SMTP id t2mr34552632ybp.747.1642500668269; Tue, 18 Jan 2022 02:11:08 -0800 (PST) MIME-Version: 1.0 References: <20220114162008.70468-1-apatel@ventanamicro.com> In-Reply-To: <20220114162008.70468-1-apatel@ventanamicro.com> From: Bin Meng Date: Tue, 18 Jan 2022 18:10:57 +0800 Message-ID: Subject: Re: [PATCH 0/3] QEMU spike machine support for U-Boot To: Anup Patel Cc: Rick Chen , Atish Patra , Alistair Francis , Anup Patel , U-Boot Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean On Sat, Jan 15, 2022 at 12:20 AM Anup Patel wrote: > > We can use same U-Boot binary compiled using qemu-riscv64_smode_defconfig > on QEMU virt machine and QEMU spike machine. To achieve this, we need HTIF > console support for U-Boot QEMU RISC-V board hence this series. > > To test this series with latest OpenSBI, we can use the following command: > qemu-system-riscv64 -M spike -m 256M -display none -serial stdio \ > -bios opensbi/build/platform/generic/firmware/fw_jump.bin -kernel \ I think you forgot to mention this needs an updated QEMU too, due to plain binary is now used for spike? > ./u-boot/u-boot.bin > > These patch can be found in qemu_riscv_htif_v1 branch at: > https://github.com/avpatel/u-boot.git > > Anup Patel (3): > serial: Add RISC-V HTIF console driver > riscv: qemu: Enable HTIF console support > riscv: qemu: Implement is_flash_available() for MTD NOR > > board/emulation/qemu-riscv/Kconfig | 1 + > board/emulation/qemu-riscv/qemu-riscv.c | 17 +++ > drivers/serial/Kconfig | 8 ++ > drivers/serial/Makefile | 1 + > drivers/serial/serial_htif.c | 178 ++++++++++++++++++++++++ > 5 files changed, 205 insertions(+) > create mode 100644 drivers/serial/serial_htif.c > Regards, Bin