ldiaz

Hi
Im using main-line/dev version not legacy. The GPIO are those of the SPI1 interface + some extra for additional signals required. in my case gpios=dc:0,led:3,reset:1. For display only its not needed to install any overlay only notro's fbtft. In case that what to use the touch screen then you need to use a device tree overlay using with spidev and spi-add-cs1 overlays. (attached my version) For touch you need and additional CS GPIO defined in spi-add-cs1 and one more for IRQ from the touch screen. I picked "PA7".  
regards,
touch.dts

@A-P if you connect the screen to the PIZero as a Hat it sure SPI1 as SPI pins are those of this interface.  SP1 CS=0. Also DC, RST/DC seems correctly mapped.
 
The relevant part of the dmsg is this:
[ 308.268459] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 308.281149] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 308.284168] m25p80 spi0.0: spi-nor spi0.0 10000kHz 8 bits mode=0x00 [ 308.284388] fbtft_device: spi_busnum_to_master(1) returned NULL [ 308.291574] fbtft_device: failed to register SPI device [ 418.056146] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 418.058972] m25p80 spi0.0: spi-nor spi0.0 10000kHz 8 bits mode=0x00 [ 418.059177] fbtft_device: spi_busnum_to_master(1) returned NULL [ 418.066383] fbtft_device: failed to register SPI device it seems the spi_busnum=1 is not activated / registered as present. This, in principle, could be accomplished by inserting this in the armbianEnv.txt
overlays=spi-spidev param_spidev_spi_bus=1 As regards current location of drivers mine are here:
root@orangepizero:~# ls /lib/modules/4.11.5-sun8i/kernel/drivers/staging/fbtft/
fb_agm1264k-fl.ko  fb_hx8347d.ko  fb_ili9163.ko  fb_ili9340.ko fb_ili9486.ko  fb_s6d02a1.ko  fb_ssd1306.ko  fb_st7735r.ko  fb_tls8204.ko  fb_upd161704.ko  fbtft_device.ko
fb_bd663474.ko   fb_hx8353d.ko  fb_ili9320.ko  fb_ili9341.ko fb_pcd8544.ko  fb_s6d1121.ko  fb_ssd1331.ko  fb_st7789v.ko  fb_uc1611.ko   fb_watterott.ko  flexfb.ko
fb_hx8340bn.ko   fb_hx8357d.ko  fb_ili9325.ko  fb_ili9481.ko fb_ra8875.ko   fb_ssd1289.ko  fb_ssd1351.ko  fb_tinylcd.ko  fb_uc1701.ko   fbtft.ko
 
But I'm using 4.11 kernel version. It should not be relevant if the module system is propperly configured.
 
Hope It can be useful
 
 
 
 
 
 

This was my original proposal to use an overlay I posted one initial version that I wan't able to make work but I'm not a DTS expert maybe someone can simply aling it with the patch that @martinayotte created.
 
 

@A-P There is no more detail in dmesg about the error?
 
It's very strange that @glow solution to busnum=0 works as OPIZERO has no pins to connect to SPI0 bus in the GPIO header. Check this:
 

 
Busnum=1 will use the pins for SPI1: SPI1_CLK,SPI1_MISO,SPI_MOSI and SPI1_CS.
 
For other needed pins (this will depend on the screen) you need to select the GPIOS manually. Be aware of the mapping:

Check your wiring to verify it is correct with fbtft parameters. What errors are shown in dmesg?
 
For checking that thet SPI1 works well you can use the spi-dev overlay simply puting this in /boot/armbianEnv.txt:
overlays= <other overlays> spi-spidev  
param_spidev_spi_bus=1
after reboot /dev/spi*  files should be present.
 

I confirm that raschid patch worked also for me. It include botth DTS mods for opizero and the patched driver for 4.11.
May thanks for the success.  I will some perfomance test also. As regards distance to AP I think this could be improved with a better antenna. The one that come with the zero seems really low quality,
 
 
 
 

That would be even better. do you think @martinayotte will be able to do it from his private build?
 

Hi
Im using main-line/dev version not legacy. The GPIO are those of the SPI1 interface + some extra for additional signals required. in my case gpios=dc:0,led:3,reset:1. For display only its not needed to install any overlay only notro's fbtft. In case that what to use the touch screen then you need to use a device tree overlay using with spidev and spi-add-cs1 overlays. (attached my version) For touch you need and additional CS GPIO defined in spi-add-cs1 and one more for IRQ from the touch screen. I picked "PA7".  
regards,
touch.dts

I hope so.
You could try my userpatch until he does:
https://drive.google.com/file/d/0B47UwibE8mfvRXYzR0p4SGJ4Vnc/view?usp=sharing
Copy it to userpatches/kernel/sun8i-dev/
Don't forget to set KERNEL_CONFIGURE="yes" and set XRADIO to manual (m).
 

I understand Reading this thread that the driver can’t be compiled in 4.11 according to @martinayotte. However, @fifteenhex claims that it is working with the patch.
Could you clarify what is the status? I understand the decision to exclude the driver from the default build but I think it would be great to make it work as an option for custom builds. It could be a crapy driver as you all comment. But i
For those, like me, that use custom builds what is the last commit of the build tool that still use 4.10? I tried to find any tag in the master branch but I was unable to find it.
 
Thanks,