On 10 November 2014 07:33, Kaiyuan wrote:
> Thanks for your explanation, Peter. In this case of
> timer_read(void *opaque, hwaddr addr, unsigned int size), could
> I think that opaque is a pointer to a register located in mmio
> address? If I cast opaque pointer to corresponding structure,
> the b
> -Origin email-
> From: Peter Maydell
> Sent Time: Friday, November 7, 2014
> To: Kaiyuan
> Cc: QEMU Developers
> Subject: Re: [Qemu-devel] What "opaque" stand for?
>
> On 7 November 2014 14:42, Kaiyuan wrote:
> >
> > Hello, all
&g
Kaiyuan wrote:
> and its meaning confuse me. What does "opaque" stand for?
Opaque is normal everyday word in English. Its dictionary meaning is
here:
http://dictionary.reference.com/browse/opaque
In the context of code code you posted, opaque means that the code gets
passed a pointer to som
On 7 November 2014 14:42, Kaiyuan wrote:
>
> Hello, all
>
> I am reviewing source of Qemu. I can see parameter called "opaque" from a lot
> of function like this:
> //@hw/timer/xilinx_timer.c
> static uint64_t timer_read(void *opaque, hwaddr addr, unsigned int size)
>
> {
> ...
> }
>
>
> , and it
Hello, all
I am reviewing source of Qemu. I can see parameter called "opaque" from a lot
of function like this:
//@hw/timer/xilinx_timer.c
static uint64_t timer_read(void *opaque, hwaddr addr, unsigned int size)
{
...
}
, and its meaning confuse me. What does "opaque" stand for?
Thanks,
Kai
