From: Antti Palosaari <crope@iki.fi>
To: linux-media <linux-media@vger.kernel.org>
Cc: htl10@users.sourceforge.net
Subject: DVB core enhancements - comments please?
Date: Thu, 28 Jun 2012 03:33:26 +0300 [thread overview]
Message-ID: <4FEBA656.7060608@iki.fi> (raw)
Here is my list of needed DVB core related changes. Feel free to comment
- what are not needed or what you would like to see instead. I will try
to implement what I can (and what I like most interesting :).
general validly checking for demodulator callback input values
--------------------------------------------------
* currently each driver needs to validate those
* values are highly hooked up to used television standard
* we can do almost all validly checking inside core
* we can also check if call is possible to perform in given condition
* for example BER is not valid when demod is unlocked
suspend / resume support
--------------------------------------------------
* support is currently quite missing, all what is done is on interface
drivers
* needs power management
* streaming makes it hard
* quite a lot work to get it working in case of straming is ongoing
use Kernel power management instead of own
--------------------------------------------------
* there seems to be Kernel services for power-management
* study if it is wise to use Kernel services instead of own
* own PM is still working very well, at least I dont know any problems
SDR - Softaware Defined Radio support DVB API
--------------------------------------------------
*
http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/44461
* there is existing devices that are SDR (RTL2832U "rtl-sdr")
* SDR is quite near what is digital TV streaming
* study what is needed
* new delivery system for frontend API called SDR?
* some core changes needed, like status (is locked etc)
* how about demuxer?
* stream conversion, inside Kernel?
* what are new parameters needed for DVB API?
DTMB standard support for DVB API
--------------------------------------------------
* it is Chinese DTV standard
* I already ran RFC but have been too busy for implementing it :]
LNA (low-noise amplifier) support for DVB API
--------------------------------------------------
* there is quite a lot of devices having LNA
* currently not supported => LNA is configured off typically
offer polling method for statistics
--------------------------------------------------
* many static counters could not be read as a "one go"
* typical cycle is : start measurement => wait => read counters
* some drivers starts own internal work-queue for polling (complexity)
* some drivers blocks IOCTL when taking measurement (bad)
fix frontend properties
--------------------------------------------------
* those has been broken since MFE => SFE change
* currently implemented as a properties per driver
* need to be properties per delivery system
* are broken because driver/chip could support multiple DTV standards
regards
Antti
--
http://palosaari.fi/
next reply other threads:[~2012-06-28 0:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 0:33 Antti Palosaari [this message]
2012-06-29 4:32 ` DVB core enhancements - comments please? Mauro Carvalho Chehab
2012-06-29 5:03 ` Antti Palosaari
2012-06-29 11:24 ` Patrick Boettcher
2012-06-29 13:07 ` Antti Palosaari
2012-06-29 14:21 ` Patrick Boettcher
2012-06-29 14:28 ` Mauro Carvalho Chehab
2012-07-02 21:27 ` Antti Palosaari
2012-07-03 16:25 ` Mauro Carvalho Chehab
2012-07-03 16:50 ` Hin-Tak Leung
2012-07-03 19:54 ` Mauro Carvalho Chehab
2012-06-29 12:02 ` Mauro Carvalho Chehab
2012-06-29 12:55 ` Antti Palosaari
2012-06-30 9:44 ` Marko Ristola
2012-07-01 11:11 ` Antti Palosaari
2012-07-03 17:21 ` Marko Ristola
2012-07-21 16:36 ` Antti Palosaari
2012-07-25 10:38 ` Antti Palosaari
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=4FEBA656.7060608@iki.fi \
--to=crope@iki.fi \
--cc=htl10@users.sourceforge.net \
--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 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.