framebuffer

disclaimer / info:

DISCLAIMER:
THIS IS EXPERIMENTAL SOFTWARE AND HARDWARE. USE AT YOUR OWN RISK. THE MAINTAINER(S) OF THESE PAGES AND THE DEVELOPER(S) OF SOFTWARE AND HARDWARE PRESENTED ON THESE PAGES CAN NOT BE HELD LIABLE UNDER ANY CIRCUMSTANCES FOR DAMAGE TO HARDWARE OR SOFTWARE, LOST DATA, OR OTHER DIRECT OR INDIRECT DAMAGE RESULTING FROM THE USE OF THIS SOFTWARE OR HARDWARE. IF YOU DO NOT AGREE TO THESE CONDITIONS, YOU ARE NOT PERMITTED TO USE OR FURTHER DISTRIBUTE THIS SOFTWARE OR TO USE ANY TEMPLATES FOR BUILDING HARDWARE PRESENTED HERE.

• this page deals with using a frambuffer device with serdisplib
• i'm not responsible for the content of external web pages
• external web pages will generally open in separate browser windows or tabs
• english is not my native language. please keep that in mind (corrections of english grammar and formulations are very welcome!)
• email: mrwastl at users.sourceforge.net

framebuffer:

description

connecting a framebuffer device:

intro

important

• the framebuffer device needs read/write-access for serdisplib
• the touchscreen device needs at least read-only access for serdisplb
• file-rights should be set using udev-rules (including a symlink for the touchscreen device)
• the framebuffer device usually is something like /dev/fbX (X ... number of framebuffer)
• the touchscreen device usually is an unpredictable input device (like /dev/input/input47) so it is best to let udev create a symlink

example for configuration of the touchscreen:

SUBSYSTEM=="input",ATTRS{idVendor}=="1ac7", ATTRS{idProduct}=="0001", GROUP="users",MODE="0660", SYMLINK+="input/touchscreen"

• idVendor 1ac7 / idProduct 0001 is for an E2i touchscreen (this can be found for example in Mimo 720s USB monitors)
• group should be changed according to ones needs
• SYMLINK would create a symlink for the touchscreen device which can be accessed via /dev/input/touchscreen
• this udev-rule should be called as late as possible (thus it should be placed in a rule like 99-somerules.rules)

examples

configuration in lcd4linux

 Display SerDispLib {
   Driver 'serdisplib'
   Model 'framebuffer'
   Options 'FBDEVICE=/dev/fb1;TOUCHDEVICE=/dev/input/touchscreen'
 }

configuration in graphlcd

 [serdisp_framebuffer]
 Driver=serdisp
 Controller=framebuffer
 Options=FBDEVICE=/dev/fb0

 [mimo720s]
 Driver=serdisp
 Controller=framebuffer
 Options=FBDEVICE=/dev/fb1;TOUCHDEVICE=/dev/input/touchscreen;TOUCHSWAPY=1

calling test program testserdisp

  testserdisp -n framebuffer -o 'FBDEV=/dev/fb1'
  testserdisp -n framebuffer -o 'FBDEV=/dev/fb1;TOUCHDEVICE=/dev/input/touchscreen;TOUCHSWAPY=1;ROTATE=90'

passing options through serdisp_init():

intro

    examples:

      serdisp_init(sdcd, "FRAMEBUFFER", "FBDEV=/dev/fb1");
      serdisp_init(sdcd, "FRAMEBUFFER", "FBDEV=/dev/fb1;TOUCHDEVICE=/dev/input/touchscreen;TOUCHSWAPY=1;ROTATE=90");
    

options

ranges, aliases

options for specific framebuffer devices

history: