Skip to contentSkip to conversation

KWorld DVB-T 305U now working

DISCUSSION Dean 2 participants 2 messages Feb 15, 2010 – Feb 16, 2010 Media (V4L/DVB)

lore
Share & tools
lore

Dean

author
#0 lore raw

My dmesg gave the following (excerpt) when I connected my KWorld 305U.

em28xx #0: Identified as KWorld DVB-T 305U (card=47) em28xx #0:

em28xx #0: The support for this board weren't valid yet. em28xx #0: Please send a report of having this working em28xx #0: not to V4L mailing list (and/or to other addresses)

So here I am, making this announcement. Do I even have the correct mailing list? What is the next step towards re-classifying the KWorld 305U as a supported device?

Regards.

#1 lore raw

V4L2 devices, subdevices, ops and fops.

Hello.

I have been writing this FM radio driver and I'm now trying to implement it as a platform driver that passes IOCTL calls to a subdevice driver that handles the communication with the hardware etc.

For IOCTLs there's a macro v4l2_device_call_until_err in v4l2-device.h that makes the calls pretty convenient to write. But for file operations there's not such define.

This leads me to the question: should there be such a define for fops or should they be treated in a different way? To me the IOCTL callbacks and the file operation callbacks look pretty similar...

Cheers,
Matti