On Thu, 20 Sep 2018, at 21:43, Cédric Le Goater wrote:
> Andrew,
>
> On 07/14/2017 08:20 AM, Andrew Jeffery wrote:
> > Hi Paolo,
> >
> > Thanks for taking a look!
> >
> > On Thu, 2017-07-13 at 14:05 +0200, Paolo Bonzini wrote:
> >> On 30/06/2017 05:00, Andrew Jeffery wrote:
> >>> This RFC patch
Andrew,
On 07/14/2017 08:20 AM, Andrew Jeffery wrote:
> Hi Paolo,
>
> Thanks for taking a look!
>
> On Thu, 2017-07-13 at 14:05 +0200, Paolo Bonzini wrote:
>> On 30/06/2017 05:00, Andrew Jeffery wrote:
>>> This RFC patch stems from a discussion on a patch for an ADC model[1] where
>>> it
>>> wa
Hi Paolo,
Thanks for taking a look!
On Thu, 2017-07-13 at 14:05 +0200, Paolo Bonzini wrote:
> On 30/06/2017 05:00, Andrew Jeffery wrote:
> > This RFC patch stems from a discussion on a patch for an ADC model[1] where
> > it
> > was pointed out that I should be able to use the .impl member of
> >
On 30/06/2017 05:00, Andrew Jeffery wrote:
> This RFC patch stems from a discussion on a patch for an ADC model[1] where it
> was pointed out that I should be able to use the .impl member of
> MemoryRegionOps to constrain how my read() and write() callbacks where
> invoked.
>
> I tried Phil's sug
Signed-off-by: Andrew Jeffery
---
Hello,
This RFC patch stems from a discussion on a patch for an ADC model[1] where it
was pointed out that I should be able to use the .impl member of
MemoryRegionOps to constrain how my read() and write() callbacks where invoked.
I tried Phil's suggested approa
