public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Priestley <tvboxspy@gmail.com>
To: Mehmet Altan Pire <baybesteci@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: DM04 USB DVB-S TUNER
Date: Sun, 05 Jun 2011 22:47:35 +0100	[thread overview]
Message-ID: <1307310455.2547.9.camel@localhost> (raw)
In-Reply-To: <1307306576.2064.13.camel@localhost>

On Sun, 2011-06-05 at 21:42 +0100, Malcolm Priestley wrote:
> On Sun, 2011-06-05 at 19:34 +0300, Mehmet Altan Pire wrote:
> > 05-06-2011 17:16, Malcolm Priestley yazmış:
> > > On Sun, 2011-06-05 at 03:35 +0300, Mehmet Altan Pire wrote:
> > >> Hi,
> > >> I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-build
> > >> drivers/modules but device  doesn't working (unknown device).
> > >>
> > >> lsusb message:
> > >> ID 3344:22f0
> > >>
> > >> under of the box:
> > >> DM04P2011050176
> > >
> > Yes, i have windows xp driver, name is "US2B0D.sys" I sending it,
> > attached in this mail. Thanks. 
> 
> Here is a modified lmedm04.c and lme2510b_fw.sh using the US2B0D.sys
> 
> Tested here, it appears to work with the sharp7395 tuner.
> 
> Are you sure it works under Windows?  I can't find your ID in the
> US2B0D.sys file. It may be a blank lme2510c chip.
> 
> I assume you are using the lastest media_build to update driver then
> over write lmedm04.c 
> 
> found in;
> media_build/linux/drivers/media/dvb/dvb-usb
> 
> If already build, just a make and sudo make install is required.
I have done some further tests with this firmware and it does not return
the correct signal lock data. By default the signal lock returns the
last good lock and updated by interrupt. This just means when lock is
lost the driver still returns lock.

I will need to modify the interrupt return.

However, it may be a different tuner.

tvboxspy





  parent reply	other threads:[~2011-06-05 21:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05  0:35 DM04 USB DVB-S TUNER Mehmet Altan Pire
     [not found] ` <1307283393.22968.12.camel@localhost>
2011-06-05 16:34   ` Mehmet Altan Pire
     [not found]     ` <1307306576.2064.13.camel@localhost>
2011-06-05 21:47       ` Malcolm Priestley [this message]
2011-06-06 23:28         ` Mehmet Altan Pire
2011-06-07  5:31           ` Malcolm Priestley
2011-06-07 19:34             ` Malcolm Priestley
     [not found]               ` <4DEF5A9F.8000200@gmail.com>
2011-06-08 15:20                 ` Malcolm Priestley
2011-06-25 21:10                   ` Malcolm Priestley
2011-09-04 19:33                     ` Malcolm Priestley
  -- strict thread matches above, loose matches on Subject: below --
2012-01-17 18:46 Dream HTPC
2012-01-17 20:24 ` Malcolm Priestley

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=1307310455.2547.9.camel@localhost \
    --to=tvboxspy@gmail.com \
    --cc=baybesteci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox