From: Wolfgang Denk <wd@denx.de>
To: "Sampath Kumar" <sampath@spartanlabs.com>
Cc: "Juergen Oberhofer" <e9826367@student.tuwien.ac.at>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: mpc / linux kernel - user space
Date: Fri, 28 Nov 2003 09:14:30 +0100 [thread overview]
Message-ID: <20031128081435.DC0CDC5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 28 Nov 2003 11:04:09 +0530." <006801c3b571$408bc6e0$c314a8c0@cm>
In message <006801c3b571$408bc6e0$c314a8c0@cm> you wrote:
>
> Write an ioctl method in your module. And provide provision in ioctl to take
> a function pointer & store it.
What a bogus advice.
You CANNOT call user space code from kernel context. [And actually
you don't want to.]
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Human beings were created by water to transport it uphill.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-11-28 8:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 16:07 mpc / linux kernel - user space Juergen Oberhofer
2003-11-27 17:38 ` Jaap-Jan Boor
2003-11-27 18:08 ` Juergen Oberhofer
2003-11-27 19:28 ` Dan Kegel
2003-11-28 4:30 ` How to change /proc to the writable directory John Zhou
2003-11-28 8:12 ` Wolfgang Denk
2003-11-28 9:16 ` mpc / linux kernel - user space Jaap-Jan Boor
2003-11-28 15:42 ` Dan Malek
2003-12-01 8:18 ` Jaap-Jan Boor
2003-12-01 12:51 ` Peripherals Memory Mapping Kevin A. Sapp
2003-12-14 15:28 ` Paul Miller
2003-12-01 13:47 ` mpc / linux kernel - user space Juergen Oberhofer
2003-11-28 5:34 ` Sampath Kumar
2003-11-28 8:14 ` Wolfgang Denk [this message]
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=20031128081435.DC0CDC5F5F@atlas.denx.de \
--to=wd@denx.de \
--cc=e9826367@student.tuwien.ac.at \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sampath@spartanlabs.com \
/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 NNTP newsgroup(s).