Comment 49 for bug 653714

Revision history for this message
In , Emil-l-velikov (emil-l-velikov) wrote :

(In reply to comment #34)
> > As mentioned it seems like the tiling (pitch) is misset by ~64 (after a quick
> > look at the attached picture)
>
> I'll look around for a doc to understand what you're saying...
>
My knowledge is kinf of flacky in the area, so here is the way I understand it.
Gpus do not always treat and/or use memory on a linear way. It may be handled as a tile with certain dimensions

> > Can you do try and establish if the issue happens in or outside of X, and in
> > which cases
>
> what do you mean by outside X? Framebuffer terminal seemed ok, how can I
> show a graphic without X?
>
Yes I meant the framebuffer. Not sure of many ways to draw stuff on it - directFB is project that normally deals with such things [1]. My main point is to understand if the issue is xf86-video-nouveau or libdrm/kernel related

> >i.e. in X only when drawing an image of dimensions x1 & y1, or
> > less than x2 & greater than y2
>
> You mean rescaling a single image or showing images of different pixel size?
>
> And you really mean drawing (e.g. with office draw) or just showing existing
> images?
>
I meant rendering images of different sizes. Looking at the iceweasel.png at bugs.debian.org indicates not everything rendered exhibits the distortion - would be great to know something specific about the files causing it

Simple tests
* grab the ice weasel picture, open it in a image viewer (and/or browser) - distorted ?
* rescale the image (using gimp or other software), reopen the picture and observe.
* same for the cursor file

Cheers
Emil

[1] http://www.directfb.org/docs/DirectFB_Tutorials/image.html