Proposal for a low-level Linux display framework

2011-09-17 Thread Laurent Pinchart
On Thursday 15 September 2011 19:05:00 Alan Cox wrote: > On Thu, 15 Sep 2011 10:50:32 -0500 > Keith Packard wrote: > > On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen wrote: > > > 1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if > > > the plan is to make DRM the core Linux d

Proposal for a low-level Linux display framework

2011-09-17 Thread Alan Cox
> Just tell the X driver to not use acceleration, and it you won't get > any acceleration used, then you get complete stability. If a driver > writer wants to turn off all accel in the kernel driver, it can, its In fact one thing we actually need really is a "dumb" KMS X server to replace the fbde

Proposal for a low-level Linux display framework

2011-09-17 Thread Dave Airlie
> > Is it? Well, okay, I don't want to use any acceleration that can crash my > machine, where can I select it, preferably as compile time option? I didn't > find > such a thing for Intel or Radeon. Don't say, I should rely on userspace here > or > use fbdev for this. Just tell the X driver to n

Proposal for a low-level Linux display framework

2011-09-17 Thread Florian Tobias Schandinat
On 09/17/2011 06:23 PM, Dave Airlie wrote: >> >> Is it? Well, okay, I don't want to use any acceleration that can crash my >> machine, where can I select it, preferably as compile time option? I didn't >> find >> such a thing for Intel or Radeon. Don't say, I should rely on userspace here >> or >

Proposal for a low-level Linux display framework

2011-09-17 Thread Florian Tobias Schandinat
On 09/17/2011 04:47 PM, Dave Airlie wrote: >> >> I disagree. This depends on the functionality the hardware has, the desired >> userspace and the manpower one has to do it. And of course if you just want >> fb >> having fb via DRM/KMS has some overhead/bloat. It's perfectly okay to have >> just >

Proposal for a low-level Linux display framework

2011-09-17 Thread Dave Airlie
> > I disagree. This depends on the functionality the hardware has, the desired > userspace and the manpower one has to do it. And of course if you just want fb > having fb via DRM/KMS has some overhead/bloat. It's perfectly okay to have > just > an fb driver for devices that can't do more anyway.

Proposal for a low-level Linux display framework

2011-09-17 Thread Felipe Contreras
On Thu, Sep 15, 2011 at 9:58 PM, Alan Cox wrote: >> One of my biggest problems with KMS is that it has (naturally) a lot more >> complexity than the fb API which leads to instability. Basically it's very > > It shouldn't do - and a sample of one (your machine) is not a > statistically valid set. F

Proposal for a low-level Linux display framework

2011-09-17 Thread Alex Deucher
On Sat, Sep 17, 2011 at 3:06 PM, Florian Tobias Schandinat wrote: > On 09/17/2011 06:23 PM, Dave Airlie wrote: >>> >>> Is it? Well, okay, I don't want to use any acceleration that can crash my >>> machine, where can I select it, preferably as compile time option? I didn't >>> find >>> such a thin

Whitespace cleanups in drm/i915

2011-09-17 Thread Eugeni Dodonov
or option 1, and then 3, in this order. -- Eugeni Dodonov <http://eugeni.dodonov.net/> -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20110917/a8d83da2/attachment.html>

[PATCH] RFCv2: omapdrm DRM/KMS driver for TI OMAP platforms

2011-09-17 Thread Rob Clark
omap_crtc->id = id; + crtc = &omap_crtc->base; + drm_crtc_init(dev, crtc, &omap_crtc_funcs); + drm_crtc_helper_add(crtc, &omap_crtc_helper_funcs); + + return crtc; + +fail: + if (crtc) { + drm_crtc_cleanup(crtc); + kfree(omap_crtc);

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Laurent Pinchart
Hi everybody, On Thursday 15 September 2011 20:39:21 Florian Tobias Schandinat wrote: > On 09/15/2011 05:52 PM, Alex Deucher wrote: > > > > Please don't claim that the DRM developers do not want to cooperate. > > I realize that people have strong opinions about existing APIs, put > > there has bee

Proposal for a low-level Linux display framework

2011-09-17 Thread Florian Tobias Schandinat
On 09/17/2011 03:16 PM, Rob Clark wrote: >>From userspace perspective, fbdev doesn't go away. It is just a > legacy interface provided on top of DRM/KMS driver mostly via helper > functions. With this approach, you get the richer KMS API (and all > the related plumbing for hotplug, EDID parsing,

No subject

2011-09-17 Thread
legacy interface provided on top of DRM/KMS driver mostly via helper functions. With this approach, you get the richer KMS API (and all the related plumbing for hotplug, EDID parsing, multi-head support, flipping, etc) for userspace stuff that needs that, but can keep the fbdev userspace interface

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Laurent Pinchart
On Thursday 15 September 2011 19:05:00 Alan Cox wrote: > On Thu, 15 Sep 2011 10:50:32 -0500 > Keith Packard wrote: > > On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen wrote: > > > 1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if > > > the plan is to make DRM the core Linux d

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Alex Deucher
On Sat, Sep 17, 2011 at 3:06 PM, Florian Tobias Schandinat wrote: > On 09/17/2011 06:23 PM, Dave Airlie wrote: >>> >>> Is it? Well, okay, I don't want to use any acceleration that can crash my >>> machine, where can I select it, preferably as compile time option? I didn't >>> find >>> such a thin

[Bug 33077] Broken rendering with black areas in Doom3-demo also falls to 3-4 fps time to time

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=33077 --- Comment #13 from Tom Stellard 2011-09-17 13:35:54 PDT --- Is this still an issue on r300g with the latest code from git? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because

[Bug 33077] Broken rendering with black areas in Doom3-demo also falls to 3-4 fps time to time

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=33077 --- Comment #13 from Tom Stellard 2011-09-17 13:35:54 PDT --- Is this still an issue on r300g with the latest code from git? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because

[Bug 40062] in etqw the strogg radar is black (regression)

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=40062 --- Comment #7 from Tom Stellard 2011-09-17 13:32:58 PDT --- Created an attachment (id=51295) View: https://bugs.freedesktop.org/attachment.cgi?id=51295 Review: https://bugs.freedesktop.org/review?bug=40062&attachment=51295 Possible Fix Can

[Bug 40062] in etqw the strogg radar is black (regression)

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=40062 --- Comment #7 from Tom Stellard 2011-09-17 13:32:58 PDT --- Created an attachment (id=51295) View: https://bugs.freedesktop.org/attachment.cgi?id=51295 Review: https://bugs.freedesktop.org/review?bug=40062&attachment=51295 Possible Fix Can

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Alan Cox
> Just tell the X driver to not use acceleration, and it you won't get > any acceleration used, then you get complete stability. If a driver > writer wants to turn off all accel in the kernel driver, it can, its In fact one thing we actually need really is a "dumb" KMS X server to replace the fbde

Re: Whitespace cleanups in drm/i915

2011-09-17 Thread Eugeni Dodonov
On Thu, Sep 15, 2011 at 22:37, Keith Packard wrote: > > I've got this nice patch from Akshay Joshi that removes almost all of > the checkpatch.pl warnings from drm/i915. If I don't merge it now, it's > going to go stale and be useless; if I merge it only to drm-intel-next, > it will be the source

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Corbin Simpson
On Sat, Sep 17, 2011 at 12:06 PM, Florian Tobias Schandinat wrote: > Again, you seem to not understand my reasoning. The "if" is the problem, it's > the kernels job to ensure stability. Allowing the userspace to decide whether > it > crashes my machine is not acceptable to me. > I do not claim th

Proposal for a low-level Linux display framework

2011-09-17 Thread Corbin Simpson
On Sat, Sep 17, 2011 at 12:06 PM, Florian Tobias Schandinat wrote: > Again, you seem to not understand my reasoning. The "if" is the problem, it's > the kernels job to ensure stability. Allowing the userspace to decide whether > it > crashes my machine is not acceptable to me. > I do not claim th

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Florian Tobias Schandinat
On 09/17/2011 06:23 PM, Dave Airlie wrote: >> >> Is it? Well, okay, I don't want to use any acceleration that can crash my >> machine, where can I select it, preferably as compile time option? I didn't >> find >> such a thing for Intel or Radeon. Don't say, I should rely on userspace here >> or >

Proposal for a low-level Linux display framework

2011-09-17 Thread Rob Clark
On Sat, Sep 17, 2011 at 11:11 AM, Florian Tobias Schandinat wrote: > On 09/17/2011 03:16 PM, Rob Clark wrote: >>>From userspace perspective, fbdev doesn't go away. ?It is just a >> legacy interface provided on top of DRM/KMS driver mostly via helper >> functions. ?With this approach, you get the r

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Dave Airlie
> > Is it? Well, okay, I don't want to use any acceleration that can crash my > machine, where can I select it, preferably as compile time option? I didn't > find > such a thing for Intel or Radeon. Don't say, I should rely on userspace here > or > use fbdev for this. Just tell the X driver to n

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Florian Tobias Schandinat
On 09/17/2011 04:47 PM, Dave Airlie wrote: >> >> I disagree. This depends on the functionality the hardware has, the desired >> userspace and the manpower one has to do it. And of course if you just want >> fb >> having fb via DRM/KMS has some overhead/bloat. It's perfectly okay to have >> just >

Proposal for a low-level Linux display framework

2011-09-17 Thread Rob Clark
On Sat, Sep 17, 2011 at 9:44 AM, Felipe Contreras wrote: > On Thu, Sep 15, 2011 at 9:58 PM, Alan Cox wrote: >>> One of my biggest problems with KMS is that it has (naturally) a lot more >>> complexity than the fb API which leads to instability. Basically it's very >> >> It shouldn't do - and a sa

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Rob Clark
On Sat, Sep 17, 2011 at 11:11 AM, Florian Tobias Schandinat wrote: > On 09/17/2011 03:16 PM, Rob Clark wrote: >>>From userspace perspective, fbdev doesn't go away.  It is just a >> legacy interface provided on top of DRM/KMS driver mostly via helper >> functions.  With this approach, you get the r

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Dave Airlie
> > I disagree. This depends on the functionality the hardware has, the desired > userspace and the manpower one has to do it. And of course if you just want fb > having fb via DRM/KMS has some overhead/bloat. It's perfectly okay to have > just > an fb driver for devices that can't do more anyway.

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Florian Tobias Schandinat
On 09/17/2011 03:16 PM, Rob Clark wrote: >>From userspace perspective, fbdev doesn't go away. It is just a > legacy interface provided on top of DRM/KMS driver mostly via helper > functions. With this approach, you get the richer KMS API (and all > the related plumbing for hotplug, EDID parsing,

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Rob Clark
On Sat, Sep 17, 2011 at 9:44 AM, Felipe Contreras wrote: > On Thu, Sep 15, 2011 at 9:58 PM, Alan Cox wrote: >>> One of my biggest problems with KMS is that it has (naturally) a lot more >>> complexity than the fb API which leads to instability. Basically it's very >> >> It shouldn't do - and a sa

Re: Proposal for a low-level Linux display framework

2011-09-17 Thread Felipe Contreras
On Thu, Sep 15, 2011 at 9:58 PM, Alan Cox wrote: >> One of my biggest problems with KMS is that it has (naturally) a lot more >> complexity than the fb API which leads to instability. Basically it's very > > It shouldn't do - and a sample of one (your machine) is not a > statistically valid set. F

[Bug 39309] vdpau decodes noise on rv350

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=39309 --- Comment #1 from almos 2011-09-17 04:09:07 PDT --- I tried this again after seeing how much work has been committed to g3dvl recently, but nothing changed. Now I also tried it with MPEG1 videos: instead of the wrong rendering it enters an infi

[Bug 39309] vdpau decodes noise on rv350

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=39309 --- Comment #1 from almos 2011-09-17 04:09:07 PDT --- I tried this again after seeing how much work has been committed to g3dvl recently, but nothing changed. Now I also tried it with MPEG1 videos: instead of the wrong rendering it enters an infi

[PATCH 4/7] swiotlb: Expose swiotlb_nr_tlb function to modules as swiotlb_enabled

2011-09-17 Thread FUJITA Tomonori
On Tue, 13 Sep 2011 10:12:47 -0400 Konrad Rzeszutek Wilk wrote: > As a mechanism to detect whether SWIOTLB is enabled or not. > And as such, we might as well wrap it within an 'swiotlb_enabled()' > function that will call the swiotlb_nr_tlb. > > We also fix the spelling - it was swioltb instead

[Bug 39308] mplayer -vo vdpau draws incorrectly on rv350

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=39308 --- Comment #1 from almos 2011-09-17 04:01:25 PDT --- I tried this again after seeing how much work has been committed to g3dvl recently, but nothing changed. Except that now Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion

[Bug 39308] mplayer -vo vdpau draws incorrectly on rv350

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=39308 --- Comment #1 from almos 2011-09-17 04:01:25 PDT --- I tried this again after seeing how much work has been committed to g3dvl recently, but nothing changed. Except that now Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion

[Bug 40062] in etqw the strogg radar is black (regression)

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=40062 --- Comment #6 from almos 2011-09-17 03:42:52 PDT --- Created an attachment (id=51285) --> (https://bugs.freedesktop.org/attachment.cgi?id=51285) stderr_good.txt.gz I applied the reverse of commit 217cd216eac65983004ca77a9e49dbfad1b720b6 to the

[Bug 40062] in etqw the strogg radar is black (regression)

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=40062 --- Comment #6 from almos 2011-09-17 03:42:52 PDT --- Created an attachment (id=51285) --> (https://bugs.freedesktop.org/attachment.cgi?id=51285) stderr_good.txt.gz I applied the reverse of commit 217cd216eac65983004ca77a9e49dbfad1b720b6 to the

[Bug 40062] in etqw the strogg radar is black (regression)

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=40062 --- Comment #5 from almos 2011-09-17 03:40:09 PDT --- Created an attachment (id=51284) --> (https://bugs.freedesktop.org/attachment.cgi?id=51284) stderr_wrong.txt -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email -

[Bug 40062] in etqw the strogg radar is black (regression)

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=40062 --- Comment #5 from almos 2011-09-17 03:40:09 PDT --- Created an attachment (id=51284) --> (https://bugs.freedesktop.org/attachment.cgi?id=51284) stderr_wrong.txt -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email -

[Bug 25764] [RADEON:R600C] glLineStipple gives inconsistent results

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=25764 raoxianhong changed: What|Removed |Added Blocks||40936 -- Configure bugmail: https://bugs.

[Bug 40936] register address overlap make line stipple error

2011-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=40936 raoxianhong changed: What|Removed |Added Depends on||25764 -- Configure bugmail: https://bugs.

[Bug 25764] [RADEON:R600C] glLineStipple gives inconsistent results

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=25764 raoxianhong changed: What|Removed |Added Blocks||40936 -- Configure bugmail: https://bugs.

[Bug 40936] register address overlap make line stipple error

2011-09-17 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=40936 raoxianhong changed: What|Removed |Added Depends on||25764 -- Configure bugmail: https://bugs.