lkml.org 
[lkml]   [1998]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: unresolved symbol open
Vasili Goutas wrote:
>
> I'm writing a device driver how needs to read a file during initialize.
> I tried to use the functions open() read() seek() and close() and
> included the asm/unistd.h, but I get unresolved symbols.
> Then I tried to use the sys_* functions, and get also a lot of
> unresolved symbols, only the sys_close() function was known.
> A look at the symbol table of my 2.0.34 kernel by 'cat /proc/ksyms'
> shows me that they realy are missing.
> Why are the other functions missing?
> Is there another way to access files from a driver?

I,m not very sure it this is possible. If your driver is
linked in kernel it can't read anything from FS because there
is not available during system init.
If the driver is module, try to send contents of config file
thru ioctl(you have to support ioctl sys_call). I think this is
easier.


Petkan

--
Petko Manolov, http://www.varel.bg/~petkan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:44    [W:0.056 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site