From: Darron Broad <darron@kewl.org>
To: wk <handygewinnspiel@gmx.de>
Cc: Hans Werner <HWerner4@gmx.de>, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] wscan: improved frontend autodetection
Date: Thu, 06 Nov 2008 17:39:13 +0000 [thread overview]
Message-ID: <29835.1225993153@kewl.org> (raw)
In-Reply-To: <49131C19.1080404@gmx.de>
In message <49131C19.1080404@gmx.de>, wk wrote:
>
>Hi,
LO
>Hans Werner wrote:
>> Currently wscan will not autodetect frontends which which have frontend != 0,
>> i.e. it only detects /dev/dvb/adapterN/frontend0 where N=0-3.
>>
>> Since multiple frontends per adapter are supported in 2.6.28, this means the correct
>> frontend may not be found. For example with the HVR4000, DVB-T is always at frontend1.
>>
>> The attached patch fixes this, searching for frontend 0-3 for each adapter 0-3.
>>
>> Signed-off-by: Hans Werner <hwerner4@gmx.de>
>Good idea. :)
>But while testing your patch it seems that it doesn't work as expected.
>Here some example:
>
>w_scan version 20081106
>Info: using DVB adapter auto detection.
> Found DVB-C frontend. Using adapter /dev/dvb/adapter0/frontend0
> Found DVB-C frontend. Using adapter /dev/dvb/adapter1/frontend0
> Found DVB-C frontend. Using adapter /dev/dvb/adapter2/frontend0
>Info: unable to open frontend /dev/dvb/adapter3/frontend1'
>Info: unable to open frontend /dev/dvb/adapter3/frontend2'
>Info: unable to open frontend /dev/dvb/adapter3/frontend3'
>-_-_-_-_ Getting frontend capabilities-_-_-_-_
>
>I'm using three dvb-c frontends.
>The detection doesnt stop anymore with your patch if a matching frontend
>was found, because it doesnt leave the outer loop.
>Normally this search has to stop at /dev/dvb/adapter0/frontend0.
>That means we have to change your patch a little. I also increased the
>number of adapters to 8, since i use more than 4.
>
>Can you please test the attached patch and give some feedback? If it
>works fine for you, i would apply to w_scan.
>
>-Winfried
>
>PS: What is actually the maximum number of adapters and frontends per
>adapter? Can anybody give some hint?
In relation to what Hans is addressing (Mutually exclusive frontends
on a single adapter AKA multi-frontend AKA MFE) then in theory the
core code is is not limited yet in practice there is a fixed provision
for two as that's the most that has been seen as yet.
Cya!
--
// /
{:)==={ Darron Broad <darron@kewl.org>
\\ \
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-11-06 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 12:47 [linux-dvb] [PATCH] wscan: improved frontend autodetection Hans Werner
2008-11-06 14:43 ` Hans Werner
2008-11-06 20:40 ` wk
[not found] ` <200811081130.21951.liplianin@tut.by>
[not found] ` <1a297b360811081323k61c0dd44vf3834ba965b20466@mail.gmail.com>
2008-11-09 18:25 ` [linux-dvb] [PATCH] stb0899: Set min symbol rate to 1000000 Goga777
2008-11-19 13:40 ` Morgan Tørvolt
2008-11-21 20:45 ` Manu Abraham
2008-11-06 16:32 ` [linux-dvb] [PATCH] wscan: improved frontend autodetection wk
2008-11-06 17:37 ` Hans Werner
2008-11-06 20:44 ` wk
2008-11-06 17:39 ` Darron Broad [this message]
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=29835.1225993153@kewl.org \
--to=darron@kewl.org \
--cc=HWerner4@gmx.de \
--cc=handygewinnspiel@gmx.de \
--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 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.