From: Mason <slash.tmp@free.fr>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media <linux-media@vger.kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: Automatic device driver back-porting with media_build
Date: Fri, 18 Dec 2015 14:40:10 +0100 [thread overview]
Message-ID: <56740CBA.1060903@free.fr> (raw)
In-Reply-To: <56740343.4000904@free.fr>
On 18/12/2015 13:59, Mason wrote: [snip previous work-arounds]
Compilation completes.
make -C /tmp/sandbox/custom-linux-3.4 SUBDIRS=/tmp/sandbox/media_build/v4l modules
make[2]: Entering directory `/tmp/sandbox/custom-linux-3.4'
Building modules, stage 2.
MODPOST 209 modules
WARNING: "of_graph_parse_endpoint" [/tmp/sandbox/media_build/v4l/videodev.ko] undefined!
WARNING: "of_get_next_parent" [/tmp/sandbox/media_build/v4l/videodev.ko] undefined!
WARNING: "nsecs_to_jiffies" [/tmp/sandbox/media_build/v4l/gpio-ir-recv.ko] undefined!
make[2]: Leaving directory `/tmp/sandbox/custom-linux-3.4'
./scripts/rmmod.pl check
found 209 modules
make[1]: Leaving directory `/tmp/sandbox/media_build/v4l'
A few link problems, two from device tree:
of_graph_parse_endpoint() commit fd9fdb78a9bf8
of_get_next_parent() was not exported until commit 6695be6863b75
nsecs_to_jiffies() was not exported until commit d560fed6abe0f
How would you fix those?
I will try building a kernel with CONFIG_OF=n
Regards.
next prev parent reply other threads:[~2015-12-18 13:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 12:13 Automatic device driver back-porting with media_build Mason
2015-12-17 12:55 ` Mauro Carvalho Chehab
2015-12-17 13:52 ` Mason
2015-12-17 14:08 ` Mauro Carvalho Chehab
2015-12-17 14:30 ` Mason
2015-12-17 14:55 ` Mauro Carvalho Chehab
2015-12-17 15:32 ` Mason
2015-12-17 16:09 ` Mauro Carvalho Chehab
2015-12-17 16:48 ` Mason
2015-12-18 10:37 ` Mauro Carvalho Chehab
2015-12-18 11:01 ` Mason
2015-12-17 17:03 ` Mason
2015-12-17 17:17 ` Mason
2015-12-18 10:44 ` Mason
2015-12-18 11:03 ` Mauro Carvalho Chehab
2015-12-18 11:22 ` Mauro Carvalho Chehab
2015-12-18 12:10 ` Mason
2015-12-18 12:59 ` Mason
2015-12-18 13:40 ` Mason [this message]
2015-12-18 15:13 ` Mason
2015-12-18 17:10 ` Mason
2015-12-18 19:42 ` Mason
2015-12-28 10:44 ` Mason
2015-12-28 12:21 ` Mason
2015-12-28 13:02 ` Mauro Carvalho Chehab
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=56740CBA.1060903@free.fr \
--to=slash.tmp@free.fr \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).