Hi...
I am currently writing a driver for a hardware codec accelerator. The calling application will open a media file, write to the codec driver, and read frames back from the codec driver. My issue comes with the read of the media file. The structure of media files is complex and I'd rather the calling application didn't need to have any knowledge of that structure. But how can the driver do the necessary read() operations?
I could, for example, have the application pass an open file descriptor in to my driver via an ioctl() call; if I understand matters correctly, my driver could then call sys_read(). I've never done anything like that before, never expected to need to, and it doesn't feel right.
Can anyone suggest the *proper* way to accomplish this?
I am not a member the list list; I hit the weekliess pretty frequently, but I'd appreciate it any responders would CC me directly at [email protected]. Thanks.
--Van Wanless
EQware Engineering, Inc.
[email protected]
--Van Wanless
EQware Engineering, Inc.
[email protected]
503-701-4178
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
