Am 16.04.19 um 13:03 schrieb Daniel Vetter:
> On Tue, Apr 16, 2019 at 12:05 PM Koenig, Christian
> wrote:
>> Am 15.04.19 um 21:17 schrieb Daniel Vetter:
>>> On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann
>>> wrote:
Hi
Am 15.04.19 um 17:54 schrieb Daniel Vetter:
> On Tue, Ap
On Tue, Apr 16, 2019 at 12:05 PM Koenig, Christian
wrote:
>
> Am 15.04.19 um 21:17 schrieb Daniel Vetter:
> > On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann
> > wrote:
> >> Hi
> >>
> >> Am 15.04.19 um 17:54 schrieb Daniel Vetter:
> >>> On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmerma
Am 15.04.19 um 21:17 schrieb Daniel Vetter:
> On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann wrote:
>> Hi
>>
>> Am 15.04.19 um 17:54 schrieb Daniel Vetter:
>>> On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote:
Hi
Am 09.04.19 um 09:12 schrieb kra...@redhat.com:
>>
On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann wrote:
>
> Hi
>
> Am 15.04.19 um 17:54 schrieb Daniel Vetter:
> > On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote:
> >> Hi
> >>
> >> Am 09.04.19 um 09:12 schrieb kra...@redhat.com:
> >>> Hi,
> >>>
> If not for TTM, what wou
Hi
Am 15.04.19 um 17:54 schrieb Daniel Vetter:
> On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 09.04.19 um 09:12 schrieb kra...@redhat.com:
>>> Hi,
>>>
If not for TTM, what would be the alternative? One VMA manager per
memory region per device?
>>>
>
On Mon, Apr 15, 2019 at 05:54:30PM +0200, Daniel Vetter wrote:
> On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote:
> > Hi
> >
> > Am 09.04.19 um 09:12 schrieb kra...@redhat.com:
> > > Hi,
> > >
> > >> If not for TTM, what would be the alternative? One VMA manager per
> > >> mem
On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 09.04.19 um 09:12 schrieb kra...@redhat.com:
> > 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
Am 08.04.19 um 13:59 schrieb Thomas Zimmermann:
[SNIP]
> If not for TTM, what would be the alternative? One VMA manager per
> memory region per device?
Since everybody vital seems to be on this mail thread anyway, let's use
it a bit for brain storming what a possible replacement for TTM should
l
Am 09.04.19 um 10:29 schrieb kra...@redhat.com:
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 coul
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
Am 09.04.19 um 09:12 schrieb kra...@redhat.com:
> 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 si
On Tue, 9 Apr 2019 at 17:12, kra...@redhat.com wrote:
>
> 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.
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
Hi
Am 08.04.19 um 13:10 schrieb Koenig, Christian:
> Well first problem is I'm not sure if that is a good idea. Essentially
> we want to get rid of TTM in the long run.
>
> On the other hand this work might aid with that goal, so it might be
> worth a try.
I see. I'm actually interested in por
Well first problem is I'm not sure if that is a good idea. Essentially
we want to get rid of TTM in the long run.
On the other hand this work might aid with that goal, so it might be
worth a try.
Second is that this might actually not work of hand. The problem is here:
> + /* TODO: This tes
Several simple framebuffer drivers copy most of the TTM code from each
other. The implementation is always the same; except for the name of
some data structures.
As recently discussed, this patch set provides generic TTM memory-
management code for framebuffers with dedicated video memory. It furt
16 matches
Mail list logo
