From: Torfinn Ingolfsen <tingox@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: dvb lock patch
Date: Mon, 23 Apr 2012 13:01:07 +0200 [thread overview]
Message-ID: <CAJ_iqta7dEdcvi9P_nTTDxAZi0rKBzz5LUZW_cp444L20k58CQ@mail.gmail.com> (raw)
In-Reply-To: <CAL9G6WVeXD99FOVNLJ+CVjPEiKrH9dNijM6Rb-G2uz8v_v_j-Q@mail.gmail.com>
On Sat, Apr 21, 2012 at 2:18 PM, Josu Lazkano <josu.lazkano@gmail.com> wrote:
>
> Thanks Torfinn!
>
> I get it working with modules compilation, that great!
Good to hear that you got it working.
>
> apt-get install linux-source-3.2
> cd /usr/src/
> tar -xjvf linux-source-3.2.tar.bz2
> cd linux-source-3.2/
> wget http://kipdola.be/subdomain/linux-2.6.38-dvb-mutex.patch
> patch -p1 linux-2.6.38-dvb-mutex.patch (I must do it manually, maybe
> for the kernel version)
> cp /boot/config-3.2.0-2-686-pae .config
> cp ../linux-headers-3.2.0-2-686-pae/Module.symvers .
> make oldconfig
> make prepare
> make scripts
> make modules SUBDIRS=drivers/media/dvb/
> cp drivers/media/dvb/dvb-core/dvb-core.ko
> /lib/modules/3.2.0-2-686-pae/kernel/drivers/media/dvb/dvb-core/
> (reboot)
>
> I am not software developer and I have no idea what means "race
> conditions", is this sasc-ng or linux driver "problem"?
Sorry, I'm also not a developer, so I can't tell. :)
As long as the driver works, I'm happy.
--
Regards,
Torfinn Ingolfsen
prev parent reply other threads:[~2012-04-23 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 20:49 dvb lock patch Josu Lazkano
[not found] ` <4f6ca10f.e503b40a.4448.ffffc0feSMTPIN_ADDED@mx.google.com>
2012-03-23 16:15 ` Josu Lazkano
2012-03-24 14:32 ` Mauro Carvalho Chehab
2012-04-17 13:30 ` Josu Lazkano
2012-04-18 18:58 ` Ezequiel García
2012-04-18 19:19 ` Mauro Carvalho Chehab
2012-04-18 20:13 ` Josu Lazkano
2012-04-19 22:39 ` Torfinn Ingolfsen
2012-04-21 12:18 ` Josu Lazkano
2012-04-23 11:01 ` Torfinn Ingolfsen [this message]
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=CAJ_iqta7dEdcvi9P_nTTDxAZi0rKBzz5LUZW_cp444L20k58CQ@mail.gmail.com \
--to=tingox@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 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.