From: Teunis Peters <teunis@wintersgift.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question: removal of syscall macros?
Date: Wed, 13 Dec 2006 12:44:49 -0800 [thread overview]
Message-ID: <45806641.5010105@wintersgift.com> (raw)
In-Reply-To: <a36005b50612131201j766d7585yad6d77629582d468@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ulrich Drepper wrote:
> On 12/13/06, Teunis Peters <teunis@wintersgift.com> wrote:
>> Now that syscall macros have been pulled from the -mm tree, what method
>> is recommended to use syscalls?
>
> glibc forever had a syscall() function for just that purpose. It was
> never a good idea to use the macros since they didn't work in PIC.
sorry - I should be a little more context specific.
for KERNEL modules that used the _syscallX macros - what mechanism should be used?
I'm aware that the drivers I'm having a problem with (ATI, vmware) are closed source - but my own work machine's dependant on it and I'm not going to waste another 3 months to get
a response from either company.
and since the macros were pulled... and I'm kind of stuck with bleeding edge until some of the other hardware I'm working with is supported... *frustrated sigh*
At the moment my workaround is just to copy the macros from released kernel in. I don't like that solution - but it DOES work.
Unless someone can suggest a low-price but recent - and still sold - laptop model that works well with linux. (rhetorical - if anyone DOES answer, keep it off the list - thanks *g*)
- - Teunis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFgGZBbFT/SAfwLKMRAvAWAJ91BZCCIFrcGTkPaahf+Vd+tPvtewCfee/g
6BAirwLkefSqJbqGruk3L3o=
=Mr7+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-12-13 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 18:51 Teunis Peters
2006-12-13 19:46 ` Arjan van de Ven
2006-12-13 20:01 ` Ulrich Drepper
2006-12-13 20:44 ` Teunis Peters [this message]
2007-03-13 3:06 ` albcamus
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=45806641.5010105@wintersgift.com \
--to=teunis@wintersgift.com \
--cc=drepper@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®