All of lore.kernel.org
 help / color / mirror / Atom feed
From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: Nemo on emulated Nokia n900 (qemu-arm)
Date: Mon, 02 Dec 2013 08:26:27 -0500	[thread overview]
Message-ID: <529C8A83.50003@codeaurora.org> (raw)
In-Reply-To: <20131128171153.GA20486@amd.pavel.ucw.cz>

Hi Pavel,

On 11/28/2013 12:11 PM, Pavel Machek wrote:
> Hi!
> 
> For testing, it would be good to have some real
> userland... unfortunately I can't figure out how to do it.
> 
> Ideally, I'd like to put nemo-armv7hl-n900-mmcblk0p.raw on emulated sd
> card, but I get:
> 
> [    1.566345] Initializing XFRM netlink socket
> [    1.568023] NET: Registered protocol family 17
> [    1.570220] NET: Registered protocol family 15
> [    1.572601] Key type dns_resolver registered
> [    1.581481] omap_vp_forceupdate_scale: vdd_mpu_iva TRANXDONE
> timeout exceeded while trying to clear the TRANXDONE status
> [    1.586242] omap_vp_forceupdate_scale: vdd_core TRANXDONE timeout
> exceeded while trying to clear the TRANXDONE status
> [    1.601074] omap_vp_forceupdate_scale: vdd_mpu_iva TRANXDONE
> timeout exceeded. Voltage change aborted
> [    1.604522] cpu cpu0: omap_target: unable to scale voltage up.
> [    1.606933] omap_hsmmc omap_hsmmc.1: no support for card's volts
> [    1.609252] mmc1: error -22 whilst initialising SDIO card
> SD: ACMD41 in a wrong state
> SD: ACMD41 in a wrong state
> SD: ACMD41 in a wrong state
> SD: ACMD41 in a wrong state
> SD: CMD1 in a wrong state
> [    1.613830] cpufreq: __cpufreq_driver_target: Failed to change cpu
> frequency: -110
> [    1.622650] ThumbEE CPU extension supported.
> 
> But according to google, old linux kernels were able to work with SD
> on qemu-arm...
> 
> IIRC there was some discussion that qemu does not properly emulate SD
> card, and that internal NAND emulation can be used instead. I tried
> using qflasher, but it is not able to use 3.5GB
> nemo-armv7hl-n900-mmcblk0p.rawnemo-armv7hl-n900-mmcblk0p.raw -- strace
> revealed file too big error.
> 
> Any ideas?

While I don't know the details of QEMU SD/MMC and NAND support, another option
you could try is the VirtIO block device peripheral.

http://www.linux-kvm.org/page/Boot_from_virtio_block_device

Regards,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	OH@amd.pavel.ucw.cz
Subject: Re: Nemo on emulated Nokia n900 (qemu-arm)
Date: Mon, 02 Dec 2013 08:26:27 -0500	[thread overview]
Message-ID: <529C8A83.50003@codeaurora.org> (raw)
In-Reply-To: <20131128171153.GA20486@amd.pavel.ucw.cz>

Hi Pavel,

On 11/28/2013 12:11 PM, Pavel Machek wrote:
> Hi!
> 
> For testing, it would be good to have some real
> userland... unfortunately I can't figure out how to do it.
> 
> Ideally, I'd like to put nemo-armv7hl-n900-mmcblk0p.raw on emulated sd
> card, but I get:
> 
> [    1.566345] Initializing XFRM netlink socket
> [    1.568023] NET: Registered protocol family 17
> [    1.570220] NET: Registered protocol family 15
> [    1.572601] Key type dns_resolver registered
> [    1.581481] omap_vp_forceupdate_scale: vdd_mpu_iva TRANXDONE
> timeout exceeded while trying to clear the TRANXDONE status
> [    1.586242] omap_vp_forceupdate_scale: vdd_core TRANXDONE timeout
> exceeded while trying to clear the TRANXDONE status
> [    1.601074] omap_vp_forceupdate_scale: vdd_mpu_iva TRANXDONE
> timeout exceeded. Voltage change aborted
> [    1.604522] cpu cpu0: omap_target: unable to scale voltage up.
> [    1.606933] omap_hsmmc omap_hsmmc.1: no support for card's volts
> [    1.609252] mmc1: error -22 whilst initialising SDIO card
> SD: ACMD41 in a wrong state
> SD: ACMD41 in a wrong state
> SD: ACMD41 in a wrong state
> SD: ACMD41 in a wrong state
> SD: CMD1 in a wrong state
> [    1.613830] cpufreq: __cpufreq_driver_target: Failed to change cpu
> frequency: -110
> [    1.622650] ThumbEE CPU extension supported.
> 
> But according to google, old linux kernels were able to work with SD
> on qemu-arm...
> 
> IIRC there was some discussion that qemu does not properly emulate SD
> card, and that internal NAND emulation can be used instead. I tried
> using qflasher, but it is not able to use 3.5GB
> nemo-armv7hl-n900-mmcblk0p.rawnemo-armv7hl-n900-mmcblk0p.raw -- strace
> revealed file too big error.
> 
> Any ideas?

While I don't know the details of QEMU SD/MMC and NAND support, another option
you could try is the VirtIO block device peripheral.

http://www.linux-kvm.org/page/Boot_from_virtio_block_device

Regards,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

  reply	other threads:[~2013-12-02 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 17:11 Nemo on emulated Nokia n900 (qemu-arm) Pavel Machek
2013-11-28 17:11 ` Pavel Machek
2013-12-02 13:26 ` Christopher Covington [this message]
2013-12-02 13:26   ` Christopher Covington

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=529C8A83.50003@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=linux-arm-kernel@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.