How to compile a kernel module for AT91SAM9263 board with buildroot linux

We are using open source so we need to add our modules into the kernel.
We are trying to compile a gpio module for our kernel.But we dont know the procedure. Can anyone tell if it is possible to add a *.ko file into the board just by copying it into the board or not? or is there any other way to register the driver into the board? Please help if you can.

Start a New Thread

On Sat, 16 May 2009 09:27:15 -0000
"pratibha_275" wrote:
> We are using open source so we need to add our modules into the
> kernel. We are trying to compile a gpio module for our kernel.But
> we dont know the procedure. Can anyone tell if it is possible to add a
> *.ko file into the board just by copying it into the board or not? or
> is there any other way to register the driver into the board? Please
> help if you can.

I'm not totally sure of what all kernels do to determine module
compatibility, but if you've used Buildroot to compile your kernel,
then, yes, if you use that same buildroot to compile a module I've had
just copying the module over to the board (into the right place) work
fine.

Note that you have to do the appropriate insmod or modprobe command to
load the module.
Start a New Thread

Your module can be loaded anywhere. When I play/study with modules, I use
NFS and leave the module on the host.
With compatibility, you can use versioning, refer to Version Magic.
If the version is wrong the Kernel will complain about that, but you can
override this if you wish.

HTH
Kris

On Sat, 16 May 2009 07:03:14 -0700, Dan Lyke wrote:
> On Sat, 16 May 2009 09:27:15 -0000
> "pratibha_275" wrote:
>> We are using open source so we need to add our modules into the
>> kernel. We are trying to compile a gpio module for our kernel.But
>> we dont know the procedure. Can anyone tell if it is possible to add a
>> *.ko file into the board just by copying it into the board or not? or
>> is there any other way to register the driver into the board? Please
>> help if you can.
>
> I'm not totally sure of what all kernels do to determine module
> compatibility, but if you've used Buildroot to compile your kernel,
> then, yes, if you use that same buildroot to compile a module I've had
> just copying the module over to the board (into the right place) work
> fine.
>
> Note that you have to do the appropriate insmod or modprobe command to
> load the module.
> Start a New Thread

Thanks a lot!!!
--- In A..., wrote:
>
> Your module can be loaded anywhere. When I play/study with modules, I use
> NFS and leave the module on the host.
> With compatibility, you can use versioning, refer to Version Magic.
> If the version is wrong the Kernel will complain about that, but you can
> override this if you wish.
>
> HTH
> Kris
>
> On Sat, 16 May 2009 07:03:14 -0700, Dan Lyke wrote:
> > On Sat, 16 May 2009 09:27:15 -0000
> > "pratibha_275" wrote:
> >> We are using open source so we need to add our modules into the
> >> kernel. We are trying to compile a gpio module for our kernel.But
> >> we dont know the procedure. Can anyone tell if it is possible to add a
> >> *.ko file into the board just by copying it into the board or not? or
> >> is there any other way to register the driver into the board? Please
> >> help if you can.
> >
> > I'm not totally sure of what all kernels do to determine module
> > compatibility, but if you've used Buildroot to compile your kernel,
> > then, yes, if you use that same buildroot to compile a module I've had
> > just copying the module over to the board (into the right place) work
> > fine.
> >
> > Note that you have to do the appropriate insmod or modprobe command to
> > load the module.
> >
> >
> >
> >
> > Start a New Thread