On Thu, Sep 05, 2019 at 08:31:34AM +, Thomas Hellstrom wrote:
> On Thu, 2019-09-05 at 09:05 +0200, Gerd Hoffmann wrote:
> > Add struct drm_vma_offset_manager to vma_private, initialize it and
> > pass it to ttm_bo_device_init().
> >
> > With this in place the last user of ttm's embedded vma of
Hi,
> > The qemu stdvga (bochs driver) has 16 MB vram by default and can be
> > configured to have up to 256 MB. Plenty of room even for multiple 4k
> > framebuffers if needed. So for the bochs driver all the ttm bo
> > migration logic is not needed, it could just store everything in vram.
>
Hi,
> If not for TTM, what would be the alternative? One VMA manager per
> memory region per device?
Depends pretty much on the device.
The cirrus is a display device with only 4 MB of vram. You can't fit
much in there. A single 1024x768 @ 24bpp framebuffer needs more 50%
of the video memory
On Thu, Feb 21, 2019 at 10:44:06AM -0800, Alistair Francis wrote:
> On Thu, Feb 21, 2019 at 3:52 AM kra...@redhat.com wrote:
> >
> > On Thu, Feb 21, 2019 at 12:33:03AM +, Alistair Francis wrote:
> > > When running RISC-V QEMU with the Bochs device attached via PCI
On Thu, Feb 21, 2019 at 12:33:03AM +, Alistair Francis wrote:
> When running RISC-V QEMU with the Bochs device attached via PCIe the
> probe of the Bochs device fails with:
> [drm:bochs_hw_init] *ERROR* ID mismatch
>
> This was introduced by this commit:
> 7780eb9ce8 bochs: convert to
On Wed, Sep 19, 2018 at 07:09:53AM +, An, Jiandi wrote:
> With virtio gpu ttm-pages being dma mapped, dma sync is needed when
> swiotlb is used as bounce buffers, before TRANSFER_TO_HOST_2D/3D
> commands are sent.
Pushed to drm-misc-next.
thanks,
Gerd
__
