This is a very bad idea - suppose the user wants to move the configuration
file location. Better to put the parsing of the configuration file into
parameters in user space and pass arguments to insmod
> and I'm trying to open it just for reading. Is there any weird
> semantics to using sys_open() from a module that I should be aware of?
Yes. sys_open takes its path name from user space. If you must do this
get the latest DaveM snapshot and look in the sound directory at the
firmware loading routines