linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: "Sven Köhler" <skoehler@upb.de>
Subject: Re: [uml-devel] Re: skas3 patch breaks ATI video drivers
Date: Wed, 26 Jan 2005 13:24:52 +0100	[thread overview]
Message-ID: <200501261324.52933.blaisorblade@yahoo.it> (raw)
In-Reply-To: <ct7r17$cqj$1@sea.gmane.org>

On Wednesday 26 January 2005 11:24, Sven Köhler wrote:


Please note this exact sentence:
> > I.e. the compilation problem is not in the kernel module, right?

> > In this 
> > case, the problem is that you have /usr/include/asm symlinked to your
> > kernel's include/asm-i386 directory, which is the wrong setup. However
> > your solution should not give any problem.

> Kernel-Modules are usually compiled against the sources in either
> /usr/src/linux or /lib/modules/<version>/build.

> Take a look at the nvidia-kernel ebuild or other ebuilds that build
> kernel modules. It would be fatal to compile them against the headers in
> /usr/include. On Gentoo, you can have linux26-headers-2.6.7 installed,
> but actually be running a 2.6.10 Kernel - and even worse, it is even
> possible to keep 2.4 headers when running a 2.6 kernel.

Sven, that is clear *and* obvious... what I was *refusing* to believe was that 
a kernel module would be using the "syscall" macro - I explained it by 
thinking it was userspace code.

Maybe that use is even legitimate (1), after all, but it astonished me a bit 
first... and my experience with NVIDIA driver was they also had a userspace 
part to link with X11.

(1) legitimate means "ugly hack which can make sense with non-GPL modules, 
i.e. does not make sense anyway". I'm not flaming ATI / NVIDIA, let's leave 
this duty to people with more spare time.
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-01-26 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 19:43 [uml-devel] skas3 patch breaks ATI video drivers Marcus Better
2005-01-24 20:13 ` Blaisorblade
2005-01-25  8:35   ` Marcus Better
2005-01-25 10:01     ` Blaisorblade
2005-01-25 10:55       ` Marcus Better
2005-01-25 11:21         ` Blaisorblade
     [not found]           ` <41FA4919.1040705@better.se>
2005-01-28 15:52             ` Blaisorblade
2005-01-26 10:24   ` [uml-devel] " Sven Köhler
2005-01-26 12:24     ` Blaisorblade [this message]
2005-01-28 15:55 ` [uml-devel] " Blaisorblade

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=200501261324.52933.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=skoehler@upb.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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