From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH RFC v2 0/3] Add SDR at V4L2 API
Date: Sun, 21 Apr 2013 10:07:24 -0300 [thread overview]
Message-ID: <5173E48C.1060903@redhat.com> (raw)
In-Reply-To: <5173D576.7090404@iki.fi>
Em 21-04-2013 09:03, Antti Palosaari escreveu:
> You just jumped over all my previous hard work and introduced implementation, as I tried still to study and finalize all requirements....
As it is posted on the topics, this is RFC. I'm sure changes will
be needed there before having it on some state that it can be merged.
>
> http://palosaari.fi/linux/kernel_sdr_api_requirement_specification.txt
Well, we discussed there already:
http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/63123
And I proposed several a few implementation details there. I'm just
going deeper and writing RFC patches to start test/implement it.
> I don't like that. I want just study all requirements and implement
> those as a once and correctly.
Ok, there are topics there yet to study, but in order to to that,
a real implementation is needed. Only implementing it is possible
to cover all that it is needed.
> That one does not meet very many of those listed requirements.
True. It doesn't cover anything that IMO it should be covered by V4L2
controls.
My focus right now is to implement support for:
- set/get frequency;
- get IF;
- set/get standard envelope/bandwidth;
- set/get sample rate (the real code will only show up
when start implementing a SDR driver - I'm yet far
behind this point);
- get tuner frequency range.
Adding new controls are the easy task, as it doesn't require
core changes (well, except for a table there with the control
names).
However, adding core support for SDR is harder, as it requires
to work on several layers at the V4L2 core.
I'm working today on more patches for it, at tuner-core.
Lots of changes are required there, in order to allow
supporting the existing tuner.
My current plan is to test SDR with cx88, so, I need tuner-core
to work fine with it. I've coded only ~50% of what's needed,
and that represents:
15 files changed, 379 insertions(+), 94 deletions(-)
Regards,
Mauro
prev parent reply other threads:[~2013-04-21 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <366469499-31640-1-git-send-email-mchehab@redhat.com>
2013-04-20 17:51 ` [PATCH RFC v2 0/3] Add SDR at V4L2 API Mauro Carvalho Chehab
2013-04-20 17:51 ` [PATCH RFC v2 1/3] [media] " Mauro Carvalho Chehab
2013-04-20 17:51 ` [PATCH RFC v2 2/3] videodev2.h: Remove the unused old V4L1 buffer types Mauro Carvalho Chehab
2013-04-20 17:51 ` [PATCH RFC v2 3/3] [media] V4L2 api: Add a buffer capture type for SDR Mauro Carvalho Chehab
2013-04-20 20:10 ` [PATCH RFCv1] [media] V4L2 sdr API: Add fields for VIDIOC_[G|S]_TUNER Mauro Carvalho Chehab
2013-04-20 20:45 ` Mauro Carvalho Chehab
2013-04-21 14:44 ` Mauro Carvalho Chehab
2013-04-21 9:34 ` [PATCH RFC v2 0/3] Add SDR at V4L2 API Hans Verkuil
2013-04-21 10:09 ` Mauro Carvalho Chehab
2013-04-21 10:34 ` Hans Verkuil
2013-04-21 11:10 ` Mauro Carvalho Chehab
2013-04-21 12:03 ` Antti Palosaari
2013-04-21 13:07 ` Mauro Carvalho Chehab [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=5173E48C.1060903@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=hverkuil@xs4all.nl \
--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.