All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Mauro Carvalho Chehab <maurochehab@gmail.com>
Cc: "Ole W. Saastad" <olewsaa@online.no>,
	Douglas Schilling Landgraf <dougsland@gmail.com>,
	linux-media@vger.kernel.org
Subject: Re: Trouble building v4l-dvb
Date: Sun, 26 Sep 2010 18:18:47 +0200	[thread overview]
Message-ID: <4C9F7267.7000707@hoogenraad.net> (raw)
In-Reply-To: <4C93800B.8070902@gmail.com>

On
Linux 2.6.28-19-generic
the problem is tackled already:
DVB_FIREDTV_IEEE1394: Requires at least kernel 2.6.30

On newer linux versions (I have tried Linux 2.6.32-24-generic) the 
problem is NOT that the modules dma is not present, it is just that the 
required header files are not present in
/usr/include

Another location mighte have been:
ls -l /usr/src/linux-headers-2.6.28-19-generic/include/config/ieee1394

but that only contains:
-rw-r--r-- 1 root root    0 2010-09-16 18:25 dv1394.h
drwxr-xr-x 3 root root 4096 2010-06-15 20:12 eth1394
-rw-r--r-- 1 root root    0 2010-09-16 18:25 eth1394.h
-rw-r--r-- 1 root root    0 2010-09-16 18:25 ohci1394.h
-rw-r--r-- 1 root root    0 2010-09-16 18:25 pcilynx.h
-rw-r--r-- 1 root root    0 2010-09-16 18:25 rawio.h
-rw-r--r-- 1 root root    0 2010-09-16 18:25 sbp2.h
-rw-r--r-- 1 root root    0 2010-09-16 18:25 video1394.h

Can you indicate where following files  should be located ?
dma.h
csr1212.h
highlevel.h

In that case checking if the dma.h file is present might be the best way 
forward.

I'll also file an ubuntu bug once I know what is missing where.
I could not find an entry in launchpad on this issue yet.

Mauro Carvalho Chehab wrote:
> Em 17-09-2010 08:08, Jan Hoogenraad escreveu:
>> Thanks !
>>
>> Indeed, the hack so that
>> make allyesmod
>> not select firedtv would be very helpful.
>>
>> that way, it is also clear that firedtv will not work on debian-like distros.
>>
>> Is there a way I cen help with that ?
>> I have no experience with Kconfig, so it would be a learning experience for me.
>
> You don't need to look at Kconfig. there are some scripts under v4l/scripts
> that will deal with Kconfig dependencies. They are meant to identify kernel versions
> and features. Those scripts are, mainly:
>
> 	v4l/scripts/make_config_compat.pl - Checks for "backported" features, enabling workarounds at v4l/compat.h
> 	v4l/scripts/make_kconfig.pl - Generates a .config file that will compile with an older kernel
> 	v4l/scripts/make_makefile.pl - Generates a Makefile that will build/install/remove the kernel modules
>
> Basically, you need to add some intelligence to one of the above scripts (likely make_kconfig)
> to identify that the kernel has broken firewire headers, and disable its compilation, printing
> a warning message to the user.
>
> You'll find a logic at make_makefile.pl to detect an Ubuntu broken kernel that stores the in-kernel
> drivers at the wrong install place. I'm not sure if all Ubuntu kernels/versions do the same
> thing, nor if this is broken for all distro-variants.
>
> Perhaps you may use this logic at make_kconfig.pl. The logic assumes that broken distros
> are the ones that store V4L/DVB files at /lib/modules/\$(KERNELRELEASE)/ubuntu/media.
> This is probably not true for all broken distros (as Ubuntu clones - and maybe Debian - could
> have the same problem, but storing the media files on a different place), so you may
> need to generalize that logic, in order to cover any other distros that don't compile
> firewire.
>
> While you're there, the better is to also disable CONFIG_ALSA on Ubuntu, as the drivers
> won't work anyway.
>
> As we don't want to have complains from users about "why driver foo is not compiling for me",
> IMO, it should be printing a warning message saying that compilation of ALSA/FIREWIRE drivers with
> that specific kernel version is not possible, due to the back packaging of kernel headers,
> recommending to the user to get a vanilla upstream kernel, if he needs one of the disabled
> drivers.
>
> Cheers,
> Mauro
>


-- 
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht

  parent reply	other threads:[~2010-09-26 16:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 19:38 Trouble building v4l-dvb Ole W. Saastad
2010-09-16 17:07 ` Jan Hoogenraad
2010-09-17  9:35   ` Jan Hoogenraad
2010-09-17 10:50     ` Mauro Carvalho Chehab
2010-09-17 11:08       ` Jan Hoogenraad
2010-09-17 14:49         ` Mauro Carvalho Chehab
2010-09-17 15:00           ` Devin Heitmueller
2010-09-17 15:08             ` Mauro Carvalho Chehab
2010-09-17 15:27           ` Jan Hoogenraad
2010-09-26 16:18           ` Jan Hoogenraad [this message]
2010-09-27  4:08             ` Mauro Carvalho Chehab
2010-09-27 18:41               ` updated make_kconfig.pl for Ubuntu Jan Hoogenraad
2010-09-27 19:12                 ` Mauro Carvalho Chehab
2010-09-27 20:45                   ` Jan Hoogenraad
2010-09-27 22:43                     ` Mauro Carvalho Chehab
2010-09-28 17:48                       ` Jan Hoogenraad
2010-09-28 18:21                         ` Mauro Carvalho Chehab
2010-09-28 19:58                           ` Jan Hoogenraad
2010-09-29 21:49                           ` patches for the Realtek rtl2831 Jan Hoogenraad
2010-09-17 17:33     ` Trouble building v4l-dvb Ole W. Saastad
2010-09-17 17:58       ` rtl2832 chip driver Jan Hoogenraad

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=4C9F7267.7000707@hoogenraad.net \
    --to=jan-conceptronic@hoogenraad.net \
    --cc=dougsland@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=maurochehab@gmail.com \
    --cc=olewsaa@online.no \
    /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.