Hi!

Thanks for the reply, Russel and David.
Now we have tried to build the module in the kernel, and also changed the header 
files, but something still goes wrong.

What we have done is:
Directory arm-linux/linux/drivers/char/
- the module is compiled and situated at this location
- Config.in added:
    tristate �test driver� CONFIG_TEST
- Makefile added:
    ifdef CONFIG_TEST
      O_OBJS+=test.o
    endif

after build kernel,  make modules, and make modules_install the module should be 
situated in /lib/modules/2.4.0-test11-rmk1-arm4 ... but that is where it goes wrong, 
the module does not show up.

Thoughts; We might have missed some step when including the module into the kernel? We 
might be using the wrong major number on the integrator?

Best regards Lena


-----Original Message-----
From: David Rusling [mailto:[EMAIL PROTECTED]]
Sent: den 11 oktober 2001 13:59
To: Lena Svedlund (MIC)
Cc: '[EMAIL PROTECTED]'
Subject: Re: file_operations within the ARM9 integrator + linux


Lena(s),

        it sounds like a cross-compilation problem.   I do exactly this all the
time.  I suggest that you build both the kernel and modules in place 
(that is, build
the module in the kernel sources using it's include files and so on).

Dave

Lena Svedlund (MIC) wrote:

> Me and my colleague have a question requarding Linux and the ARM integrator. We are 
>for the moment working with a ARM9 processor.
> We have build a device driver on a Linux PC and would like to run it on the ARM 
>integrator.
> 
> What we have done so far:
> On the Linux PC (kernel 2.4.2-2 and on the ARM integrator it is kernel 
>2.4.0-test11-rmk1-arm4): Just a simple driver (that works as a loadable module) with 
>the file_operations open,close,read and write.
> 
> The problem is that on the Linux PC everything (open,close,read,write) works just 
>fine but when we try to run it on the ARM integrator (after cross-compiling and 
>insmod -f test.o) the driver can only be opened and closed. 
> It looks like it has problems finding the file_operation functions. 
> Could it have something to do with the include files or where (in what folder) we 
>have put our codes? Now we have put the files(.c, .h and our test function) under 
>lib/modules/2.4.0-test11-rmk1-arm4/kernel/drivers/char.
> 
> 
> If you have the possibilities to help us with this problem we would be grateful.
> Any thoughts are welcome.
> 
> Best reqards
> Lena Hagstr�m & Lena Svedlund
> 
> 
> 
> _______________________________________________
> http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
> Please visit the above address for information on this list.
> 
> 
> 



-- 
----------------------------------------------------------------------
David A Rusling                 Consulting Engineer
                                ARM Limited
                                Liberty House,
                                Moorbridge Road,
                                Maidenhead, SL6 8LT

                                Tel: UK-(0)1628-427754
                                Fax: UK-(0)1628-780551
                                e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------------

_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.

Reply via email to