Re: [microblaze-uclinux] driver missing after boot up

[Wendy Liang <wendy.liang@xxxxxxxxxxxxx>]

Hi Chris,

If you want a built-in driver, you should configured the driver as a built-in driver. e.g. CONFIG_TUN=y instead of CONFIG_TUN=m.

You have to add a device node to the root file system image if your root file system is read only (by default, petalinux uses read only file system) by changing the petalinux-dist/vendors/PetaLogix/common/common.mak.

E.g. if you want to add a `tun` in `/dev/net`, you can try to add the following code in `ifndef CONFIG_SYSTEM_ROOTFS_JFFS2` section in common.mak file.

ifdef CONFIG_TUN
  mkdir -p $(ROMFSDIR)/dev/net
  touch $(ROMFSDIR)/dev/net/@<device name>,<device type>,<major num>,<minor num>
endif

Regards,
Wendy

On Thu, Apr 23, 2009 at 4:20 AM, Chris Robson <clr1004@xxxxxxxxxxx> wrote:

Driver question...

I'm trying get a tun interface enabled after bootup for a Petalinux
build. The driver is built, aka tun.c is built resulting in tun.o.
However after loading up image.ub on the target system the only .ko file
I can find is:

/lib/modules/2.6.20-uc0/kernel/drivers/char/hw_random/rng-core.ko

Is there a place I should be looking to further enable the module driver
at build time? What is strange, to me at least, is the eth0 E1000
interface works but it also as no .ko file.

Thanks....chris

---

Rediscover Hotmail®: Get e-mail storage that grows with you. Check it out.