Where is the "right place" to put my driver? I tried: /lib/modules/2.6.26.3-rt3/kernel/m9k/m9kdriver.ko and then ran: ./ltib -p modeps -f
The module wasn't loaded during boot.
Should my module show up in: /etc/rc.d/rc.conf $MODLIST=""
Could you point me to a recipe to "make it a package and have LTIB handle it"? Even after a lot of Googling I don't know where to begin.
----- Original Message -----
From: "Stuart Hughes" <address@hidden>
To: address@hidden
Cc: address@hidden
Sent: Friday, February 18, 2011 3:42:20 AM
Subject: Re: [Ltib] User Device Driver Installation
Hi Todd,
The easiest thing is to make it a package and have LTIB handle it.
Another possibility is to run:
$ ./ltib -p modeps -f
after you've copied you're module to the right place.
Regards, Stuart
On 17/02/11 22:18, address@hidden wrote:
> I currently compile a device driver for my target and put it in
> /lib/modules/mydriver.ko. This is done after LTIB is finished.
>
> I run insmod /lib/modules/m9kdriver.ko on the target after boot. This
> all works fine. However, now I want to automate everything so the
> driver gets installed automatically at boot.
>
> I added /lib/modules/m9kdriver.ko to: Target System Configuration --->
> Options ---> load these modules at boot
>
> This doesn't work because depmod/modprobe expects the .ko files to be
> in: /lib/modules/`uname -r`/kernel/
>
> I copied m9kdriver.ko to
> /lib/modules/2.6.26.3-rt3/kernel/m9k/m9kdriver.ko and hoped it would be
> loaded at boot time but it doesn't work. lsmod shows nothing loaded.
> depmod -n does find m9kdriver.ko. (See below)
>
> Specifically, this is what I would like to do:
>
> 1. Compile m9kdriver.ko on my own.
> 2. Copy it to the rootfs.
> 3. Tell LTIB that I want my driver to be loaded, (if I need to.)
> 4. Be happy when it loads at boot.
>
>
> Is this possible? Any hints? Feel free to make recommendations if I'm
> corrupting the flow too much.
>
> As always, much appreciated.
> Todd
>
> Using: ltib 10.1.1 ($Revision: 1.68 $)
> Target: MPC5200
> Host: Ubuntu 10.10
>
>
> address@hidden /]# lsmod
> Module Size Used by
> address@hidden /]# depmod -n
> /lib/modules/2.6.26.3-rt3/kernel/net/xfrm/xfrm_user.ko:
> /lib/modules/2.6.26.3-rt3/kernel/drivers/scsi/scsi_wait_scan.ko:
> /lib/modules/2.6.26.3-rt3/kernel/drivers/char/alloc_rtsj_mem.ko:
> /lib/modules/2.6.26.3-rt3/kernel/drivers/char/rmem.ko:
> */lib/modules/2.6.26.3-rt3/kernel/m9k/m9kdriver.ko:*
> # pci module vendor device subvendor subdevice class
> clas
> s_mask driver_data
> # usb module _type cu_model dev_type dev_model
> # ieee1394 module match_flags vendor_id model_id specifier_id version
> # isapnp module cardvendor carddevice driver_data vendor
> function ...
>
> # module matchBits bustype vendor product version evBits keyBits
> relBits
> absBits mscBits ledBits sndBits ffBits driver_info
> # Aliases extracted from modules themselves.
> alias net-pf-16-proto-6 xfrm_user
> alias of:N*T*Cm9kdrv* *m9kdriver*
> # Aliases for symbols, used by symbol_request().
>
>
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib