just some random thoughts on our release model, etc.. I've been
meaning to write up for a while but haven't had time
There has been some feedback, for example on #pandaboard, that the
monthly release cycle is confusing and detrimental for folks looking
for something working and stable, and not ne
On Fri, Apr 6, 2012 at 4:05 AM, Wookey wrote:
> +++ Clark, Rob [2012-04-05 21:10 -0500]:
>> just some random thoughts on our release model, etc.. I've been
>> meaning to write up for a while but haven't had time
>>
>> There has been some feedback, for exampl
On Fri, Apr 6, 2012 at 2:59 PM, Nicolas Pitre wrote:
> On Fri, 6 Apr 2012, Ricardo Salveti wrote:
>
>> On Fri, Apr 6, 2012 at 6:05 AM, Wookey wrote:
>> > The fundamental question really is 'are we a distro or not'? If linaro
>> > is not a distro then no-one should be expecting stable releases - w
There is an omap_drv.so which should be the xorg driver to load.. it
will attempt to load (if present) omap_pvr_drv.so as a submodule for
EXA accel. I'm not entirely sure why it is named pvr_drv.so in your
filesystem, but from list of symbols it seems to match what I would
expect to be omap_pvr_dr
usr/lib/debug/usr/lib/xorg/modules/drivers/omap_pvr_drv.so
> ./usr/lib/xorg/modules/drivers/omap_pvr_drv.so
>
> which is the same as "*drv*" gives.
>
> - Martin
>
>
>
> On 04/16/12 16:42, Clark, Rob wrote:
>>
>> There is an omap_drv.so which s
t;>> the only one in that directory when extracting that tarball. Actually there
>>> is no file at all named omap_drv.so:
>>>
>>> $ find . -name "omap_drv.so"
>>>
>>> return nothing, while just omap gives
>>>
>>> $
On Thu, May 3, 2012 at 7:29 AM, Martin Ertsås wrote:
> Hi.
>
> I have gotten a lot of help from you guys getting the PowerVR drivers up
> and running with the 3.3 kernel on the Pandaboard ES. Problem now is
> that all I tested then, was that X was running. After some more work, we
> tried out EGL,
Could you try also adding 'nohz=0' to bootargs to disable tickless
scheduler? Depending on what is the default in current linaro kernel,
this might help..
BR,
-R
On Mon, Aug 29, 2011 at 1:57 PM, Tom Gall wrote:
>
> An update on my oprofile adventures with panda.
>
> I did add the kernel param a
On Wed, Aug 31, 2011 at 7:19 AM, Dechesne, Nicolas wrote:
>
>
> On Wed, Aug 31, 2011 at 1:08 PM, Ilias Biris wrote:
>>
>> Also note the development on MM: Jesse is preparing a GIT tree to
>> contain the patches available, including components from the
>> Video-Multimedia side (eg OMAP DRM driver
in case any of the multimedia/middleware folks interested in camerabin2
didn't notice this email from gst-devel list:
-- Forwarded message --
From: Thiago Sousa Santos
Date: Fri, Dec 3, 2010 at 11:30 PM
Subject: Re: [gst-devel] Camerabin2 Prototype and IRC Meeting
To: Discussion o
t;
> Thanks
> Sachin
>
> --
> *From:* linaro-dev-boun...@lists.linaro.org [mailto:
> linaro-dev-boun...@lists.linaro.org] *On Behalf Of *Clark, Rob
> *Sent:* Sunday, December 05, 2010 11:00 PM
> *To:* linaro-dev@lists.linaro.org
> *Subject:* Fwd: [
On Fri, Feb 11, 2011 at 7:47 AM, Alexandros Frantzis
wrote:
>
> * First version of Unified Memory Management position:
>
> https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Projects/UnifiedMemoryManagement
btw, the access control aspect of this sort of reminds me of the DRM
driver inf
On Wed, Feb 9, 2011 at 10:31 AM, Arnd Bergmann wrote:
> On Wednesday 09 February 2011, Sascha Hauer wrote:
>
>> The driver patch itself is Cced to linux-fbdev, only the introductory
>> mail is not.
>
> Ok, I see.
>
>> > Did you consider making the driver a KMS driver instead of
>> > a frame buffer
se
>
> On Wed, Feb 16, 2011 at 4:22 AM, Arnd Bergmann wrote:
>>
>> On Tuesday 15 February 2011, Clark, Rob wrote:
>> > I'd been experimenting a bit on the side w/ the DRM driver framework (
>> >
>> > http://gitorious.com/~robclark/pandaboard/robclarks-k
> can serve as what we needed.
>
> Regards,
> Jammy
>
> On Thu, Feb 17, 2011 at 9:08 AM, Clark, Rob wrote:
>>
>> I'm still in the learning-as-I-go phase here, so definitely not ready
>> to propose a solution, but it does seem to me like there is room for
&g
I'm all for a more modular drm, although I think the framework of
CRTCs, encoders, and connectors is a nice fit, at least for our hw.
It would be nice to have a better way to expose overlays. And I'm
still thinking about how/if GEM fits in with our various video and
2/3d accelerators.
BR,
-R
On
n implement one, it would be beneficial for all ARM platforms. By
> the way, does X driver of TI support XRandR1.2+?
>
> Regards,
> Jammy
>
> On Thu, Feb 17, 2011 at 11:25 PM, Clark, Rob wrote:
>>
>> Hmm, I was thinking more on the xf86 side of things.. ie.
On Fri, Feb 18, 2011 at 10:39 AM, Robert Fekete
wrote:
> Hi,
>
> In order to expand this knowledge outside of Linaro I took the Liberty of
> inviting both linux-me...@vger.kernel.org and
> gstreamer-de...@lists.freedesktop.org. For any newcomer I really recommend
> to do some catch-up reading on
>
On Thu, Feb 24, 2011 at 2:19 PM, Edward Hervey wrote:
>
> What *needs* to be solved is an API for data allocation/passing at the
> kernel level which v4l2,omx,X,GL,vdpau,vaapi,... can use and that
> userspace (like GStreamer) can pass around, monitor and know about.
yes yes yes yes!!
vaapi/vdpa
On Thu, Feb 24, 2011 at 7:17 AM, Hans Verkuil wrote:
> There are two parts to this: first of all you need a way to allocate large
> buffers. The CMA patch series is available (but not yet merged) that does
> this.
> I'm not sure of the latest status of this series.
>
> The other part is that ever
On Thu, Feb 24, 2011 at 7:10 AM, Laurent Pinchart
wrote:
> On Thursday 24 February 2011 14:04:19 Hans Verkuil wrote:
>> On Thursday, February 24, 2011 13:29:56 Linus Walleij wrote:
>> > 2011/2/23 Sachin Gupta :
>> > > The imaging coprocessor in today's platforms have a general purpose DSP
>> > > a
Then this sounds to me a bit like like GEM.. (or maybe I should say DRM and
either TTM/GEM below)? If you can pass buffers back and forth between
kernel and various processes by integer id, and then optionally
read/write/mmap thru some ioctls if needed.. then the buffer sharing problem
is solved.
On Wed, Mar 23, 2011 at 9:09 AM, Robert Fekete wrote:
> On 21 March 2011 21:08, Alex Deucher wrote:
> > On Mon, Mar 21, 2011 at 3:50 PM, Geert Uytterhoeven
> > wrote:
> >> On Mon, Mar 21, 2011 at 20:25, Jesse Barnes
> wrote:
> >>> On Mon, 21 Mar 2011 19:19:43 +
> >>> timofonic timofonic wr
On Wed, Mar 16, 2011 at 3:14 AM, Kyungmin Park wrote:
>
> Rough schedules.
>
> 1. Warsaw meetings (3/16~3/18): mostly v4l2 person and some SoC vendors
> Make a consensence at media developers. and share the information.
> Please note that it's v4l2 brainstorming meeting. so memory
> management i
hmm,
https://review.source.android.com/#change,22239
>From a quick look, it appears to be doing a similar thing as GEM..
although as a stand-alone driver rather than coupled with display
driver (drm).
BR,
-R
___
linaro-dev mailing list
linaro-dev@lis
e, Apr 12, 2011 at 11:12 AM, Clark, Rob wrote:
>> hmm,
>>
>> https://review.source.android.com/#change,22239
>>
>> From a quick look, it appears to be doing a similar thing as GEM..
>> although as a stand-alone driver rather than co
26 matches
Mail list logo
