From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Randazzo, Michael" <RANDAZZO@ddc-web.com>
Cc: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: Kernel 2.x POSIX Compliance/Conformance...
Date: Wed, 4 Feb 2004 16:39:07 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0402041631470.3277@chaos> (raw)
In-Reply-To: <89760D3F308BD41183B000508BAFAC4104B16F39@DDCNYNTD>
On Wed, 4 Feb 2004, Randazzo, Michael wrote:
> ok...I think I get it....
>
> I can't use any of the posix functions in
> device drivers (modules).....is this correct?
>
> M.
You cannot ever use any 'C' runtime library functions in your
modules. This means you cannot use open(), close(), read(),
write(), lseek(), etc. However, the kernel has some of its
own POSIX-compliant functions like memset(), memcpy(), strcpy(),
etc. You can look in ../linux-nn.nn/lib or look through the
headers to see what's available. There are semaphones and
other locking mechanisms available for use in the kernel
which, I recall, was your first inquiry.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-02-04 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 20:22 Randazzo, Michael
2004-02-04 21:39 ` Richard B. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 20:18 Randazzo, Michael
2004-02-04 20:21 ` Valdis.Kletnieks
2004-02-04 20:51 ` Torrey Hoffman
2004-02-04 21:02 ` J.A. Magallon
2004-02-04 19:44 Randazzo, Michael
2004-02-04 19:58 ` Valdis.Kletnieks
2004-02-04 19:30 Randazzo, Michael
2004-02-04 19:40 ` Valdis.Kletnieks
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=Pine.LNX.4.53.0402041631470.3277@chaos \
--to=root@chaos.analogic.com \
--cc=RANDAZZO@ddc-web.com \
--cc=Valdis.Kletnieks@vt.edu \
--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
all inboxes | Powered by JetHome®