From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: linux-omap@vger.kernel.org
Cc: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Tony Lindgren <tony@atomide.com>,
Ameya Palande <ameya.palande@nokia.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Tomi Valkeinen <tomi.valkeinen@nokia.com>,
Shivananda Hebbar <x0hebbar@ti.com>,
Andy Shevchenko <ext-andriy.shevchenko@nokia.com>,
Ernesto Ramos <ernesto@ti.com>,
Fernando Guzman Lugo <x0095840@ti.com>,
Ramesh Gupta G <grgupta@ti.com>,
Mika Kukkonen <mika.kukkonen@nokia.com>,
Hari Kanigeri <h-kanigeri2@ti.com>, Nishanth Menon <nm@ti.com>,
C A Subramaniam <subramaniam.ca@ti.com>,
Rebecca Schultz Zavin <rebecca@android.com>,
Phil Carmody <ext-phil.2.carmody@nokia.com>,
Omar Ramirez Luna <omar.ramirez@ti.com>
Subject: [dspbridge] news: omap mailbox implementation
Date: Tue, 23 Mar 2010 12:08:22 -0600 [thread overview]
Message-ID: <1269367702-2589-1-git-send-email-omar.ramirez@ti.com> (raw)
Hi All,
When updating the custom dspbridge mailbox functions with the ones
avaliable through omap mailbox (by pulling latest dspbridge),
PLEASE remember to enable omap mailbox through menuconfig:
make menuconfig
System Type --->
TI OMAP Implementations --->
<*> Mailbox framework support
otherwise, compilation will break like:
Building modules, stage 2.
MODPOST 7 modules
ERROR: "omap_mbox_msg_send" [drivers/dsp/bridge/bridgedriver.ko] undefined!
ERROR: "omap_mbox_put" [drivers/dsp/bridge/bridgedriver.ko] undefined!
ERROR: "omap_mbox_get" [drivers/dsp/bridge/bridgedriver.ko] undefined!
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
make: *** [modules] Error 2
Regards,
Omar
next reply other threads:[~2010-03-23 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 18:08 Omar Ramirez Luna [this message]
2010-03-23 17:54 ` [dspbridge] news: omap mailbox implementation Ameya Palande
2010-03-23 18:29 ` Omar Ramirez Luna
2010-03-23 18:31 ` Ameya Palande
2010-03-23 18:42 ` Omar Ramirez Luna
2010-03-23 18:33 ` Omar Ramirez Luna
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=1269367702-2589-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=ernesto@ti.com \
--cc=ext-andriy.shevchenko@nokia.com \
--cc=ext-phil.2.carmody@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=grgupta@ti.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mika.kukkonen@nokia.com \
--cc=nm@ti.com \
--cc=rebecca@android.com \
--cc=subramaniam.ca@ti.com \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.com \
--cc=x0095840@ti.com \
--cc=x0hebbar@ti.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