From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Chris Tapp <opensource@keylevel.com>,
Yocto Project <yocto@yoctoproject.org>
Subject: Re: Kernel driver for Turbosight TBS6285 DVB card
Date: Tue, 19 Aug 2014 22:08:06 -0400 [thread overview]
Message-ID: <53F40306.2080500@windriver.com> (raw)
In-Reply-To: <4EAABF91-29AE-4B7D-9FEE-07C87F37197D@keylevel.com>
On 2014-08-19, 5:26 PM, Chris Tapp wrote:
> I need to include the kernel driver for the Turbosight TBS6285 DVB card in an image.
>
> The official bundle at http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v140707.zip includes the drivers and a load of other "stuff" (e.g. a full V4L build).
>
> LinuxTV.org have the drivers extracted into a .tar.bz2 at (e.g.) http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2, so I plan to use this as the download source.
>
> So far I have a recipe which downloads from this URL and extracts the files into the work area and ${WORKAREA}/drivers/media includes a Makefile and Kconfig.
>
> I've looked at the Yocto documentation, but this doesn't seem to be a good match for the "Out of tree" kernel module case.
Hmm. At a glance, I'd say that it does sound like a typical out of
tree module build.
Did you try adopting the meta-skeleton hello-mod recipe and point it
at that source directory ?
Bruce
>
> How should I proceed from here? Is there another driver I can use as a starting point?
>
> --
>
> Chris Tapp
> opensource@keylevel.com
> www.keylevel.com
>
>
>
>
next prev parent reply other threads:[~2014-08-20 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 21:26 Kernel driver for Turbosight TBS6285 DVB card Chris Tapp
2014-08-20 2:08 ` Bruce Ashfield [this message]
2014-08-20 20:11 ` Chris Tapp
2014-08-21 4:08 ` Bruce Ashfield
2014-08-21 8:17 ` Chris Tapp
2014-08-21 18:28 ` Bruce Ashfield
2014-08-21 19:11 ` Chris Tapp
2014-08-21 19:30 ` Bruce Ashfield
2014-08-22 7:37 ` Chris Tapp
2014-08-22 13:29 ` Bruce Ashfield
2014-08-22 19:57 ` Chris Tapp
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=53F40306.2080500@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=opensource@keylevel.com \
--cc=yocto@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.