All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Marcus Better <marcus@better.se>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] skas3 patch breaks ATI video drivers
Date: Tue, 25 Jan 2005 11:01:26 +0100	[thread overview]
Message-ID: <200501251101.26981.blaisorblade@yahoo.it> (raw)
In-Reply-To: <41F604BA.30008@better.se>

On Tuesday 25 January 2005 09:35, Marcus Better wrote:
> Blaisorblade wrote:
> > I.e. the compilation problem is not in the kernel module, right?
>
> Yes, the compilation error is in compiling the fglrx module.
Ok, unexpected.
> > In this case, the problem is that you have /usr/include/asm symlinked to
> > your kernel's include/asm-i386 directory,
>
> No, I don't, but I use Debian's make-kpkg which probably uses header
> files from the kernel tree. This is the normal method of building
> kernels on Debian, though.
Well, since it is a kernel module, then it's correct...
> I might add that I tried to fix the problem directly in the fglrx
> module, but it doesn't seem to work.

> It really must use the name 
> modify_ldt in the macro
Yes, because the name in the macro is used to build the "__NR_modify_ldt"
> , and this conflicts with the UML patch.

Ok, this makes me wonder a bit... there is something which may cause conflicts 
in the UML patch (i.e. renaming modify_ldt that way), but it is very 
*strange* that a kernel module uses the "_syscall" macro to do a syscall with 
"int 0x80" while already being in kernelspace...

-- 
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-25  9:44 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 [this message]
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
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=200501251101.26981.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=marcus@better.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.