Multiple issues with omapdrm

2013-06-07 Thread Dave Airlie
On Thu, Jun 6, 2013 at 9:25 PM, Rob Clark wrote: > On Thu, Jun 6, 2013 at 3:\ Why do you "need" drmOpen("omap")? Is it just a convention to use that kind of name, instead of "omapdrm" style name? >>> >>> all of the /dev/dri/cardN get opened, and then DRM_IOCTL_VERSION ioctl >>> to get th

Re: Multiple issues with omapdrm

2013-06-06 Thread Dave Airlie
On Thu, Jun 6, 2013 at 9:25 PM, Rob Clark wrote: > On Thu, Jun 6, 2013 at 3:\ Why do you "need" drmOpen("omap")? Is it just a convention to use that kind of name, instead of "omapdrm" style name? >>> >>> all of the /dev/dri/cardN get opened, and then DRM_IOCTL_VERSION ioctl >>> to get th

Multiple issues with omapdrm

2013-06-06 Thread Tomi Valkeinen
On 05/06/13 17:58, Rob Clark wrote: > could be udev or something else was triggering the module to load? > Not 100% sure offhand. Well in my case I load them manually. But if there are applications out there, that at the moment use drmOpen("omapdrm"), then the change would break those apps. >> W

Multiple issues with omapdrm

2013-06-06 Thread Rob Clark
On Thu, Jun 6, 2013 at 3:14 AM, Tomi Valkeinen wrote: > On 05/06/13 17:58, Rob Clark wrote: > >> could be udev or something else was triggering the module to load? >> Not 100% sure offhand. > > Well in my case I load them manually. But if there are applications out > there, that at the moment use

Re: Multiple issues with omapdrm

2013-06-06 Thread Tomi Valkeinen
On 05/06/13 17:58, Rob Clark wrote: > could be udev or something else was triggering the module to load? > Not 100% sure offhand. Well in my case I load them manually. But if there are applications out there, that at the moment use drmOpen("omapdrm"), then the change would break those apps. >> W

Re: Multiple issues with omapdrm

2013-06-06 Thread Rob Clark
On Thu, Jun 6, 2013 at 3:14 AM, Tomi Valkeinen wrote: > On 05/06/13 17:58, Rob Clark wrote: > >> could be udev or something else was triggering the module to load? >> Not 100% sure offhand. > > Well in my case I load them manually. But if there are applications out > there, that at the moment use

Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
On 05/06/13 14:52, Rob Clark wrote: > On Wed, Jun 5, 2013 at 7:35 AM, Tomi Valkeinen > wrote: >> On 05/06/13 13:57, Rob Clark wrote: >> >>> 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we >>> need to rename the .ko >> >> Has something been changed that broke that? Or was "omap

Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
On 05/06/13 13:57, Rob Clark wrote: > 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we > need to rename the .ko Has something been changed that broke that? Or was "omapdrm" just a badly chosen name from the start? If drmOpen("omapdrm") works now, doesn't changing the module nam

Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
On 05/06/13 13:43, Rob Clark wrote: > On Wed, Jun 5, 2013 at 4:59 AM, Tomi Valkeinen > wrote: >> Hi, >> >> I did some testing with omapdrm on v3.10-rc1. Here are some issues I >> encountered. >> For most of them I don't have any idea where to even start looking for a >> problem, >> so I hope th

Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
Hi, I did some testing with omapdrm on v3.10-rc1. Here are some issues I encountered. For most of them I don't have any idea where to even start looking for a problem, so I hope that you may have some ideas. dispc_runtime_get/put used in irq context = d

Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 8:16 AM, Tomi Valkeinen wrote: > On 05/06/13 14:52, Rob Clark wrote: >> On Wed, Jun 5, 2013 at 7:35 AM, Tomi Valkeinen >> wrote: >>> On 05/06/13 13:57, Rob Clark wrote: >>> 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we need to rename the .ko

Re: Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
On 05/06/13 14:52, Rob Clark wrote: > On Wed, Jun 5, 2013 at 7:35 AM, Tomi Valkeinen wrote: >> On 05/06/13 13:57, Rob Clark wrote: >> >>> 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we >>> need to rename the .ko >> >> Has something been changed that broke that? Or was "omapdrm

Re: Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
On 05/06/13 13:57, Rob Clark wrote: > 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we > need to rename the .ko Has something been changed that broke that? Or was "omapdrm" just a badly chosen name from the start? If drmOpen("omapdrm") works now, doesn't changing the module nam

Re: Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
On 05/06/13 13:43, Rob Clark wrote: > On Wed, Jun 5, 2013 at 4:59 AM, Tomi Valkeinen wrote: >> Hi, >> >> I did some testing with omapdrm on v3.10-rc1. Here are some issues I >> encountered. >> For most of them I don't have any idea where to even start looking for a >> problem, >> so I hope that

Multiple issues with omapdrm

2013-06-05 Thread Tomi Valkeinen
Hi, I did some testing with omapdrm on v3.10-rc1. Here are some issues I encountered. For most of them I don't have any idea where to even start looking for a problem, so I hope that you may have some ideas. dispc_runtime_get/put used in irq context = d

Re: Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 8:16 AM, Tomi Valkeinen wrote: > On 05/06/13 14:52, Rob Clark wrote: >> On Wed, Jun 5, 2013 at 7:35 AM, Tomi Valkeinen wrote: >>> On 05/06/13 13:57, Rob Clark wrote: >>> 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we need to rename the .ko >>>

Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 7:35 AM, Tomi Valkeinen wrote: > On 05/06/13 13:57, Rob Clark wrote: > >> 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we >> need to rename the .ko > > Has something been changed that broke that? Or was "omapdrm" just a > badly chosen name from the start?

Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 6:43 AM, Rob Clark wrote: > On Wed, Jun 5, 2013 at 4:59 AM, Tomi Valkeinen > wrote: >> Hi, >> >> I did some testing with omapdrm on v3.10-rc1. Here are some issues I >> encountered. >> For most of them I don't have any idea where to even start looking for a >> problem, >

Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 4:59 AM, Tomi Valkeinen wrote: > Hi, > > I did some testing with omapdrm on v3.10-rc1. Here are some issues I > encountered. > For most of them I don't have any idea where to even start looking for a > problem, > so I hope that you may have some ideas. > > > dispc_runtime_

Re: Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 7:35 AM, Tomi Valkeinen wrote: > On 05/06/13 13:57, Rob Clark wrote: > >> 1) drmOpen("omap") will try to modprobe "omap", not "omapdrm" so we >> need to rename the .ko > > Has something been changed that broke that? Or was "omapdrm" just a > badly chosen name from the start?

Re: Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 6:43 AM, Rob Clark wrote: > On Wed, Jun 5, 2013 at 4:59 AM, Tomi Valkeinen wrote: >> Hi, >> >> I did some testing with omapdrm on v3.10-rc1. Here are some issues I >> encountered. >> For most of them I don't have any idea where to even start looking for a >> problem, >> s

Re: Multiple issues with omapdrm

2013-06-05 Thread Rob Clark
On Wed, Jun 5, 2013 at 4:59 AM, Tomi Valkeinen wrote: > Hi, > > I did some testing with omapdrm on v3.10-rc1. Here are some issues I > encountered. > For most of them I don't have any idea where to even start looking for a > problem, > so I hope that you may have some ideas. > > > dispc_runtime_