From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Bosko Radivojevic <bosko.radivojevic@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Inserting code from userspace to kernel space
Date: Mon, 26 May 2008 08:48:01 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805260846150.29857@anakin> (raw)
In-Reply-To: <d6c8ef150805220541v711c5acahc60541e3fd9f44fc@mail.gmail.com>
On Thu, 22 May 2008, Bosko Radivojevic wrote:
> For now we have two different kernel modules, one exporting a function
> which another module uses. Process of compiling kernel module is quite
> ineligible for standard end user (along with the requirement to
> support multi platform cross compiling) compared to just cross
> compiling a simple code that doesn't use any libraries than libc.
For cross-compiling a kernel module, you need:
- a cross-compiler
For cross-compiling `a simple code that doesn't use any libraries than
libc', you need:
- a cross-compiler
- a cross-libc
Hence the kernel module approach needs less ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-05-26 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 12:41 Bosko Radivojevic
2008-05-22 13:06 ` Jan Engelhardt
2008-05-22 14:31 ` Helge Hafting
2008-05-22 16:04 ` Shuduo Sang
2008-05-25 5:44 ` Alex Belits
2008-05-25 7:18 ` Bart Van Assche
2008-05-26 6:48 ` Geert Uytterhoeven [this message]
2008-05-26 9:54 ` Jike Song
2008-05-23 14:30 devzero
2008-05-25 3:37 ` Shuduo Sang
2008-05-25 3:47 ` David Newall
2008-05-25 15:44 ` Shuduo Sang
2008-05-26 9:44 ` Jiri Kosina
2008-05-26 11:49 ` David Newall
2008-05-25 9:35 devzero
2008-05-25 12:21 ` David Newall
2008-05-25 13:14 ` Tom Spink
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.64.0805260846150.29857@anakin \
--to=geert@linux-m68k.org \
--cc=bosko.radivojevic@gmail.com \
--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®