-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ulrich Drepper wrote: > On 12/13/06, Teunis Peters <[EMAIL PROTECTED]> 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----- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
