All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jelle De Loecker <skerit@kipdola.com>
To: Torgeir Veimo <torgeir@pobox.com>,
	LinuxTV DVB Mailing <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] dvbloopback:
Date: Thu, 06 Nov 2008 10:36:20 +0100	[thread overview]
Message-ID: <4912BA94.8060809@kipdola.com> (raw)
In-Reply-To: <BF8F0D96-3ED8-4D3D-8EF7-899FCAC4514E@pobox.com>

Torgeir Veimo schreef:
> Am trying to use dvbloopback in a setup with two cards, but it seems  
> to fail, I get these errors;
>
> Nov  6 09:30:30.151 frontend: Could not open /dev/dvb/adapter2/ 
> frontend1. Error was: 14
> Open failed
> : Bad address
> Nov  6 09:30:30.151 demux: Could not open /dev/dvb/adapter2/demux1.  
> Error was: 14
> Open failed
> : Bad address
>
> Looking in /var/log/messages, I see the errors;
>
> Nov  6 09:30:30 htpc kernel: Failed to find private data during open
>
> Looking into the dvbloopback kernel module source, it looks like it's  
> not able to retrieve its private member variables;
>
> lbdev = (struct dvblb_devinfo *)dvbdev->priv;
> if (lbdev == NULL) {
>    printk("Failed to find private data during open\n");
>    return -EFAULT;
> }
>
> This would indicate something serious is happening with the kernel  
> module loading? I am using kernel 2.6.26, am not sure if there are any  
> incompatibilities there, as the compile script seems to support up to  
> 2.6.25 only?
>
> Is the dvbloopback module author subscribed to this list?
>   
Hi Torgeir,

First of all, I admire your courage for asking help about dvbloopback on 
this list.
Dvbloopback (and so sasc-ng) is kind of taboo on most MLs.

Unjust, in my opinion.
Sure, the software can be abused for signal "piracy" or whatever you 
want to call it, but in the same way can you abuse Azureus, Gift, ... 
for illegal downloading. In the same way is watching a dvd in America 
some silly patent infringment thing or what-ever.

So, to anyone, I use sasc-ng (and a couple of my friends, too) so that 
we can use 1 smartcard for several tuners.
This is in no way illegal (at least not here in Belgium). However, it 
could be a breach of contract, but that's not any worry of this list. 
(And since my provider supports settop-boxes with multiple tuners I'm 
not worried, too)

And after ALL that, just talking about using and compiling the progrem 
certainly isn't illegal.

I know nobody has said anything about "don't mention sasc-ng on this 
list" yet, I'm just preparing.

Anyway!

Are you using S2API and the S2API patch found on open-sasc-ng's trac?
Because I have the same problem ("error 14", I don't get the "private 
data" bit, though) with kernel 2.6.26 (which came with Debian Lenny) AND 
with my own compiled 2.6.27

In my case it must be an S2API thing, because when I was using 
Multiproto everything worked fine.

Or maybe it's a regression in the latest revision (r53?) I should find 
out ...

Greetings,
Jelle De Loecker

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

  reply	other threads:[~2008-11-06  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 23:48 [linux-dvb] dvbloopback: Torgeir Veimo
2008-11-06  9:36 ` Jelle De Loecker [this message]
2008-11-06 10:38   ` Torgeir Veimo
2008-11-06 10:41   ` Per Heldal
2008-11-06 12:57     ` Torgeir Veimo

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=4912BA94.8060809@kipdola.com \
    --to=skerit@kipdola.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=torgeir@pobox.com \
    /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.