Wäre interessant als Alternative zu GraphTFT 
Zumindest theoretisch. Ich weiss nicht wie effektiv das ganze mit höheren Auflösungen läuft.
graphlcd (base, vdr-plugin) touchcol branch (archiv)
- wastl
- Geschlossen
-
-
Mit dem tracker bzw. git bin ich noch nicht so firm. Deshalb hänge ich den Patch hier mal an. Ist gegen das aktuelle git.
Wie schon gesagt, im Moment gehen nur 24bit, die Auflösung läßt sich per graphlcd.conf ändern. Es gibt für den VNCSERVER Treiber einen zusätzlichen Parameter "HttpDir". Der beinhaltet den Pfad zum Verzeichnis webclients (inkl., z.B. /usr/share/webclients). Dieses Verzeichnis findet man beim libvncserver Projekt.
Wenn dieser Parameter gesetzt ist, sollte auch ein Zugriff auf port 5800 der Anwendung per web browser gehen.Gruß,
kanadakruemel -
das ginge aber auch einfacher:
serdisplib bietet einen SDL-treiber, der dafuer eingespannt werden kann (den verwende ich zum testen (habe dafuer mehrere sections im graphlcd.conf definiert mit unterschiedl. aufloesungen und farbtiefen). auch die screenshots in diesem thread sind grossteils screenshots vom libSDL-ausgabefenster.ERGAENZUNG:
aber grundsaetzlich sieht der treiber brauchbar aus (habe kurz den patch durchgelesen). spricht nichts dagegen, den einzubauen ... -
Das kannte ich noch gar nicht. Für mich war die Netzwerkfähigkeit von VNC noch ganz nützlich. Ansonsten ist SDL sicherlich performanter.
Wie gesagt, für mich war es nützlich. Deshalb wollte ich es Euch nicht vorenthalten.Gruß,
kanadakruemel -
news (graphlcd-base):
- added new driver 'vncserver' (contrib. by Michael Heyer)
-
So I think we are almost there, when I start vdr, I do not see any reaction from the display, but as soon as I run gdb for debugging the clock appears on the display. I don't know if the output from gdb is of any use as it states that there is no stack when running where or bt see below.
Code
Alles anzeigenroot@avg:~# gdb --args vdr -P 'graphlcd -d st7565r' GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>... Reading symbols from /usr/bin/vdr...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/vdr -P graphlcd\ -d\ st7565r [Thread debugging using libthread_db enabled] [New Thread 0xb7d1eb70 (LWP 10731)] [Thread 0xb7d1eb70 (LWP 10731) exited] [New Thread 0xb751db70 (LWP 10732)] [Thread 0xb751db70 (LWP 10732) exited] [New Thread 0xb7d1eb70 (LWP 10733)] vdr: no primary device found - using first device! [Thread 0xb7d1eb70 (LWP 10733) exited] [Inferior 1 (process 10598) exited with code 02] (gdb) bt No stack. (gdb)This is the output from valgrind which hopefully reveals more.
Code
Alles anzeigen==19619== Thread 2: ==19619== Invalid read of size 4 ==19619== at 0x4BC2E2E: GLCD::cSkinObject::cSkinObject(GLCD::cSkinDisplay*) (object.c:82) ==19619== by 0x4BE0BD3: GLCD::cSkinVariable::cSkinVariable(GLCD::cSkin*) (variable.c:19) ==19619== Address 0x642f598 is 0 bytes inside a block of size 60 free'd ==19619== at 0x4027919: operator delete(void*) (vg_replace_malloc.c:387) ==19619== by 0x4B430BD: cGraphLCDSkinConfig::~cGraphLCDSkinConfig() (in /usr/lib/vdr/plugins/libvdr-graphlcd.so.1.7.21) ==19619== by 0x4B3A4AF: cGraphLCDDisplay::~cGraphLCDDisplay() (in /usr/lib/vdr/plugins/libvdr-graphlcd.so.1.7.21) ==19619== by 0x4B3A596: cGraphLCDDisplay::~cGraphLCDDisplay() (in /usr/lib/vdr/plugins/libvdr-graphlcd.so.1.7.21) ==19619== by 0x4B3F8EA: cPluginGraphLCD::DisconnectDisplay(unsigned int) (in /usr/lib/vdr/plugins/libvdr-graphlcd.so.1.7.21) ==19619== by 0x4B3EC5E: cPluginGraphLCD::~cPluginGraphLCD() (in /usr/lib/vdr/plugins/libvdr-graphlcd.so.1.7.21) ==19619== by 0x4B3EDE0: cPluginGraphLCD::~cPluginGraphLCD() (in /usr/lib/vdr/plugins/libvdr-graphlcd.so.1.7.21) ==19619== by 0x80FC04C: cDll::~cDll() (in /usr/bin/vdr) ==19619== by 0x80FC0AF: cDll::~cDll() (in /usr/bin/vdr) ==19619== by 0x812B9DE: cListBase::Del(cListObject*, bool) (in /usr/bin/vdr) ==19619== by 0x80FD234: cPluginManager::Shutdown(bool) (in /usr/bin/vdr) ==19619== by 0x809E30D: main (in /usr/bin/vdr) ==19619== ==19619== Invalid read of size 4 ==19619== at 0x4BC2E36: GLCD::cSkinObject::cSkinObject(GLCD::cSkinDisplay*) (driver.h:93) ==19619== by 0x4BE0BD3: GLCD::cSkinVariable::cSkinVariable(GLCD::cSkin*) (variable.c:19) ==19619== Address 0x10 is not stack'd, malloc'd or (recently) free'd ==19619== ==19619== ==19619== Process terminating with default action of signal 11 (SIGSEGV) ==19619== Access not within mapped region at address 0x10 ==19619== at 0x4BC2E36: GLCD::cSkinObject::cSkinObject(GLCD::cSkinDisplay*) (driver.h:93) ==19619== by 0x4BE0BD3: GLCD::cSkinVariable::cSkinVariable(GLCD::cSkin*) (variable.c:19) ==19619== If you believe this happened as a result of a stack ==19619== overflow in your program's main thread (unlikely but ==19619== possible), you can try to increase the size of the ==19619== main thread stack using the --main-stacksize= flag. ==19619== The main thread stack size used in this run was 8388608. ==19619== ==19619== HEAP SUMMARY: ==19619== in use at exit: 5,635,018 bytes in 27,500 blocks ==19619== total heap usage: 86,249 allocs, 58,749 frees, 10,010,727 bytes allocated ==19619== ==19619== LEAK SUMMARY: ==19619== definitely lost: 216 bytes in 8 blocks ==19619== indirectly lost: 20 bytes in 1 blocks ==19619== possibly lost: 50,284 bytes in 479 blocks ==19619== still reachable: 5,584,498 bytes in 27,012 blocks ==19619== suppressed: 0 bytes in 0 blocks ==19619== Rerun with --leak-check=full to see details of leaked memory ==19619== ==19619== For counts of detected and suppressed errors, rerun with: -v ==19619== ERROR SUMMARY: 13 errors from 8 contexts (suppressed: 76 from 13) Getötetmfg fuzzy
-
Just for further information, the lcd display does react when loading and with the standard logos and pnm's provided with the source. A line of blocks (approx 10 mm high) is produced at the top of the display. I have exchanged the contents from the source with the logos provided in the reel source and this produces a complete black display. Outside of this there is no further reaction.
I am now searching for how to test the lcd and find the problem with no further reaction. I also noticed in the reel sources that there is a fpctl, which includes the drivers and graphics library from graphlcd. I don't know if this is used for control of the lcd display, or only for the leds and buttons?
-
news (graphlcd-base):
- support for new generic touchscreen events provided by serdisplib; renamed class cSimpleTouchEvent to cTouchEvent
siehe auch: www.vdr-portal.de/board17-deve…port-zb-usb-mini-monitore
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!