[Hit send too early on previous mail...]
> The basic device interface looks like
> ...
> +
> +/* Register a memory region at START_ADDR/SIZE. The REGION structure will
> + be initialized appropriately for DEV using CB as the operation set. */
> +extern void cpu_register_memory_region(MemoryRegi
> The basic device interface looks like
> ...
> +
> +/* Register a memory region at START_ADDR/SIZE. The REGION structure will
> + be initialized appropriately for DEV using CB as the operation set. */
> +extern void cpu_register_memory_region(MemoryRegion *region,
> +
On 4/23/10, Richard Henderson wrote:
> On 04/22/2010 01:01 PM, Blue Swirl wrote:
> >> This is also fine. Although by using NULL all you'd get is a qemu
> >> null pointer dereference; I suppose this might get caught and
> >> translated to an cpu exception, but I think it would be preferable
>
On 04/22/2010 01:01 PM, Blue Swirl wrote:
>> This is also fine. Although by using NULL all you'd get is a qemu
>> null pointer dereference; I suppose this might get caught and
>> translated to an cpu exception, but I think it would be preferable
>> long-term to be more explicit about this and f
On 4/22/10, Richard Henderson wrote:
> On 04/22/2010 12:38 PM, Blue Swirl wrote:
> > Subpages are used when there are several devices on the same page.
> > It's needed for at least Sparc32.
>
>
> That's fine.
>
>
> > Subwidth (with NULL) is used mainly to indicate that the device does
> > not
On 04/22/2010 12:38 PM, Blue Swirl wrote:
> Subpages are used when there are several devices on the same page.
> It's needed for at least Sparc32.
That's fine.
> Subwidth (with NULL) is used mainly to indicate that the device does
> not accept accesses in some access widths. Sparc32 and Sparc64 n
On 4/20/10, Richard Henderson wrote:
> Step 1 to implementing alpha-softmmu is to properly handle 64-bit
> I/O operations. Tristan Gingold managed a hack where he buffered
> half of the I/O operation in the host bridge; I think that's not
> something we want to encourage.
>
> I'm a bit confus
