From: vic <vic@zini-associati.it>
To: linux-media@vger.kernel.org
Subject: Re: lifeview NOT LV3H not working
Date: Wed, 04 Mar 2009 09:34:31 +0100 [thread overview]
Message-ID: <49AE3D17.20401@zini-associati.it> (raw)
In-Reply-To: <49AC472B.90202@zini-associati.it>
ciencio ha scritto:
> Hello,
> I bought the TV card in the object, it is a PCI hybrid TV-card, both
> analogue and DVB-T.
>
> I bought it, because on the manufacturer site they said they develop a
> linux driver, unfortunately when I downloaded the driver (which claims
> to be for fedora) I found the whole V4L tree to be compiled.
>
> By the way, I tried to compiled it but it failed 'because it looked for
> the 2.6.19 kernel sources while I'm on Ubuntu Intrepid with a 2.6.27.
While I was trying to make the card work, I found a peculiar note in the
NotOnlyTV faq that says that the driver they provide only works on
Fedora 6.0.
Since Fedora 6.0 is an "old" distro (Fedora is now at the 10th revision)
and since on ubuntu intrepid, the distro I'm using, the 2.6.19 kernel
isn't available, I wondered if and how I could manage to apply the
modifications they did to the main tree to make the driver work on more
recent kernels and if those modifications could be imported in the main
tree.
I attach the link to the V4l tree NOT provide is someone more expert
than me wants have a look.
http://www.notonlytv.net/download/driver/lv3hlv3afedora.rar
And this is their faq (not very usefull indeed)
http://www.notonlytv.net/download/faq/faq_lv3h.pdf
Last thing, how can I know if someone is working on that card or on the
chipset that card uses?
--
Vic
next prev parent reply other threads:[~2009-03-04 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 20:52 lifeview NOT LV3H not working ciencio
2009-03-04 8:34 ` vic [this message]
2009-03-09 9:42 ` vic
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=49AE3D17.20401@zini-associati.it \
--to=vic@zini-associati.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox