Changes between Version 10 and Version 11 of driver_howto


Ignore:
Timestamp:
07/15/08 21:00:38 (11 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • driver_howto

    v10 v11  
    6666   * '''graphic mode''':
    6767     * ''drv_Sample_blit'': transfer the framebuffer managed by the generic graphic subsystem to the display. That's all what's up to you!
    68    * ''drv_Sample_GPO'': set GPO's
    69    * ''drv_Sample_start'': maybe read some things from the config file, and initialize display
    70    * ''drv_Sample_init'': read things from config (e.g. display size), set some necessary global variables, and initialize the driver
    71    * if your display supports some special features (like contrast, backlight, brightness, ...) implement it as ''plugins''. See ''plugin_contrast'' for an example.
    72    * if there are none, remove all the ''contrast'' stuff
    73    * As your display is either serial or parallel one, you have to adopt these parts, too. Serial (and USB) displays are very easy to handle (there is a drv_generic_serial_send() function which does all the low-level communication). Parallel port displays are a bit tricky, because you have to do all the bit-banging by hand. I tried to provide some very basic functionality in the sample driver (which will surely '''not''' work on any display!), and I hope you get the idea...
     68     * ''drv_Sample_GPO'': set GPO's
     69     * ''drv_Sample_start'': maybe read some things from the config file, and initialize display
     70     * ''drv_Sample_init'': read things from config (e.g. display size), set some necessary global variables, and initialize the driver
     71     * if your display supports some special features (like contrast, backlight, brightness, ...) implement it as ''plugins''. See ''plugin_contrast'' for an example.
     72     * if there are none, remove all the ''contrast'' stuff
     73     * As your display is either serial or parallel one, you have to adopt these parts, too. Serial (and USB) displays are very easy to handle (there is a drv_generic_serial_send() function which does all the low-level communication). Parallel port displays are a bit tricky, because you have to do all the bit-banging by hand. I tried to provide some very basic functionality in the sample driver (which will surely '''not''' work on any display!), and I hope you get the idea...
    7474 * test it with your display
    7575 * run ''./indent.sh'' to apply coding style (this does source code formatting)
     
    7777   * run ''svn diff >your_patch.diff'' and send us the file
    7878   * run ''svn commit -m "<your log message>"'' if you have SVN developer access and '''you know what you're doing'''
    79  * '''add documentation to the wiki!!!'''
     79 * '''Please''' add documentation to the wiki!!!
    8080
    8181It's easy, believe me!