From: "Chris R" <chrisrfq@gmail.com>
To: <linux-media@vger.kernel.org>
Subject: FW: Delivery Status Notification (Failure)
Date: Thu, 31 Jul 2014 08:12:26 -0700 [thread overview]
Message-ID: <016d01cfacd1$d752bda0$85f838e0$@gmail.com> (raw)
In-Reply-To: <047d7b16059f97447804ff7e75d5@google.com>
I'm trying to build the V4L-DVB drivers for an embedded system
(OMAP3530/DM3730) that uses the 2.6.37 kernel. I'm using the build
instructions from
http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-D
VB_Device_Drivers and am following the more manually intensive approach
column.
The first make crashes (make tar DIR=/home/me/mykernel) with missing file
errors. It lists about 20 missing files such as include/linux/dma-buf.h and
include/trace/events/v4l2.h. It doesn't look like those files show up in
the kernel source until versions 3.3 and 3.14 respectively. What is the
best approach to resolve the missing file errors for my 2.6.37 kernel and
still have the drivers build and run?
Thanks,
Chris
parent reply other threads:[~2014-07-31 15:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <047d7b16059f97447804ff7e75d5@google.com>]
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='016d01cfacd1$d752bda0$85f838e0$@gmail.com' \
--to=chrisrfq@gmail.com \
--cc=linux-media@vger.kernel.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 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).