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: Fri, 17 Sep 2010 13:08:00 +0200	[thread overview]
Message-ID: <4C934C10.2060801@hoogenraad.net> (raw)
In-Reply-To: <4C934806.7050503@gmail.com>

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.


Mauro Carvalho Chehab wrote:
> Em 17-09-2010 06:35, Jan Hoogenraad escreveu:
>> I see that the build now succeeded.
>>
>> Ole: this is something that should have been fixed a long time ago, but isn't.
>> make allyesmod
>> should set only those divers that do actually compile.
>> Unfortunately, the FIREDTV driver has bugs for as long as I remember.
> 
> The problem are not related to bugs at firedtv driver, but, instead, due to the fact
> that the provided firewire drivers and fw-core don't match the drivers that are shipped
> with the distro kernel. In order words, at Ubuntu (and some other deb-based distros),
> they're shipping the wrong include files at /lib/modules/`uname -r`/build/. So, there's
> no way to build and run any module based on that wrong broken headers.
> 
> Up to a certain amount, the same happens with -alsa files on Ubuntu: although they
> will compile [1], as the provided headers at /lib/modules/`uname -r`/build/ are from a different
> version than the alsa modules provided with Ubuntu, the drivers that depend on -alsa will 
> generally compile, but they generally won't load (and, if they load, they'll can cause
> an OOPS and some other random troubles), as the symbol dependency will not match.
> 
> While a hack might be added at v4l-dvb -hg tree to make firedtv to compile against a broken
> header, the firedtv driver will not work anyway.
> 
> The only real solution for it is to fix this issue at the distro.
> 
> Cheers,
> Mauro
> 
> [1] The v4l-dvb is smart enough to adapt to -alsa API changes that are backported into
> an older kernel, since it checks for the API symbols that changed, instead of just looking
> for the kernel version. This works fine with all distros (like Fedora, RHEL, SUSE, OpenSUSE,
> Mandriva, ...) where the include files for alsa are at the right place:
> /lib/modules/`uname -r`/build/).
> 


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

  reply	other threads:[~2010-09-17 11:08 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 [this message]
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
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=4C934C10.2060801@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.