From: Denys Dmytriyenko <denys@ti.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: pvrsrvkm failing on kernel 3.14.26 for am3359
Date: Fri, 9 Jan 2015 10:41:06 -0500 [thread overview]
Message-ID: <20150109154106.GI4759@edge> (raw)
In-Reply-To: <CAMCfZKH_-v_S=mLiNLQVRZ_YmUYZgz1a6q8h_ZX5VRqfwjiESQ@mail.gmail.com>
Diego,
The fix finally got merged to the kernel yesterday and will be picked up by
the recipe update I posted last night.
--
Denys
On Fri, Jan 09, 2015 at 08:41:19AM -0200, Diego Sueiro wrote:
> Folks,
>
> I have recently updated my meta-ti daisy branch and noticed that
> omap3-sgx-modules are not being loaded.
>
> Here is the log for 3.14.26 kernel (from meta-ti commit
> 1d46274416c3b50808590963bdb6c157d9d7c745):
>
> pvrsrvkm: Unknown symbol v7_dma_map_area (err 0)
> pvrsrvkm: Unknown symbol v7_dma_flush_range (err 0)
> insmod: ERROR: could not insert module
> /lib/modules/3.14.26/kernel/drivers/gpu/pvr/pvrsrvkm.ko: Unknown symbol in
> module
> Could not find pvrsrvkm driver
>
>
> The 3.14.25 kernel version (from meta-ti commit
> 31348244882a8defb640af75119ba275d9915f09) is OK.
>
> I'm using the default kernel configuration.
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2015-01-09 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 10:41 pvrsrvkm failing on kernel 3.14.26 for am3359 Diego Sueiro
2015-01-09 13:33 ` Carlos Hernandez
2015-01-09 15:41 ` Denys Dmytriyenko [this message]
2015-01-09 18:53 ` Diego Sueiro
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=20150109154106.GI4759@edge \
--to=denys@ti.com \
--cc=diego.sueiro@gmail.com \
--cc=meta-ti@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.