From: Zong Li <zongbox@gmail.com>
To: hch@infradead.org
Cc: Zong Li <zong@andestech.com>, Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
greentime@andestech.com
Subject: Re: [PATCH v2 0/4] Building for 32-bit RISC-V kernel
Date: Sat, 30 Jun 2018 01:06:23 +0800 [thread overview]
Message-ID: <CA+ZOyahMwEtrG+uzQqGtbfmbeyBDNQVQJUn9oyaMfJb2wNmybw@mail.gmail.com> (raw)
In-Reply-To: <20180629072307.GF12956@infradead.org>
Christoph Hellwig <hch@infradead.org> 於 2018年6月29日 週五 下午3:23寫道：
>
> Btw, what kind of userspace do you use for riscv32? Do you have an
> easy to use root file system available somewhere (or a way to build
> one)?
I'm porting 32 bit riscv glibc now, and it is almost completion but
still has few fail cases of glibc testsuite.
I built the root file system consist of busybox, bash and dropbear and
so on. I can push the
rootfs I used or a build script to github if somebody need it.
prev parent reply other threads:[~2018-06-29 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 8:49 [PATCH v2 0/4] Building for 32-bit RISC-V kernel Zong Li
2018-06-25 8:49 ` [PATCH v2 1/4] RISC-V: Add conditional macro for zone of DMA32 Zong Li
2018-06-29 7:08 ` Christoph Hellwig
2018-06-25 8:49 ` [PATCH v2 2/4] RISC-V: Select GENERIC_UCMPDI2 on RV32I Zong Li
2018-06-29 7:08 ` Christoph Hellwig
2018-06-25 8:49 ` [PATCH v2 3/4] RISC-V: Add definiion of extract symbol's index and type for 32-bit Zong Li
2018-06-29 7:12 ` Christoph Hellwig
2018-06-29 16:53 ` Zong Li
2018-07-04 20:58 ` Palmer Dabbelt
2018-07-05 13:33 ` Zong Li
2018-07-05 16:42 ` Palmer Dabbelt
2018-06-25 8:49 ` [PATCH v2 4/4] RISC-V: Change variable type for 32-bit compatible Zong Li
2018-06-29 7:12 ` Christoph Hellwig
2018-06-29 7:23 ` [PATCH v2 0/4] Building for 32-bit RISC-V kernel Christoph Hellwig
2018-06-29 17:06 ` Zong Li [this message]
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=CA+ZOyahMwEtrG+uzQqGtbfmbeyBDNQVQJUn9oyaMfJb2wNmybw@mail.gmail.com \
--to=zongbox@gmail.com \
--cc=greentime@andestech.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=zong@andestech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).