Bongani Hlope schrieb:
On Monday 31 March 2008 13:47:23 Bernd Büttner wrote:
Bongani Hlope schrieb:
8<
You really shouldn't be doing that in a module, that is why those symbols
are not exported. But if you really insist on reading/writing a file in a
kernel module look here: http://www.linuxjournal.com/article/8110 it has
both the lengthy warning and examples of how to do it if you insist on
doing the "wrong" thing
Thank you for the hint.
I read the article and understand the problems.
But I don't want to read from a file. I just want to read and write single
bytes from and to a qspi-device. If I don't want to rewrite the qspi
functions I have to call the qspi-driver.
So what I'm searching for is a way to read/write a qspi-device from kernel
mode without the indirection through user-mode.
What device does you module drive?
I have a device driver which handles digital and analog i/o. Most of them are
located
at pins of the coldfire cpu, some of them are behind the qspi bus. All
data-ports are
scanned in a settable time intervall and represented to user-space as a data
field.
User-space doesn't know whether data are located behind qspi or not.
The hardware is flexible (no hotplugging), so the driver has a configuration
area which
is loaded from a flash device during startup, this is the reason for loadable
modules.
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
