From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>,
"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 12:08:52 -0300 [thread overview]
Message-ID: <4C938484.3050606@gmail.com> (raw)
In-Reply-To: <AANLkTi=bs0qReM=+h-8eH=rx_AJkyUOWnZy4tarMbNbe@mail.gmail.com>
Em 17-09-2010 12:00, Devin Heitmueller escreveu:
> On Fri, Sep 17, 2010 at 10:49 AM, Mauro Carvalho Chehab
> <maurochehab@gmail.com> wrote:
>> While you're there, the better is to also disable CONFIG_ALSA on Ubuntu, as the drivers
>> won't work anyway.
>
> Note: while building ALSA modules did fail in some versions for
> Ubuntu, it has been over a years since I've seen that problem.
> Blindly disabling ALSA for all Ubuntu users would be a huge regression
> for users.
Yeah, blindly disabling it, if some versions work is not the right thing to do.
I'm not an Ubuntu user, so, I'm not sure when it was fixed. Still, from time to time,
people complain to me about this problem with some Ubuntu versions. The last complains I
heard were with some netbook versions of Ubuntu-based distros.
If there's a way to check what versions have broken alsa headers, then the checker should
just disable to the broken ones. Otherwise, the better way seems to just print a warning
message that ALSA might not be working, but keep it enabled.
Cheers,
Mauro
next prev parent reply other threads:[~2010-09-17 15: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
2010-09-17 14:49 ` Mauro Carvalho Chehab
2010-09-17 15:00 ` Devin Heitmueller
2010-09-17 15:08 ` Mauro Carvalho Chehab [this message]
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=4C938484.3050606@gmail.com \
--to=maurochehab@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=dougsland@gmail.com \
--cc=jan-conceptronic@hoogenraad.net \
--cc=linux-media@vger.kernel.org \
--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.