From: van <van.wanless@eqware.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: File I/O from within a drive
Date: Wed, 25 May 2005 10:47:55 -0700 [thread overview]
Message-ID: <2005525104755.652038@Oz> (raw)
> Your assumption that the driver should parse the media file structure
> is probably wrong. You should rather do as much as possible in a user
> space library. Pass a file name to a library call and have that
> work with all the complex parts of the file format, then define an
> ioctl interface for the driver on a relatively low level.
I think this is probably the bit of insight I was looking for; when it looks what what you need to do is wrong, you probably don't need to do that.
In fact, right now I am implementing a simple write() interface as a starting point. Later on I will be wanting to used mmap()ed buffers anyway, and at that point the application (or some app-level library) will *absolutely* have to be able to parse frames out of the media file.
Thanks, all.
--Van Wanless
EQware Engineering, Inc.
van.wanless@eqware.net
reply other threads:[~2005-05-25 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2005525104755.652038@Oz \
--to=van.wanless@eqware.net \
--cc=linux-kernel@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