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 18:10:15 +0100 [thread overview]
Message-ID: <56743DF7.2040904@free.fr> (raw)
In-Reply-To: <20151217125505.0abc4b40@recife.lan>
On 17/12/2015 15:55, Mauro Carvalho Chehab wrote:
> Did the driver compile fine?
Once all the modules finish building, I have many *.ko files in v4l.
I copy them to my target's /lib/modules/3.4.39.13/kernel
and run depmod -a
It seems modprobe rc-dvbsky doesn't bring in all the stuff needed
to actually use the device.
I added a few more modules at random:
Module Size Used by
dvb_core 73479 0
v4l2_common 1628 0
videodev 111886 1 v4l2_common
media 9838 1 videodev
rc_dvbsky 815 0
rc_core 15521 1 rc_dvbsky
Probably needs dvb_usb but I don't see it built...
$ grep -rn '\<CONFIG_DVB_USB\>'
linux/drivers/media/usb/dvb-usb/Makefile:3:obj-$(CONFIG_DVB_USB) += dvb-usb.o
v4l/.myconfig:245:CONFIG_DVB_USB := n
v4l/Makefile.media:1010:obj-$(CONFIG_DVB_USB) += dvb-usb.o
v4l/config-compat.h:548:#undef CONFIG_DVB_USB
v4l/.config:183:# CONFIG_DVB_USB is not set
(All these files are generated by the build process.)
Am I doing something wrong?
Regards.
next prev parent reply other threads:[~2015-12-18 17:10 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
2015-12-18 15:13 ` Mason
2015-12-18 17:10 ` Mason [this message]
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=56743DF7.2040904@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).