Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_class_itemlist.php on line 448
Arpith Chacko Jacob<br /> <b>Warning</b>: date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in <b>/home/web/arpith/b2evocore/_functions_cats.php</b> on line <b>401</b><br /> - Adding a new kernel module into the uClinux distribution
Arpith Chacko Jacob - since 1982...

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 342

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 358

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 359

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 391

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 342

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 358

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 359

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 391

  Adding a new kernel module into the uClinux distribution


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 342

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 358

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 359

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 391
Saturday 24th 2004f July 2004,
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 342

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 358

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 359

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/web/arpith/b2evocore/_functions.php on line 391
09:16:10 am. Posted in: Embedded. 493 words.  

This article details the steps that need to be followed to add a kernel module to the uClinux build process.

In case a driver is being added to an existing directory, for example a serial driver in uClinux-dist/linux-2.4.x/drivers/char/, the existing Makefile and Config.in files need to be modified as detailed in steps 1, 4 and 5.

If however the driver is to be added to a new directory in uClinux-dist/linux-2.4.x/drivers/, all steps below must be followed:

  1. The directory, say acme, is created in uClinux-dist/linux-2.4.x/drivers/ and the file uClinux-dist/linux-2.4.x/drivers/acme/Makefile is created with the following contents:
    export-objs := i2s.o
    obj-$(CONFIG_ACME) += acme.o

    subdir-$(CONFIG_ACME_LCD) += lcd

    acme-objs := i2s.o pinpad.o

    acme.o: $(acme-objs)
            $(LD) -r -o $@ $(acme-objs)

    include $(TOPDIR)/Rules.make

    In the Makefile above, two objects to be linked with the kernel or to be built as modules (as the case may be) are created. acme.o is created in uClinux-dist/linux-2.4.x/drivers/acme/ from i2s.c and pinpad.c. i2s.c contains certain symbols that must be exported to the kernel symbol table (via the EXPORT_SYMBOL macro in the code). Hence it is added in the 'export-objs' variable. The second object file is created in the subdirectory 'lcd'. A corresponding Makefile and source code must exist in that subdirectory.

  2. Next, uClinux-dist/linux-2.4.x/drivers/Makefile is modified to include the new directory in the kernel build process:
    subdir-$(CONFIG_ACME) += acme
  3. The top level Makefile in uClinux-dist/linux-2.4.x/ is also modified to add the following lines:
    DRIVERS-$(CONFIG_ACME) += drivers/acme/acme.o
    DRIVERS-$(CONFIG_ACME_LCD) += drivers/acme/lcd/lcd.o
  4. A configuration option for the drivers must also be added in Config.in. This can be done in the architecture specific directory, for example uClinux-dist/linux-2.4.x/arch/armnommu/, or in the driver directory. In the latter case the driver configuration must be included from the top level configuration file, by adding the following line in uClinux-dist/linux-2.4.x/arch/armnommu/Config.in:
    source drivers/acme/Config.in

    The Config.in file contains options to select the driver during the configuration process, and can be added in an existing or new driver group.

    #----------------------------------------
    #                    A C M E
    #----------------------------------------
    mainmenu_option next_comment
    comment 'ACME Kernel module'
    tristate 'ACME driver support' CONFIG_ACME
    tristate 'ACME lcd support' CONFIG_ACME_LCD
    endmenu

    The selected configuration after a 'make xconfig' is saved in: uClinux-dist/linux-2.4.x/.config.
    CONFIG_ACME and CONFIG_ACME_LCD should be set to 'y' or 'm' to build the drivers as part of the kernel image or as modules respectively.

  5. Finally, a description of the driver is added by editing the file uClinux-dist/linux-2.4.x/Documentation/Configure.help
    CONFIG_ACME
      This option enables the ACME driver.

A 'make xconfig; make dep; make' builds the driver as part of the linux kernel.

Comments:

No Comments for this post yet...



Post a comment:

Name:

Email:

Your email address will not be displayed on this site.
Site/Url:

Comment text:

Allowed XHTML tags: <p, ul, ol, li, dl, dt, dd, address, blockquote, ins, del, a, span, bdo, br, em, strong, dfn, code, samp, kdb, var, cite, abbr, acronym, q, sub, sup, tt, i, b, big, small>
URLs, email, AIM and ICQs will be converted automatically.

Options:

Auto-BR
Remember me (Set cookies for name, email & url)