horai

  • Content Count

    15
  • Joined

  • Last visited

About horai

  • Rank
    Member

Recent Profile Visitors

805 profile views
  1. Ok, you mean the display, that's the NOTRO driver, but I guess my note was about hardware 3D acceleration and most of the sites at the time I was trying to run it were claiming that hardware 3D acceleration is possible only with legacy kernel not with the mainline kernel. With legacy kernel, it's possible to accelerate 3D graphics and image it on ILI9431, but adding touch capability of the display was an issue for me.
  2. Ok, great, thank you very much, as soon as possible, I'll try the mainline kernel for software GPIO chip select, hopefully it will work. I hope I'll find a tutorial, how to perform it, if you have a hint how to perform it or a link, I would be very grateful if you could share it. Hopefully the display will work with the new kernel, I'll sacrifice OpenGL acceleration. Anyway, with the ads7846_device module, I noticed it's not compiled as a module for the 3.4.113 kernel, therefore I downloaded the source code from https://github.com/notro/fbtft/wiki/fbtft_device. It also has a Mak
  3. For the display there is fbtft_device loadable module which chains the fbtft module and loads it automatically (when parameters of fbtft_device set up properly) I guess the same applies to touch layer via https://github.com/notro/fbtft_tools/wiki/ads7846_device where all the parameters are specified. which probably loads the module ads7846 automatically, I guess my problem is that I have both attached to SPI0, but no CS is provided for touchscreen, data are probably mangled it it cannot register the module, but I also connected the touch layer alone as I have done
  4. I would love to use mainline kernel, but so far it will be way too much complicated for me as I have Mali400 hardware acceleration (I am not sure whether it is possible to have it on mainline kernel, some sites say yes, I even saw source code to build the driver) set up already. Moreove there is no stable release for OP Lite yet and I only need to resolve the touchscreen for me than I'll play with mainline on differend SD card.
  5. Ok, just to sum it up. The device has 2x master SPI controller and to each master there are two SPI slaves therefore we have up to 4 CS, but we have two physical pins one PIN SPI0_CS1 (pin 8) and SPI1_CS0 (pin 24) (Raspberry which has two physical PINS SPI0_CE1(CS1) and SPI0_CE0(CS0), but only one master. In case we have 4 SPI devices for Orange Pi, we place all 2 CS pins from those SPI0_CS (pin 24) and the other 2 pins to SPI1_CS (pin 8), but 0 and 1 are multiplexed. In my case where I need to connect display driver and touchscreen driver, can't I connect display driver on SPI0 and
  6. On this advertisement they also mention 2x chipselects: http://linuxgizmos.com/orange-pi-sbc-tempts-raspberry-pi-clone-fans/
  7. Ok, I was confused by a pinout image I found for Orange Pi: https://github.com/rm-hull/luma.led_matrix/issues/27 There are SPI_CE0 and SPI_CE1, but on the picture, there is only one chip select depicted, I thought that there are SPI_CE1,2 are two chip selects, I thought that maybe the other one is configurable. Could you also please explain to me one more thing? In this documentation http://dl.linux-sunxi.org/H3/Allwinner_H3_Datasheet_V1.0.pdf page 454, there is reference to SPI and there is mentioned: Four chip selects to support multiple peripheral Polarity
  8. Dear all, were any of you able to run xpt2046 touchscreen touch controller? I am struggling to resolve it, I followed many hints but now I am stuck, here is my opened topic for what I have done so far, maybe it helps someone else. Thank you very much for all the help.
  9. spi xp2046 device needs patching and recompiling even though SPI ili9341 works from scratch on the same board with spi xpt2046 which does not work? There is even a kernel driver ads7846 in kernel firmware package, I guess those are the proper externally compiled modules to the same kernel, just loadable, not packaged to the distribution due to space issues. I am a newbie so I don't see the reason why display on SPI is working and touchscreen on SPI is not working and needs a lot of extra work to be done. I opened a new topic about this here just to see what I have done so far. Thank
  10. Dear all, I would like to kindly ask you for a help. My goal is to enable touchscreen. I was able to run the display according to this connection and command: MOSI - 19, MISO - 21, SCK (SPI_CLK) - 23, CS - 24, RESET, DC and LED - 11, 13, 15. power supply and ground as usual sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:0,led:3 speed=48000000 fps=25 rotate=90 bgr=1 txbuflen=65536 I understood that the pin layout is slightly different from Raspberry Pi and I have to follow pinout table on: https://linux-sunxi.org/Xunlong_Orange_Pi_One BUT
  11. Dear all, were you able to run the display touchscreen controller? I ran modprobe ads7846, but even dmesg yields nothing and there is no more device in /dev/input/
  12. Thank you for prompt reply, I am using 5V power supply with 2.5A output, I guess this should be enough and standard HDMI cable. I am also running Raspberry on the same TV and cable with no problems even the Orange Pi works and I can work in console, I suspected Vim and X11 probably use something I am not familiar with, anyway, I'll try to use another cable, TV and power supply. All can be seen here: https://www.youtube.com/channel/UCofsIJz81fIkeltL4njHUhw I already tried h3-disp before posting this, I just want to exclude a failed unit.
  13. Dear all, Recently I purchased Orange Pi Lite. I installed recommended Armbian with Legacy 3.4.113 kernel as there is no mainline image yet. When pushing the power button a logo appears, the screen goes black and after 10 seconds command prompt with login appears with no dmesg output on screen while loading kernel image and services that all is already loaded but no output shown. So far, I am happy with it, BUT when I run Vim command to open certain file, I see it opens the file and screen dimms in few seconds to complete darkness, the only way how to get out of this blac
  14. Hello, thank you very much, I did not handle SDL properly. Now it runs super fast hardware accelerated on this small display, only text textures are missing. Anyway, it's amazing what this hardware can do. Please, if you have some other more efficient way how to run this emulator (probably without X windows), me and I guess many other people would be very greateful for posting it. Thank you very much Ivo
  15. Dear Sir, I am really excited by the capabilities of Orange Pi. I recently purchased Orange Pi Lite and wanted to reproduce running of the emulator depicted in your video, but I am really struggling to proceed any further with reasonable performance. Therefore I would like to kindly ask you for a help. I will briefly described my way. I am running Pi Lite on Armbian. I decided to compile Mupen64Plus this way: Before the standalone compilation, I installed the display according to your instructions finally obtaining /dev/fb8 as a display driver output. Then I installed Mali 400 hard