On Wed, 30 Sep 2015, Artyom Tarasenko wrote:
> >> codebase (see http://www.openfirmware.info/OpenBIOS for wiki
> >> instructions). I'm not sure that anyone has done much with the other
> >> firmware implementations recently, although I would be happy to accept
> >> build fixes. Which platform are you looking to work on?
>
> Can you try bisecting the problem? It used to build ~ one year ago.
The main problem is that I have posted to the wrong mailing list :)
The problem has been fixed in ofw r3782 - the missing file
has been added.
I got ofw running with and with BIOS under qemu-system-i386.
By the way, I like your blog very much - been following
your efforts since your first SPARCstation 5 attempts.
~Marcin
Hi,
I was trying to build ofw to run under
qemu (using wiki instructions) and it
seems that r3781 added
fload ${BP}/forth/lib/string-tools.fth
in forth/lib/loadcomm.fth
but there is no corresponding string-tools.fth file.
~Marcin
The child address of the PCI-EBus bridge "ranges" property should be offset from
the BAR address and not the beginning of the address space (similar as to how
the "assigned-addresses" property is generated). This fixes EBus enumeration
under FreeBSD SPARC64.
Reported-by: Marius Strobl <marius(a)alchemy.franken.de>
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk>
---
openbios-devel/drivers/pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/openbios-devel/drivers/pci.c b/openbios-devel/drivers/pci.c
index 366f4a1..b76c43e 100644
--- a/openbios-devel/drivers/pci.c
+++ b/openbios-devel/drivers/pci.c
@@ -824,7 +824,7 @@ int ebus_config_cb(const pci_config_t *config)
ncells += pci_encode_phys_addr(props + ncells,
flags, space_code, config->dev,
PCI_BASE_ADDR_0 + (i * sizeof(uint32_t)),
- 0);
+ config->assigned[i] & ~mask);
props[ncells++] = config->sizes[i];
}
--
1.7.10.4
On 14/09/15 06:35, Inon Fefer wrote:
> Please remove me from this list.
>
> On 14 Sep 2015 01:42, <openbios-request(a)openbios.org
> <mailto:openbios-request@openbios.org>> wrote:
>
> Send OpenBIOS mailing list submissions to
> openbios(a)openbios.org <mailto:openbios@openbios.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.openfirmware.info/mailman/listinfo/openbios
> or, via email, send a message with subject or body 'help' to
> openbios-request(a)openbios.org
> <mailto:openbios-request@openbios.org>
>
> You can reach the person managing the list at
> openbios-owner(a)openbios.org <mailto:openbios-owner@openbios.org>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBIOS digest..."
Hi Inon,
The digest header quoted in your reply above should give you all the
information you need to manage your subscription, including
unsubscribing from the list. If you find that you are still unable to
unsubscribe using the links above then please contact me off-list and I
will do my best to help.
ATB,
Mark.
On Sep 11, 2015, at 12:00 PM, qemu-discuss-request(a)nongnu.org wrote:
> On 10/09/2015 8:58 AM, Maximilian H. wrote:
>> Hello,
>>
>> I was looking into what parts would need change to save and restore the
>> nvram content for the qemu-system-sparc vm between boots.
>>
>> I see the code in hw/timer/m48t59.c that implements the nvram.
>>
>> So some questions arise, and before I spend too much time poking around
>> the still unknown code, I'd thought I ask first.
>>
>> 1. Command line processing starts in vl.c in the main fct there ? Can I
>> add a command line argument there, say "-sparcnvram" ?
>>
>> 2. In hw/timer/m48t59.c has no functionality that I see from having a
>> look at it (not in depth) to save or restore the nvram's contents for
>> sparc. Is there a general facility that qemu has that provides such a
>> functionality - i.e. is there a general qemu save and restore framework ?
>>
>> 3. Is there an example somebody could point me to that implements
>> something similar ? Imitation is the sincerest of flattery ....
>>
>> 4. All the alarm and watchdog functionality that the m48t08 provides, is
>> that used on sparc too ?
>>
>> 5. Besides what is in
>> http://wiki.qemu.org/Documentation/GettingStartedDevelopers, is there
>> some qemu coding documentation to make it faster for somebody unfamilar
>> with qemu's code like me to be able to implement something ? I'd like to
>> spend a few evenings on this, produce a patch and move on.
>>
>> Thanks
>> BR
>> Max.
>
This sounds like a good idea. Having OpenBIOS settings actually be saved between boots
would make things more real.
Mark, do you think it is possible for a QEMU command line option to actually load the
saved OpenBIOS settings from a file and restore them into memory? I'm thinking something
along the lines of -prom-memory <file name>.
Max, there is a project that you should probably look at called OpenBIOS. It implements
an implementation of Open Firmware. Here is where more info can be found: http://www.openfirmware.info/Welcome_to_OpenBIOS. If you do want to implement this feature,
it would help to know how the BIOS is implemented.
Please remove me from this list.
On 14 Sep 2015 01:42, <openbios-request(a)openbios.org> wrote:
> Send OpenBIOS mailing list submissions to
> openbios(a)openbios.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.openfirmware.info/mailman/listinfo/openbios
> or, via email, send a message with subject or body 'help' to
> openbios-request(a)openbios.org
>
> You can reach the person managing the list at
> openbios-owner(a)openbios.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBIOS digest..."
>
>
> Today's Topics:
>
> 1. Re: [Qemu-discuss] Qemu-system-sparc: What would I need to
> change to add functionality to save the nvram content between
> boots ? (Programmingkid)
> 2. Re: [Qemu-discuss] Qemu-system-sparc: What would I need to
> change to add functionality to save the nvram content between
> boots ? (Laurent Vivier)
> 3. Re: [Qemu-discuss] Qemu-system-sparc: What would I need to
> change to add functionality to save the nvram content between
> boots ? (Programmingkid)
> 4. Re: [Qemu-discuss] Qemu-system-sparc: What would I need to
> change to add functionality to save the nvram content between
> boots ? (Mark Cave-Ayland)
> 5. Re: [Qemu-discuss] Qemu-system-sparc: What would I need to
> change to add functionality to save the nvram content between
> boots ? (Programmingkid)
> 6. Re: [Qemu-discuss] Qemu-system-sparc: What would I need to
> change to add functionality to save the nvram content between
> boots ? (Bodo Eggert)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 11 Sep 2015 17:07:49 -0400
> From: Programmingkid <programmingkidx(a)gmail.com>
> To: Laurent Vivier <laurent(a)vivier.eu>
> Cc: jim(a)suresafe.co.uk, The OpenBIOS Mailinglist
> <openbios(a)openbios.org>, Mark Cave-Ayland
> <mark.cave-ayland(a)ilande.co.uk>, qemu-discuss
> <qemu-discuss(a)nongnu.org>
> Subject: Re: [OpenBIOS] [Qemu-discuss] Qemu-system-sparc: What would I
> need to change to add functionality to save the nvram content
> between
> boots ?
> Message-ID: <98CF0A2F-43B1-4E68-8535-42D69DFC3D25(a)gmail.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Sep 11, 2015, at 4:09 PM, Laurent Vivier wrote:
>
> >
> >
> > Le 11/09/2015 20:01, Programmingkid a ?crit :
> >>
> >> On Sep 11, 2015, at 12:00 PM, qemu-discuss-request(a)nongnu.org
> >> <mailto:qemu-discuss-request@nongnu.org> wrote:
> >>
> >>> On 10/09/2015 8:58 AM, Maximilian H. wrote:
> >>>> Hello,
> >>>>
> >>>> I was looking into what parts would need change to save and restore
> the
> >>>> nvram content for the qemu-system-sparc vm between boots.
> >>>>
> >>>> I see the code in hw/timer/m48t59.c that implements the nvram.
> >>>>
> >>>> So some questions arise, and before I spend too much time poking
> around
> >>>> the still unknown code, I'd thought I ask first.
> >>>>
> >>>> 1. Command line processing starts in vl.c in the main fct there ? Can
> I
> >>>> add a command line argument there, say "-sparcnvram" ?
> >>>>
> >>>> 2. In hw/timer/m48t59.c has no functionality that I see from having a
> >>>> look at it (not in depth) to save or restore the nvram's contents for
> >>>> sparc. Is there a general facility that qemu has that provides such a
> >>>> functionality - i.e. is there a general qemu save and restore
> framework ?
> >>>>
> >>>> 3. Is there an example somebody could point me to that implements
> >>>> something similar ? Imitation is the sincerest of flattery ....
> >>>>
> >>>> 4. All the alarm and watchdog functionality that the m48t08 provides,
> is
> >>>> that used on sparc too ?
> >>>>
> >>>> 5. Besides what is in
> >>>> http://wiki.qemu.org/Documentation/GettingStartedDevelopers, is there
> >>>> some qemu coding documentation to make it faster for somebody
> unfamilar
> >>>> with qemu's code like me to be able to implement something ? I'd like
> to
> >>>> spend a few evenings on this, produce a patch and move on.
> >>>>
> >>>> Thanks
> >>>> BR
> >>>> Max.
> >>>
> >>
> >> This sounds like a good idea. Having OpenBIOS settings actually be saved
> >> between boots
> >> would make things more real.
> >>
> >> Mark, do you think it is possible for a QEMU command line option to
> >> actually load the
> >> saved OpenBIOS settings from a file and restore them into memory? I'm
> >> thinking something
> >> along the lines of -prom-memory <file name>.
> >
> > Nostalgia: a seven years old thread, out of date now:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2008-05/msg00002.html
> >
> >>
> >> Max, there is a project that you should probably look at called
> >> OpenBIOS. It implements
> >> an implementation of Open Firmware. Here is where more info can be
> >> found: http://www.openfirmware.info/Welcome_to_OpenBIOS. If you do want
> >> to implement this feature,
> >> it would help to know how the BIOS is implemented.
> >
> > Laurent
>
> Could you send the patch please?
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 12 Sep 2015 09:46:48 +0200
> From: Laurent Vivier <laurent(a)vivier.eu>
> To: Programmingkid <programmingkidx(a)gmail.com>
> Cc: jim(a)suresafe.co.uk, The OpenBIOS Mailinglist
> <openbios(a)openbios.org>, Mark Cave-Ayland
> <mark.cave-ayland(a)ilande.co.uk>, qemu-discuss
> <qemu-discuss(a)nongnu.org>
> Subject: Re: [OpenBIOS] [Qemu-discuss] Qemu-system-sparc: What would I
> need to change to add functionality to save the nvram content
> between
> boots ?
> Message-ID: <55F3D868.3030702(a)vivier.eu>
> Content-Type: text/plain; charset=windows-1252
>
>
>
> Le 11/09/2015 23:07, Programmingkid a ?crit :
> >
> > On Sep 11, 2015, at 4:09 PM, Laurent Vivier wrote:
> >
> >>
> >>
> >> Le 11/09/2015 20:01, Programmingkid a ?crit :
> >>>
> >>> On Sep 11, 2015, at 12:00 PM, qemu-discuss-request(a)nongnu.org
> >>> <mailto:qemu-discuss-request@nongnu.org> wrote:
> >>>
> >>>> On 10/09/2015 8:58 AM, Maximilian H. wrote:
> >>>>> Hello,
> >>>>>
> >>>>> I was looking into what parts would need change to save and restore
> the
> >>>>> nvram content for the qemu-system-sparc vm between boots.
> >>>>>
> >>>>> I see the code in hw/timer/m48t59.c that implements the nvram.
> >>>>>
> >>>>> So some questions arise, and before I spend too much time poking
> around
> >>>>> the still unknown code, I'd thought I ask first.
> >>>>>
> >>>>> 1. Command line processing starts in vl.c in the main fct there ?
> Can I
> >>>>> add a command line argument there, say "-sparcnvram" ?
> >>>>>
> >>>>> 2. In hw/timer/m48t59.c has no functionality that I see from having a
> >>>>> look at it (not in depth) to save or restore the nvram's contents for
> >>>>> sparc. Is there a general facility that qemu has that provides such a
> >>>>> functionality - i.e. is there a general qemu save and restore
> framework ?
> >>>>>
> >>>>> 3. Is there an example somebody could point me to that implements
> >>>>> something similar ? Imitation is the sincerest of flattery ....
> >>>>>
> >>>>> 4. All the alarm and watchdog functionality that the m48t08
> provides, is
> >>>>> that used on sparc too ?
> >>>>>
> >>>>> 5. Besides what is in
> >>>>> http://wiki.qemu.org/Documentation/GettingStartedDevelopers, is
> there
> >>>>> some qemu coding documentation to make it faster for somebody
> unfamilar
> >>>>> with qemu's code like me to be able to implement something ? I'd
> like to
> >>>>> spend a few evenings on this, produce a patch and move on.
> >>>>>
> >>>>> Thanks
> >>>>> BR
> >>>>> Max.
> >>>>
> >>>
> >>> This sounds like a good idea. Having OpenBIOS settings actually be
> saved
> >>> between boots
> >>> would make things more real.
> >>>
> >>> Mark, do you think it is possible for a QEMU command line option to
> >>> actually load the
> >>> saved OpenBIOS settings from a file and restore them into memory? I'm
> >>> thinking something
> >>> along the lines of -prom-memory <file name>.
> >>
> >> Nostalgia: a seven years old thread, out of date now:
> >>
> >> https://lists.gnu.org/archive/html/qemu-devel/2008-05/msg00002.html
> >>
> >>>
> >>> Max, there is a project that you should probably look at called
> >>> OpenBIOS. It implements
> >>> an implementation of Open Firmware. Here is where more info can be
> >>> found: http://www.openfirmware.info/Welcome_to_OpenBIOS. If you do
> want
> >>> to implement this feature,
> >>> it would help to know how the BIOS is implemented.
> >>
> >> Laurent
> >
> > Could you send the patch please?
> >
>
> The patch is attached to the mail in the thread. Anyway, I don't think
> it applies now.
>
> Laurent
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 12 Sep 2015 14:01:33 -0400
> From: Programmingkid <programmingkidx(a)gmail.com>
> To: Laurent Vivier <laurent(a)vivier.eu>
> Cc: jim(a)suresafe.co.uk, The OpenBIOS Mailinglist
> <openbios(a)openbios.org>, Mark Cave-Ayland
> <mark.cave-ayland(a)ilande.co.uk>, qemu-discuss
> <qemu-discuss(a)nongnu.org>
> Subject: Re: [OpenBIOS] [Qemu-discuss] Qemu-system-sparc: What would I
> need to change to add functionality to save the nvram content
> between
> boots ?
> Message-ID: <AF2A4476-8D57-4A73-911E-1F4658F6A5E5(a)gmail.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Sep 12, 2015, at 3:46 AM, Laurent Vivier wrote:
>
> >
> >
> > Le 11/09/2015 23:07, Programmingkid a ?crit :
> >>
> >> On Sep 11, 2015, at 4:09 PM, Laurent Vivier wrote:
> >>
> >>>
> >>>
> >>> Le 11/09/2015 20:01, Programmingkid a ?crit :
> >>>>
> >>>> On Sep 11, 2015, at 12:00 PM, qemu-discuss-request(a)nongnu.org
> >>>> <mailto:qemu-discuss-request@nongnu.org> wrote:
> >>>>
> >>>>> On 10/09/2015 8:58 AM, Maximilian H. wrote:
> >>>>>> Hello,
> >>>>>>
> >>>>>> I was looking into what parts would need change to save and restore
> the
> >>>>>> nvram content for the qemu-system-sparc vm between boots.
> >>>>>>
> >>>>>> I see the code in hw/timer/m48t59.c that implements the nvram.
> >>>>>>
> >>>>>> So some questions arise, and before I spend too much time poking
> around
> >>>>>> the still unknown code, I'd thought I ask first.
> >>>>>>
> >>>>>> 1. Command line processing starts in vl.c in the main fct there ?
> Can I
> >>>>>> add a command line argument there, say "-sparcnvram" ?
> >>>>>>
> >>>>>> 2. In hw/timer/m48t59.c has no functionality that I see from having
> a
> >>>>>> look at it (not in depth) to save or restore the nvram's contents
> for
> >>>>>> sparc. Is there a general facility that qemu has that provides such
> a
> >>>>>> functionality - i.e. is there a general qemu save and restore
> framework ?
> >>>>>>
> >>>>>> 3. Is there an example somebody could point me to that implements
> >>>>>> something similar ? Imitation is the sincerest of flattery ....
> >>>>>>
> >>>>>> 4. All the alarm and watchdog functionality that the m48t08
> provides, is
> >>>>>> that used on sparc too ?
> >>>>>>
> >>>>>> 5. Besides what is in
> >>>>>> http://wiki.qemu.org/Documentation/GettingStartedDevelopers, is
> there
> >>>>>> some qemu coding documentation to make it faster for somebody
> unfamilar
> >>>>>> with qemu's code like me to be able to implement something ? I'd
> like to
> >>>>>> spend a few evenings on this, produce a patch and move on.
> >>>>>>
> >>>>>> Thanks
> >>>>>> BR
> >>>>>> Max.
> >>>>>
> >>>>
> >>>> This sounds like a good idea. Having OpenBIOS settings actually be
> saved
> >>>> between boots
> >>>> would make things more real.
> >>>>
> >>>> Mark, do you think it is possible for a QEMU command line option to
> >>>> actually load the
> >>>> saved OpenBIOS settings from a file and restore them into memory? I'm
> >>>> thinking something
> >>>> along the lines of -prom-memory <file name>.
> >>>
> >>> Nostalgia: a seven years old thread, out of date now:
> >>>
> >>> https://lists.gnu.org/archive/html/qemu-devel/2008-05/msg00002.html
> >>>
> >>>>
> >>>> Max, there is a project that you should probably look at called
> >>>> OpenBIOS. It implements
> >>>> an implementation of Open Firmware. Here is where more info can be
> >>>> found: http://www.openfirmware.info/Welcome_to_OpenBIOS. If you do
> want
> >>>> to implement this feature,
> >>>> it would help to know how the BIOS is implemented.
> >>>
> >>> Laurent
> >>
> >> Could you send the patch please?
> >>
> >
> > The patch is attached to the mail in the thread. Anyway, I don't think
> > it applies now.
> >
> > Laurent
>
> The extension on the patch is incorrectly set to .bin. Had to change it to
> .txt to make it work. Thanks.
> I don't have the original poster's email address so I can't send it to
> him. Hopefully he had read these
> emails and knows about it.
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 13 Sep 2015 18:14:05 +0100
> From: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk>
> To: Programmingkid <programmingkidx(a)gmail.com>, qemu-discuss
> <qemu-discuss(a)nongnu.org>
> Cc: jim(a)suresafe.co.uk, The OpenBIOS Mailinglist
> <openbios(a)openbios.org>
> Subject: Re: [OpenBIOS] [Qemu-discuss] Qemu-system-sparc: What would I
> need to change to add functionality to save the nvram content
> between
> boots ?
> Message-ID: <55F5AEDD.3040801(a)ilande.co.uk>
> Content-Type: text/plain; charset=windows-1252
>
> On 11/09/15 19:01, Programmingkid wrote:
>
> > On Sep 11, 2015, at 12:00 PM, qemu-discuss-request(a)nongnu.org
> > <mailto:qemu-discuss-request@nongnu.org> wrote:
> >
> >> On 10/09/2015 8:58 AM, Maximilian H. wrote:
> >>> Hello,
> >>>
> >>> I was looking into what parts would need change to save and restore the
> >>> nvram content for the qemu-system-sparc vm between boots.
> >>>
> >>> I see the code in hw/timer/m48t59.c that implements the nvram.
> >>>
> >>> So some questions arise, and before I spend too much time poking around
> >>> the still unknown code, I'd thought I ask first.
> >>>
> >>> 1. Command line processing starts in vl.c in the main fct there ? Can I
> >>> add a command line argument there, say "-sparcnvram" ?
> >>>
> >>> 2. In hw/timer/m48t59.c has no functionality that I see from having a
> >>> look at it (not in depth) to save or restore the nvram's contents for
> >>> sparc. Is there a general facility that qemu has that provides such a
> >>> functionality - i.e. is there a general qemu save and restore
> framework ?
> >>>
> >>> 3. Is there an example somebody could point me to that implements
> >>> something similar ? Imitation is the sincerest of flattery ....
> >>>
> >>> 4. All the alarm and watchdog functionality that the m48t08 provides,
> is
> >>> that used on sparc too ?
> >>>
> >>> 5. Besides what is in
> >>> http://wiki.qemu.org/Documentation/GettingStartedDevelopers, is there
> >>> some qemu coding documentation to make it faster for somebody unfamilar
> >>> with qemu's code like me to be able to implement something ? I'd like
> to
> >>> spend a few evenings on this, produce a patch and move on.
> >>>
> >>> Thanks
> >>> BR
> >>> Max.
> >>
> >
> > This sounds like a good idea. Having OpenBIOS settings actually be saved
> > between boots
> > would make things more real.
> >
> > Mark, do you think it is possible for a QEMU command line option to
> > actually load the
> > saved OpenBIOS settings from a file and restore them into memory? I'm
> > thinking something
> > along the lines of -prom-memory <file name>.
> >
> > Max, there is a project that you should probably look at called
> > OpenBIOS. It implements
> > an implementation of Open Firmware. Here is where more info can be
> > found: http://www.openfirmware.info/Welcome_to_OpenBIOS. If you do want
> > to implement this feature,
> > it would help to know how the BIOS is implemented.
>
> >From memory the reason this hasn't been done is because the NVRAM
> interface is used across multiple architectures and there hasn't been a
> solution devised that would work well enough for all of them. Then again
> as the BIOSs involved have continued to develop, it may be now that some
> of the issues can now be solved so it never hurts to ask on the -devel
> list.
>
> May I ask why you want to save the NVRAM state between boots on SPARC?
> My guess would be that you're using a real SS-5 PROM image and looking
> to avoid having to type boot commands into the terminal after every
> reset. If this is the case then you may be pleasantly surprised using
> QEMU 2.4 with the built-in OpenBIOS as there were fixes applied during
> the last development cycle that were enough to allow SunOS 4.1.4 to boot.
>
> If this solution works for you and you are keen use the alarm/watchdog
> features then there may be some scope to add the required features to
> QEMU/OpenBIOS in future.
>
>
> ATB,
>
> Mark.
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 13 Sep 2015 17:55:39 -0400
> From: Programmingkid <programmingkidx(a)gmail.com>
> To: Bodo Eggert <7eggert(a)online.de>
> Cc: jim(a)suresafe.co.uk, The OpenBIOS Mailinglist
> <openbios(a)openbios.org>, Mark Cave-Ayland
> <mark.cave-ayland(a)ilande.co.uk>, qemu-discuss
> <qemu-discuss(a)nongnu.org>
> Subject: Re: [OpenBIOS] [Qemu-discuss] Qemu-system-sparc: What would I
> need to change to add functionality to save the nvram content
> between
> boots ?
> Message-ID: <57E81229-4BF3-4354-A896-94070580C3FD(a)gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> On Sep 13, 2015, at 5:50 PM, Bodo Eggert wrote:
>
> > On Sun, 13 Sep 2015, Mark Cave-Ayland wrote:
> >> On 11/09/15 19:01, Programmingkid wrote:
> >
> >>> Mark, do you think it is possible for a QEMU command line option to
> >>> actually load the
> >>> saved OpenBIOS settings from a file and restore them into memory? I'm
> >>> thinking something
> >>> along the lines of -prom-memory <file name>.
> >
> >>> From memory the reason this hasn't been done is because the NVRAM
> >> interface is used across multiple architectures and there hasn't been a
> >> solution devised that would work well enough for all of them. Then again
> >> as the BIOSs involved have continued to develop, it may be now that some
> >> of the issues can now be solved so it never hurts to ask on the -devel
> list.
> >
> > I'm wondering, why wouldn't it be enough to memmap a nvram file instead
> of
> > mallocing (or whatever) the memory area?
>
> What advantage does mmap() have over malloc()? I think malloc() is a lot
> more
> familiar to use than mmap().
>
>
> ------------------------------
>
> Message: 6
> Date: Sun, 13 Sep 2015 23:50:31 +0200 (CEST)
> From: Bodo Eggert <7eggert(a)online.de>
> To: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk>
> Cc: jim(a)suresafe.co.uk, Programmingkid <programmingkidx(a)gmail.com>,
> The OpenBIOS Mailinglist <openbios(a)openbios.org>, qemu-discuss
> <qemu-discuss(a)nongnu.org>
> Subject: Re: [OpenBIOS] [Qemu-discuss] Qemu-system-sparc: What would I
> need to change to add functionality to save the nvram content
> between
> boots ?
> Message-ID: <alpine.DEB.2.11.1509132343080.9673@be10>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Sun, 13 Sep 2015, Mark Cave-Ayland wrote:
> > On 11/09/15 19:01, Programmingkid wrote:
>
> > > Mark, do you think it is possible for a QEMU command line option to
> > > actually load the
> > > saved OpenBIOS settings from a file and restore them into memory? I'm
> > > thinking something
> > > along the lines of -prom-memory <file name>.
>
> > >From memory the reason this hasn't been done is because the NVRAM
> > interface is used across multiple architectures and there hasn't been a
> > solution devised that would work well enough for all of them. Then again
> > as the BIOSs involved have continued to develop, it may be now that some
> > of the issues can now be solved so it never hurts to ask on the -devel
> list.
>
> I'm wondering, why wouldn't it be enough to memmap a nvram file instead of
> mallocing (or whatever) the memory area?
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> --
> OpenBIOS mailing list
> OpenBIOS(a)openbios.org
> http://www.openfirmware.info/mailman/listinfo/openbios
>
> ------------------------------
>
> End of OpenBIOS Digest, Vol 125, Issue 2
> ****************************************
>
