public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jordi Molse <jordi.moles@gmail.com>
To: BOUWSMA Barry <freebeer.bouwsma@gmail.com>, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] lifeview pci trio (saa7134) not working	through diseqc anymore
Date: Thu, 11 Dec 2008 14:49:34 +0100	[thread overview]
Message-ID: <49411A6E.2020107@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0812111415560.989@ybpnyubfg.ybpnyqbznva>

En/na BOUWSMA Barry ha escrit:
> On Thu, 11 Dec 2008, Jordi Moles Blanco wrote:
>
>   
>> would you mind telling me what linux system are you working with? i'm 
>> desperate for this to work, i will change to any distro that makes 
>> diseqc work.
>>     
>
> If you are willing to get your hands dirty with kernel
> source and possibly a source-control system, then you
> may be able to get a working system, without the need to
> change distributions -- maybe.
>
> The drawback to the convenience of packaged distributions
> is that they are frozen at a particular point in time,
> which can lock you out of improvements.  That's one of
> the tradeoffs for the convenience about not having to
> worry about these things, which is great, when it works.
>
>
> The linux-dvb source should be self-contained for all
> that you need to get your device working.  (But not
> always...)  So, the easiest way would be for you to
> build the linux-dvb source as modules against your
> present kernel version, whatever that may be.
>
> This will also allow you to go back in time, should
> your device fail to work with the latest source, and
> go back to the point where it did work -- and thereby
> help the developers to get the latest source to work
> again.
>
>
> Anyway, you will need to update/download...
> the sources for the kernel you are using
> the latest linux-dvb source or tarball
>
> The latter can be found at
> http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.bz2
> or, slightly larger,
> http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.gz
>
> This is the latest source; if you look around the
> linuxtv.org site, you will also see a way to download
> the entire history of the source which will help you
> go back in time -- such as I've done today in order
> to try to see if my production 2.6.14-ish machine
> can use the last useable release without problems.
>
>
> Are you comfortable working with the command line?
> I hope so, because that's exclusively what I use.
> When you've downloaded one of the above archives,
> you'll need to extract it into a suitable playground,
> perhaps like
> % cd ~/
> % mkdir src
> % cd src
> % tar z(or j or y)xvf ~/tip.tar.(whatever)
> % cd (whatever-has-been-created)
> % make
>
> This expects you to have downloaded the source for
> your kernel as well -- if you're unsure of how to get
> this, someone familiar with your distribution should
> be able to help, if there isn't anything on the wiki
> to give details of building this.
>
> If you don't have the proper kernel source, your attempt
> to `make' will fail with lots of complaints.
>
> If you do have the source, it's also possible your
> attempted `make' will fail, and probably someone here
> or elsewhere can help fix what's needed (if the source
> is not found where it is expected, for example)
>
>
> If all goes will, you will have the very latest kernel
> modules that support your device, and can try them, to
> see if they work, or if there are still problems.
>
>
> barry bouwsma
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   
hi,

thanks for all the information provided, it's great!!..

i'm not and experienced user, but i get along well with command shell, 
and i'm able to run gcc and install thing form the scratch.

i'll give a try to see if i can compile and use those modules you suggest.

i'll report back with what i've found.

thanks.

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

  reply	other threads:[~2008-12-11 13:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 17:32 [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore Jordi Moles Blanco
2008-12-10 17:49 ` BOUWSMA Barry
2008-12-10 17:58   ` Jordi Moles Blanco
2008-12-10 19:16     ` BOUWSMA Barry
2008-12-10 19:45       ` Jordi Molse
2008-12-11  0:34         ` hermann pitton
2008-12-11  1:02           ` Jordi Molse
2008-12-11  1:25             ` hermann pitton
2008-12-11  8:05               ` Jordi Moles Blanco
2008-12-11 13:44                 ` BOUWSMA Barry
2008-12-11 13:49                   ` Jordi Molse [this message]
2008-12-11 15:04                     ` Jordi Moles Blanco
2008-12-11 15:47                       ` BOUWSMA Barry
2008-12-11 23:21                         ` Jordi Molse
2008-12-12  8:17                           ` BOUWSMA Barry
2008-12-12 13:22                             ` Jordi Moles Blanco
2008-12-13  1:04                               ` hermann pitton
2008-12-13 14:57                                 ` Jordi Moles
2008-12-11 23:03                 ` hermann pitton
2008-12-11 23:26                   ` Jordi Molse
2008-12-12  0:48                     ` hermann pitton
2008-12-12  0:57                       ` Jordi Molse

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=49411A6E.2020107@gmail.com \
    --to=jordi.moles@gmail.com \
    --cc=freebeer.bouwsma@gmail.com \
    --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