Messages in this thread | | | Date | Mon, 1 Jan 2007 23:59:43 +0900 | From | Paul Mundt <> | Subject | Re: Using _syscall3 to manipulate files in a driver |
| |
On Sun, Dec 31, 2006 at 12:13:52PM -0500, Jon Smirl wrote: > I have the source code for a vendor written driver that is targeted at > 2.6.9. It includes this and then proceeds to manipulate files from the > driver. > > asmlinkage _syscall3(int,write,int,fd,const char *,buf,off_t,count) > asmlinkage _syscall3(int,read,int,fd,char *,buf,off_t,count) > asmlinkage _syscall3(int,open,const char *,file,int,flag,int,mode) > asmlinkage _syscall1(int,close,int,fd) > > What is the simplest way to get open/close/read/write working under > 2.6.20-rc2? I know this is horrible and shouldn't be done, I just want > to get the driver working long enough to see if it is worth saving. > I'm on x86. > In-kernel syscalls were removed by f5738ceed46782aea7663d62cb6398eb05fc4ce0. You can stub them back in if you want a quick and lame fix for the driver, but you're better off rewriting it to behave sensibly rather than wasting your time on vendor hacks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |