All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@roeck-us.net (Guenter Roeck)
To: linux-riscv@lists.infradead.org
Subject: Risc-V, qemu, and initrd
Date: Thu, 21 Jun 2018 09:34:48 -0700	[thread overview]
Message-ID: <20180621163448.GA2292@roeck-us.net> (raw)
In-Reply-To: <20180621145217.GA12445@infradead.org>

On Thu, Jun 21, 2018 at 07:52:17AM -0700, Christoph Hellwig wrote:
> On Thu, Jun 21, 2018 at 07:48:21AM -0700, Guenter Roeck wrote:
> > I did. The resulting image hangs (I tried v4.17.2 and v4.18-rc1).
> 
> The upstream kernel is missing support for irq controllers and timers,
> so I don't think it can boot on anything.
> 
Hmm ... not as bad as a car with no engine, but getting close.

> Here is my branch that allows me to boot qemu with 4.18-rc:
> 
> 	http://git.infradead.org/users/hch/riscv.git/shortlog/refs/heads/riscv-linux-4.18

Yes, that boots if I disable setup_initrd(). I am still puzzled about the
purpose of setup_initrd() - it effectively disables external initrd,
initrd built into the kernel via CONFIG_INITRAMFS_SOURCE works just fine
without it, and no other architecture has similar code. Can/should it be
removed ?

Thanks,
Guenter

  reply	other threads:[~2018-06-21 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21  6:11 Risc-V, qemu, and initrd Guenter Roeck
2018-06-21  8:11 ` Atish Patra
2018-06-21 14:30 ` Andreas Schwab
2018-06-21 14:48   ` Guenter Roeck
2018-06-21 14:52     ` Christoph Hellwig
2018-06-21 16:34       ` Guenter Roeck [this message]
2018-06-21 17:33       ` Guenter Roeck
2018-06-21 17:55         ` Christoph Hellwig
2018-06-21 22:08           ` Guenter Roeck
2018-06-22  5:38             ` Christoph Hellwig
2018-06-22 16:34               ` Guenter Roeck

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=20180621163448.GA2292@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-riscv@lists.infradead.org \
    /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.