public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Subject: Re: [PATCH RFCv1] v4l2: add support for SDR transmitter
Date: Fri, 15 May 2015 14:20:46 +0300	[thread overview]
Message-ID: <5555D68E.4090708@iki.fi> (raw)
In-Reply-To: <5555BB9C.8070605@xs4all.nl>

Moikka!

On 05/15/2015 12:25 PM, Hans Verkuil wrote:
> Hi Antti,
>
> Looks good, but the DocBook updates are missing. You probably planned to do that in
> RFCv2 or similar.

Yep, first code then doc.

> Which device will have sdr_out? What's the cheapest device and where can I buy it? I'd
> like to be able to test it (and add qv4l2 support),

I used HackRF One, it is likely 150-250e used one.

Currently I have implemented almost all radio features it has, only 
option to enable antenna power supply is missing (and firmware upgrade, 
but it is not radio feature).

Device is half-duplex - only RX or TX could be used at the time. Driver 
creates two device nodes, one for receiver and another for transmitter.

There is:
2 x struct video_device
2 x struct v4l2_device
2 x struct vb2_queue
2 x struct v4l2_ctrl_handler

Locking is still missing. I am not sure how it should be done, but 
likely I try add lock to start/stop streaming. When start streaming is 
called it sets some flag/lock and if another device node tries start 
streaming at same time error is returned.

Device uses Complex S8 format for both receiver and transmitter. I will 
add that format to vivid and then it should be possible generate beep 
using vivid and transmit it using HackRF (cat /dev/swradio0 > 
/dev/swradio1), where swradio0 is vivid and swradio1 is HackRF.

regards
Antti

-- 
http://palosaari.fi/

      reply	other threads:[~2015-05-15 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 17:51 [PATCH RFCv1] v4l2: add support for SDR transmitter Antti Palosaari
2015-05-15  9:25 ` Hans Verkuil
2015-05-15 11:20   ` Antti Palosaari [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=5555D68E.4090708@iki.fi \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox