From: "Green, Neal" <Neal.Green@PERKINELMER.COM>
To: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Devfs ioctl's
Date: Tue, 15 Sep 2009 13:42:00 -0000 [thread overview]
Message-ID: <C79FD82C13618D418DA1ACA93267131E04066E47@AMERMAIL02.PERKINELMER.NET> (raw)
In-Reply-To: <4AAF83BF.5060304@zynaptic.com>
This is my first post to this list so I hope I did it right.
I'm porting a driver to eCos but the io subsystem doesn't provide ioctl.
We don't want to have to change all of our ioctl calls in our
applicatons. I see that other drivers have ioctl functions - what's the
correct way to handle this situation?
-Neal
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-09-15 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 11:12 [ECOS] I/O thread safety Stanislav Meduna
2009-09-15 12:09 ` Chris Holgate
2009-09-15 13:42 ` Green, Neal [this message]
2009-09-15 15:58 ` [ECOS] Re: Devfs ioctl's Grant Edwards
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=C79FD82C13618D418DA1ACA93267131E04066E47@AMERMAIL02.PERKINELMER.NET \
--to=neal.green@perkinelmer.com \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).