Re: Using _syscall3 to manipulate files in a driver

2007-01-01 Thread Daniel Drake
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. In future just kill the code in question, it's wrong and not needed. It's already mostly disabled in the code, based on my requ

Re: Using _syscall3 to manipulate files in a driver

2007-01-01 Thread Jon Smirl
On 1/1/07, Paul Mundt <[EMAIL PROTECTED]> wrote: 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,writ

Re: Using _syscall3 to manipulate files in a driver

2007-01-01 Thread Paul Mundt
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) > asmlinkag

Re: Using _syscall3 to manipulate files in a driver

2007-01-01 Thread bert hubert
On Sun, Dec 31, 2006 at 12:13:52PM -0500, Jon Smirl wrote: > 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 no expert, but try loo

Using _syscall3 to manipulate files in a driver

2006-12-31 Thread Jon Smirl
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 _syscal