All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Charles Lohr <lohr85@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	cleger@rivosinc.com, Conor Dooley <conor@kernel.org>,
	samuel.holland@sifive.com,
	Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Conor Dooley <conor.dooley@microchip.com>,
	ajones@ventanamicro.com, dlemoal@kernel.org,
	Bjorn Topel <bjorn@rivosinc.com>,
	Atish Patra <atishp@rivosinc.com>
Subject: Re: [PATCH] riscv: deprecate CONFIG_MMU=n
Date: Wed, 27 Mar 2024 11:40:37 +0800	[thread overview]
Message-ID: <ZgOVNYkmXbXVCReV@xhacker> (raw)
In-Reply-To: <CAGu26P-CqdsQzNTNDidBUg=pxU3vs7QhNEajokGKe7p8M2sLBA@mail.gmail.com>

On Tue, Mar 26, 2024 at 06:34:09PM -0700, Charles Lohr wrote:
> Sorry, if you don't mind clarifying, do you know which version you
> used, where you got it, and if you had to apply any patches?

Hi,

rv32 uclibc toolchain is based on gcc12.2, while rv64 uclibc is based on
gcc13.2

I built them with the mainline buildroot, and rv32 toolchain was built
a year ago, I forget whether there was patches applied. I may apply
patches from your mini-rv32ima repo. The rv64 toolchain was built a
month ago, no patch is applied.

Thanks
> 
> Charles
> 
> On Tue, Mar 26, 2024 at 6:28 PM Jisheng Zhang <jszhang@kernel.org> wrote:
> >
> > On Tue, Mar 26, 2024 at 01:25:08PM -0700, Charles Lohr wrote:
> > > Jisheng, are you using musl or uclibc? I've been having difficulty
> > > getting new versions of each working with the newer kernels with
> > > system calls not lining up.
> >
> > Hi Charles,
> >
> > I tested nommu linux with uclibc, both rv32 and rv64
> >
> > Thanks
> >
> > >

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@kernel.org>
To: Charles Lohr <lohr85@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	cleger@rivosinc.com, Conor Dooley <conor@kernel.org>,
	samuel.holland@sifive.com,
	Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Conor Dooley <conor.dooley@microchip.com>,
	ajones@ventanamicro.com, dlemoal@kernel.org,
	Bjorn Topel <bjorn@rivosinc.com>,
	Atish Patra <atishp@rivosinc.com>
Subject: Re: [PATCH] riscv: deprecate CONFIG_MMU=n
Date: Wed, 27 Mar 2024 11:40:37 +0800	[thread overview]
Message-ID: <ZgOVNYkmXbXVCReV@xhacker> (raw)
In-Reply-To: <CAGu26P-CqdsQzNTNDidBUg=pxU3vs7QhNEajokGKe7p8M2sLBA@mail.gmail.com>

On Tue, Mar 26, 2024 at 06:34:09PM -0700, Charles Lohr wrote:
> Sorry, if you don't mind clarifying, do you know which version you
> used, where you got it, and if you had to apply any patches?

Hi,

rv32 uclibc toolchain is based on gcc12.2, while rv64 uclibc is based on
gcc13.2

I built them with the mainline buildroot, and rv32 toolchain was built
a year ago, I forget whether there was patches applied. I may apply
patches from your mini-rv32ima repo. The rv64 toolchain was built a
month ago, no patch is applied.

Thanks
> 
> Charles
> 
> On Tue, Mar 26, 2024 at 6:28 PM Jisheng Zhang <jszhang@kernel.org> wrote:
> >
> > On Tue, Mar 26, 2024 at 01:25:08PM -0700, Charles Lohr wrote:
> > > Jisheng, are you using musl or uclibc? I've been having difficulty
> > > getting new versions of each working with the newer kernels with
> > > system calls not lining up.
> >
> > Hi Charles,
> >
> > I tested nommu linux with uclibc, both rv32 and rv64
> >
> > Thanks
> >
> > >

  reply	other threads:[~2024-03-27  3:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 14:06 [PATCH] riscv: deprecate CONFIG_MMU=n Clément Léger
2024-02-26 14:06 ` Clément Léger
2024-02-26 14:57 ` Damien Le Moal
2024-02-26 14:57   ` Damien Le Moal
2024-02-26 14:59   ` Clément Léger
2024-02-26 14:59     ` Clément Léger
2024-02-26 15:01     ` Damien Le Moal
2024-02-26 15:01       ` Damien Le Moal
2024-02-26 15:14 ` Samuel Holland
2024-02-26 15:14   ` Samuel Holland
2024-02-26 15:25   ` Clément Léger
2024-02-26 15:25     ` Clément Léger
2024-02-26 16:02     ` Conor Dooley
2024-02-26 16:02       ` Conor Dooley
2024-02-26 19:00       ` Charles Lohr
2024-02-26 19:00         ` Charles Lohr
2024-02-26 21:29         ` Conor Dooley
2024-02-26 21:29           ` Conor Dooley
2024-02-27  9:11         ` Clément Léger
2024-02-27  9:11           ` Clément Léger
2024-02-27 16:38           ` Palmer Dabbelt
2024-02-27 16:38             ` Palmer Dabbelt
2024-03-14 12:46             ` Jisheng Zhang
2024-03-14 12:46               ` Jisheng Zhang
2024-03-14 13:02               ` Jisheng Zhang
2024-03-14 13:02                 ` Jisheng Zhang
2024-03-25 16:59                 ` Jisheng Zhang
2024-03-25 16:59                   ` Jisheng Zhang
2024-03-26 20:25                   ` Charles Lohr
2024-03-26 20:25                     ` Charles Lohr
2024-03-27  1:14                     ` Jisheng Zhang
2024-03-27  1:14                       ` Jisheng Zhang
2024-03-27  1:34                       ` Charles Lohr
2024-03-27  1:34                         ` Charles Lohr
2024-03-27  3:40                         ` Jisheng Zhang [this message]
2024-03-27  3:40                           ` Jisheng Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZgOVNYkmXbXVCReV@xhacker \
    --to=jszhang@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@rivosinc.com \
    --cc=bjorn@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lohr85@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.