public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Wang Diancheng <dcwang@redflag-linux.com>
To: "Daniel D韆z" <mrchapp@gmail.com>
Cc: linux-omap@vger.kernel.org,
	Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: omap24xxvout alloc DMA page failed when using openMAX
Date: Thu, 19 Feb 2009 14:37:57 +0800	[thread overview]
Message-ID: <87ab8j0w56.fsf@redflag-linux.com> (raw)
In-Reply-To: <e7df06480902161406s1a403c31gcf0169b60da330f9@mail.gmail.com> ("Daniel D韆z"'s message of "Mon, 16 Feb 2009 16:06:31 -0600")


Hi Daniel and Felipe,
Thank you for your reply,
has the patch fixing this issue merged to omapzoom.org?
I try again with today's kernel and same command, but failed again.

Best Regards,

Diancheng

>>>>> Daniel D韆z <mrchapp@gmail.com> writes:

    > Hello!  If you don't mind the top-posting, please see the quoted
    > chain of emails below. Summary is that some changes need to make
    > it to the omapzoom.org kernel for Zoom2.

    > Greetings!

    > Daniel D韆z ddiaz@ti.com



    > ________________________________________ From: Jimenez Villareal,
    > Omar Sent: Monday, February 16, 2009 11:46 AM To: Mande, Nikhil;
    > Turquette, Mike; Diaz, Daniel; Castaneda Gonzalez, Axel; Munoz,
    > Jose Luis Diaz Subject: RE: omap24xxvout alloc DMA page failed
    > when using openMAX

    > This bootargs are needed since 23.12 release because of memory
    > allocation at boot time but in omap zoom this changes are not
    > merged, first need to be done changes in omap zoom kernel and then
    > when merged 720p resolution support this bootargs will be needed.

    > Regards,

    > Omar Jimenez ________________________________________ De: Mande,
    > Nikhil Enviado el: lunes, 16 de febrero de 2009 10:42 a.m.  Para:
    > Turquette, Mike; Jimenez Villareal, Omar; Diaz, Daniel; Castaneda
    > Gonzalez, Axel; Munoz, Jose Luis Diaz Asunto: RE: omap24xxvout
    > alloc DMA page failed when using openMAX

    > They are related. Both kernel changes and those bootargs are
    > required.

    > -----Original Message----- From: Turquette, Mike Sent: Monday,
    > February 16, 2009 10:32 AM To: Jimenez Villareal, Omar; Mande,
    > Nikhil; Diaz, Daniel; Castaneda Gonzalez, Axel; Munoz, Jose Luis
    > Diaz Subject: RE: omap24xxvout alloc DMA page failed when using
    > openMAX

    > This is probably unrelated, but I saw in another thread by Lajos
    > that it is necessary to set omap24xxfb:rotation=0 in the bootargs
    > to avoid some errors when specifically using the Zoom2 board.

    > Obviously a rotation of 0 is the default, but Lajos said it had to
    > be specifically set to avoid some sort of issue.  Maybe related,
    > maybe not.

    > Mike

    >> -----Original Message----- From: Jimenez Villareal, Omar Sent:
    >> Monday, February 16, 2009 9:57 AM To: Mande, Nikhil; Diaz,
    >> Daniel; Turquette, Mike; Castaneda Gonzalez, Axel; Munoz, Jose
    >> Luis Diaz Subject: RE: omap24xxvout alloc DMA page failed when
    >> using openMAX
    >> 
    >> Hi all,
    >> 
    >> You are rigth, we are working to send the patches to sync up omap
    >> zoom with 23x, with these changes this issue is gone.
    >> 
    >> We will keep you updated when this get ready,
    >> 
    >> Thanks,
    >> 
    >> Omar Jimenez ________________________________________ De: Mande,
    >> Nikhil Enviado el: lunes, 16 de febrero de 2009 09:36 a.m.  Para:
    >> Diaz, Daniel; Turquette, Mike CC: Jimenez Villareal, Omar Asunto:
    >> RE: omap24xxvout alloc DMA page failed when using openMAX
    >> 
    >> Some changes in L23.x kernel are not merged into OMAPZoom kernel
    >> yet.  Now we reserve memory required by display driver at boot
    >> time, so we don't run into this issue.
    >> 
    >> Omar, I believe we are merging these changes for L23.14, right?
    >> 
    >> Thanks, Nikhil
    >> 
    >> -----Original Message----- From: Diaz, Daniel Sent: Monday,
    >> February 16, 2009 9:22 AM To: Mande, Nikhil; Turquette, Mike
    >> Subject: FW: omap24xxvout alloc DMA page failed when using
    >> openMAX
    >> 
    >> Hello!
    >> 
    >> Do you guys have any information on this? This appeared on the
    >> linux-omap mailing list.
    >> 
    >> Greetings!
    >> 
    >> Daniel D韆z ddiaz@ti.com
    >> 
    >> 
    >> 
    >> ________________________________________ From: Felipe Contreras
    >> [felipe.contreras@gmail.com] Sent: Monday, February 16, 2009 4:03
    >> AM To: Wang Diancheng Cc: linux-omap@vger.kernel.org; Diaz,
    >> Daniel Subject: Re: omap24xxvout alloc DMA page failed when using
    >> openMAX
    >> 
    >> On Mon, Feb 16, 2009 at 11:14 AM, Wang Diancheng
    >> <dcwang@redflag-linux.com> wrote:
    >> > Hey, I posted this independently, and someone suggested I
    >> should send > it to this mailing list.  > I don't read the list,
    >> so I'm not sure if this is useful or on-topic > or what.  My
    >> apologies in advance if this is noise.  > omap24xxvout alloc DMA
    >> page failed when I use openMAX on ZOOM2 board, > following is my
    >> test command and output:
    >> >
    >> > gst-launch videotestsrc ! goosink_pp > Setting pipeline to
    >> PAUSED ...  > Pipeline is PREROLLING ...  > ^CVIDIOC_STREAMON:
    >> Cannot allocate memory > Caught interrupt -- handling interrupt.
    >> 
    >> I'm cc'ing Daniel D韆z, who should know about gst-goo.
    >> 
    >> Also, you can try gst-omapfb instead:
    >> http://github.com/felipec/gst-omapfb
    >> 
    >> -- Felipe Contreras

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-02-19  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  9:14 omap24xxvout alloc DMA page failed when using openMAX Wang Diancheng
2009-02-16 10:03 ` Felipe Contreras
2009-02-16 22:06   ` Daniel Díaz
2009-02-19  6:37     ` Wang Diancheng [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ab8j0w56.fsf@redflag-linux.com \
    --to=dcwang@redflag-linux.com \
    --cc=felipe.contreras@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mrchapp@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox