From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MtgV6-0003dU-OD
	for qemu-devel@nongnu.org; Fri, 02 Oct 2009 07:40:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MtgV0-0003QU-2M
	for qemu-devel@nongnu.org; Fri, 02 Oct 2009 07:40:40 -0400
Received: from [199.232.76.173] (port=37205 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MtgUz-0003QH-Gg
	for qemu-devel@nongnu.org; Fri, 02 Oct 2009 07:40:33 -0400
Received: from mx1.redhat.com ([209.132.183.28]:22930)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1MtgUx-0003VT-T0
	for qemu-devel@nongnu.org; Fri, 02 Oct 2009 07:40:33 -0400
Message-ID: <4AC5E691.5000909@redhat.com>
Date: Fri, 02 Oct 2009 13:40:01 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Reorganize option rom (+linux kernel)
	loading.
References: <1254325401-18777-1-git-send-email-kraxel@redhat.com>
	<f43fc5580909301251k63bb5fbqa623ec2aa9045275@mail.gmail.com>
	<4AC4725D.1020009@redhat.com>
	<f43fc5580910010925r7ed7e621yd926f68da824d37c@mail.gmail.com>
In-Reply-To: <f43fc5580910010925r7ed7e621yd926f68da824d37c@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org

> OK, V2 seems to work, except that the command line is not passed:
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
>   <0>Press L1-A to return to the boot prom

So you are booting sparc via -kernel I guess?

>> around for no reason.  Maybe make restore-on-reset opt-in?
>
> Or make writability opt-in feature?

v2 does it automagically by checking the memory type.
'info roms' got a new mem=[ram|rom] entry.

cheers,
   Gerd