From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Srinivas G." <srinivasg@esntechnologies.co.in>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Having problem with mmap system call!!!
Date: Thu, 16 Sep 2004 10:54:55 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0409161050200.12305@chaos> (raw)
In-Reply-To: <1095341494.22744.26.camel@localhost.localdomain>
On Thu, 16 Sep 2004, Alan Cox wrote:
> On Iau, 2004-09-16 at 15:07, Richard B. Johnson wrote:
> > if((vp = mmap((caddr_t) HINT, len, PROT, FLAGS, fd, addr)) == SHM_FAIL)
> > {
> > fprintf(stderr, "Can't access shared memory\n");
> > exit(EXIT_FAILURE);
>
> SHM_FAIL is the wrong error check btw.
>
MAP_FAILED only appeared in real late 'C' runtime library headers.
That's why the code defines SHM_FAIL, which is also correct, but
doesn't cause a redefinition error.
> It is much better to do this in the driver than do nasty user mode hacks
> using /dev/mem. When you do it kernel driver side you end up with a
> cleaner mmap interface, a sensible permissions model and the hardware
> device pages mapped directly and nicely into the app
>
Well that's really nice. Now, how do you do that? The kernel DS
is not the user DS so you end up with a kernel hack instead of
a user hack?
Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-09-16 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EE0CBA31942E547B99B3D4BFAB348111078FE@mail.esn.co.in>
2004-09-16 14:07 ` Richard B. Johnson
2004-09-16 13:31 ` Alan Cox
2004-09-16 14:54 ` Richard B. Johnson [this message]
2004-09-16 15:57 ` Alan Cox
2004-09-16 18:13 ` Richard B. Johnson
2004-09-16 20:01 ` Alan Cox
2004-09-16 14:42 Srinivas G.
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.0409161050200.12305@chaos \
--to=root@chaos.analogic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasg@esntechnologies.co.in \
/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®