public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: insomniac <insomniac@slackware.it>
To: linux-dvb@linuxtv.org
Cc: Antti Palosaari <crope@iki.fi>
Subject: Re: [linux-dvb] New unsupported device
Date: Mon, 17 Mar 2008 10:41:47 +0100	[thread overview]
Message-ID: <20080317104147.1ade57fe@slackware.it> (raw)
In-Reply-To: <47DDD817.9020605@iki.fi>

On Mon, 17 Mar 2008 04:31:51 +0200
Antti Palosaari <crope@iki.fi> wrote:

> yes, thats correct. I made simple patch, you can test if it does 
> something nasty. You can also look dib0700_devices.c file and try
> some changes. Patch can be applied towards current v4l-dvb-master.

Patched and recompiled the modules. Now plugging in the usb stick
triggers the loading of the related kernel modules.
The one error I get in dmesg is 

dvb_core: exports duplicate symbol dvb_unregister_adapter (owned by
kernel)

so I have removed all the DVB support from kernel, and left only
CONFIG_DVB_CORE=y, and now kernel is compiling. What to say.. whatever
will happen, all this showed again the power of the open source,
I'm moved :-)

-- 
Andrea Barberio

a.barberio@oltrelinux.com - Linux&C.
andrea.barberio@slackware.it - Slackware Linux Project Italia
GPG key on http://insomniac.slackware.it/gpgkey.asc
2818 A961 D6D8 1A8C 6E84  6181 5FA6 03B2 E68A 0B7D
SIP: 5327786, Phone: 06 916503784

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-03-17  9:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 17:26 [linux-dvb] New unsupported device insomniac
2008-03-16 20:42 ` Jarryd Beck
2008-03-17  0:19   ` insomniac
2008-03-17  1:09     ` Antti Palosaari
2008-03-17  1:50       ` insomniac
2008-03-17  1:57         ` Antti Palosaari
2008-03-17  1:58           ` insomniac
2008-03-17  2:31             ` Antti Palosaari
2008-03-17  9:41               ` insomniac [this message]
2008-03-17 10:48                 ` insomniac
2008-03-17 11:09                   ` Jarryd Beck
2008-03-17 12:08                     ` Antti Palosaari
2008-03-17 12:35                       ` Albert Comerma
2008-03-17 12:42                         ` Albert Comerma
2008-03-17 17:28                           ` insomniac
2008-03-17 18:15                           ` insomniac
2008-03-17 20:33                       ` insomniac
2008-03-17 21:12                         ` Albert Comerma
2008-03-17 21:18                           ` insomniac
     [not found]                           ` <20080317221546.6a4dd75e@slackware.it>
     [not found]                             ` <ea4209750803171420t55f203eev3ba21b70d93bc39f@mail.gmail.com>
2008-03-17 21:24                               ` insomniac
     [not found]                                 ` <ea4209750803171427x45224559l4b60f804401e6c87@mail.gmail.com>
     [not found]                                   ` <ea4209750803171438x34e25fb5o6bbfa91b38defa2e@mail.gmail.com>
2008-03-17 22:46                                     ` insomniac
2008-03-17 22:59                                       ` Albert Comerma
2008-03-17 23:21                                         ` insomniac
2008-03-18 10:20                                           ` Albert Comerma

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=20080317104147.1ade57fe@slackware.it \
    --to=insomniac@slackware.it \
    --cc=crope@iki.fi \
    --cc=linux-dvb@linuxtv.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