From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JtIvs-0008Lr-Cc for qemu-devel@nongnu.org; Tue, 06 May 2008 04:53:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JtIvp-0008JZ-TH for qemu-devel@nongnu.org; Tue, 06 May 2008 04:53:55 -0400 Received: from [199.232.76.173] (port=53735 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JtIvp-0008JF-KO for qemu-devel@nongnu.org; Tue, 06 May 2008 04:53:53 -0400 Received: from ecfrec.frec.bull.fr ([129.183.4.8]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JtIvp-0004VR-5f for qemu-devel@nongnu.org; Tue, 06 May 2008 04:53:53 -0400 Subject: Re: [Qemu-devel] [Patch] [kinda-resend] persistent real-time-clock From: Laurent Vivier In-Reply-To: <50BFF407-EAE4-4BF6-8701-5229CBAB8B5C@adacore.com> References: <20080427154501.GA20547@karma.qumranet.com> <4814B0A9.7090601@codemonkey.ws> <20080501084833.GA21769@karma.qumranet.com> <481F6CAF.6060308@codemonkey.ws> <481F7896.1000409@qumranet.com> <481F8C55.8080302@codemonkey.ws> <50BFF407-EAE4-4BF6-8701-5229CBAB8B5C@adacore.com> Content-Type: text/plain; charset=utf-8 Date: Tue, 06 May 2008 10:53:43 +0200 Message-Id: <1210064023.4311.14.camel@frecb07144> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Dan Kenigsberg Le mardi 06 mai 2008 =C3=A0 10:26 +0200, Tristan Gingold a =C3=A9crit : > > It's a bios parameter (just like default boot device). It makes =20 > > sense to allow the bios to let the user customize bios parameters =20 > > and have that be saved. > > > > CMOS is non-volatile in real life so making it non-volatile in QEMU =20 > > seems like the obvious thing to do. >=20 > I fully agree. Platforms have many non-volatile storage (CMOS, =20 > ethernet eeproms, flashes...). It would > be nice if qemu were able to making them non-volatile. >=20 > I'd plan to work on this, although not soon. Herv=C3=A9 Poussineau had already done this kind of work for DS1225Y chip= . The content of the NVRAM is saved into the file "nvram". I think we should have a more generic way to manage this. I mean: - a parameter to specify the file - a default filename per machine (something like "~/.qemu/pc.cmos", "~/.qemu/sun4m.nvram" or "~/.qemu/ppc_oldworld.nvram") (and if we create a "~/.qemu" directory, perhaps we could store some default configurations ... :-P ) There is also the -prom-env parameter to specify a value of the nvram (for sparc only, but could be generic). Laurent --=20 ------------- Laurent.Vivier@bull.net --------------- "The best way to predict the future is to invent it." - Alan Kay