Hi,

I'm not very familiar with the cape manager, but you should get a look 
at http://www.embest-tech.com/community/index.php?topic=2845.0

I am using kernels 3.1x that do not have the cape manager, so I play with 
the dts files and rebuild a kernel each time.

I told you about the BB-View because your LCD seems to be using 24bits.
If you hookup your lcd the same way the BB-View is done, you should be able 
to get something.

Can't help more than that.


Le mardi 17 février 2015 14:33:53 UTC-5, Rahul Mahajan a écrit :
>
> HI Cedric, 
>
> Thanks for your prompt reply. 
> I am using 3.8.13-bone68 kernel.but i am not understand how to enable 
> the bb-view dts in the config files as a starting point. 
> That file not having with me. 
> Please tell me how to proceed 
>
> thanks 
>
> On Mon, Feb 16, 2015 at 11:07 PM, Cedric Malitte 
> <[email protected] <javascript:>> wrote: 
> > Hi, 
> > 
> > you should look at this 
> > 
> http://www.element14.com/community/servlet/JiveServlet/previewBody/65082-102-5-294046/BB%20VIEW%20User%20Manual%20V3.pdf
>  
> > 
> > This is also a 24bit rgb lcd panel. 
> > 
> > If you want to enable your panel in linux, it will depend on your kernel 
> > version. 
> > If you have the 3.8.13, the one that came on the BBB , you will just 
> have to 
> > enalbe the bb-view dts in the config files as a starting point. 
> > 
> > For other kernels, I think bb-view is enabled at some point, but I'm not 
> > using those displays. 
> > I use the 4D systems cape displays because they are 16 bits, so it saves 
> me 
> > a few pins on the BBB. 
> > 
> > Regards. 
> > 
> > 
> > 2015-02-16 7:40 GMT-05:00 <[email protected] <javascript:>>: 
> > 
> >> Hi Cedric, 
> >> 
> >> can you tell me how your applying patch i am new to device tree. 
> >> can you tell me i am using this LCD paneel 
> >> 
> >> 
> http://www.aliexpress.com/store/product/4-3-inch-40PIN-TFT-LCD-Screen-with-Touch-Panel-OTA5180A-Drive-IC-480-272-RGB/224898_1899445212.html
>  
> >> but its not working as per this i changes in .dts file 
> >> but LCD is not working. 
> >> 
> >> Please give me details. 
> >> 
> >> thanks 
> >> 
> >> On Saturday, August 2, 2014 at 12:20:24 PM UTC+5:30, Cedric Malitte 
> wrote: 
> >>> 
> >>> Hi, 
> >>> 
> >>> I compiled the 3.13 and 3.15 kernel using Robert tools, and I saw this 
> >>> hoping to get LCD4 cape support: 
> >>> http://www.spinics.net/lists/linux-omap/msg109735.html 
> >>> 
> >>> I applied the patch against the kernel tree, but nothing happened at 
> boot 
> >>> after a rebuild, I mean screen stayed black. 
> >>> 
> >>> A quick look in the kernel tree dirs and the 
> am335x-bone-display-cape.dts 
> >>> has not been compiled. 
> >>> So I tried to ass it to Makefile, rebuild and got a fatal error from 
> DTC. 
> >>> 
> >>> I'm not very used to DT, so if someone could have a look at this file 
> and 
> >>> tell me what can be wrong, I'll try to rebuild it. 
> >>> 
> >>> /* 
> >>>  * Copyright (C) 2014 Texas Instruments Incorporated - 
> http://www.ti.com/ 
> >>>  * 
> >>>  * This program is free software; you can redistribute it and/or 
> modify 
> >>>  * it under the terms of the GNU General Public License version 2 as 
> >>>  * published by the Free Software Foundation. 
> >>>  * 
> >>>  * This DTS adds supports for display capes using LCD interface for 
> >>> display 
> >>>  * and GPIO or PWM interface for backlight controls. 
> >>>  */ 
> >>> &am33xx_pinmux { 
> >>> bbcape_backlight_pins: bbcape_backlight_pins { 
> >>> pinctrl-single,pins = < 
> >>> 0x48  (PIN_OUTPUT | MUX_MODE7) /* gpmc_a[2].GPIO1[18] (backlight 
> control) 
> >>> */ 
> >>> >; 
> >>> }; 
> >>> bbcape_lcd_pins: bbcape_lcd_pins { 
> >>> pinctrl-single,pins = < 
> >>> 0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */ 
> >>> 0xa4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */ 
> >>> 0xa8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data2.lcd_data2 */ 
> >>> 0xac (PIN_OUTPUT | MUX_MODE0) /* lcd_data3.lcd_data3 */ 
> >>> 0xb0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data4.lcd_data4 */ 
> >>> 0xb4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data5.lcd_data5 */ 
> >>> 0xb8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data6.lcd_data6 */ 
> >>> 0xbc (PIN_OUTPUT | MUX_MODE0) /* lcd_data7.lcd_data7 */ 
> >>> 0xc0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data8.lcd_data8 */ 
> >>> 0xc4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data9.lcd_data9 */ 
> >>> 0xc8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data10.lcd_data10 */ 
> >>> 0xcc (PIN_OUTPUT | MUX_MODE0) /* lcd_data11.lcd_data11 */ 
> >>> 0xd0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data12.lcd_data12 */ 
> >>> 0xd4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data13.lcd_data13 */ 
> >>> 0xd8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data14.lcd_data14 */ 
> >>> 0xdc (PIN_OUTPUT | MUX_MODE0) /* lcd_data15.lcd_data15 */ 
> >>> 0xe0 (PIN_OUTPUT | MUX_MODE0) /* lcd_vsync.lcd_vsync */ 
> >>> 0xe4 (PIN_OUTPUT | MUX_MODE0) /* lcd_hsync.lcd_hsync */ 
> >>> 0xe8 (PIN_OUTPUT | MUX_MODE0) /* lcd_pclk.lcd_pclk */ 
> >>> 0xec (PIN_OUTPUT | MUX_MODE0) /* lcd_ac_bias_en.lcd_ac_bias_en 
> (lcd_en) 
> >>> */ 
> >>> 0x1a4 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* mcasp0_fsr.gpio3[19] 
> (lcd_disen) 
> >>> */ 
> >>> >; 
> >>> }; 
> >>> bbcape_touchscreen_pins: bbcape_touchscreen_pins { 
> >>> pinctrl-single,pins = < 
> >>> 0x184 (PIN_INPUT_PULLDOWN | MUX_MODE7) /* uart1_txd.gpio0[15] (enter) 
> */ 
> >>> 0x40  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a0.gpio1[16] (left) */ 
> >>> 0x44  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a1.gpio1[17] (right) */ 
> >>> 0x4c  (PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a3.gpio1[19] (up) */ 
> >>> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE7) /* mcasp0_axr0.gpio3[16] (down) 
> */ 
> >>> >; 
> >>> }; 
> >>> }; 
> >>> 
> >>> / { 
> >>> backlight { 
> >>> status = "okay"; 
> >>> compatible = "gpio-backlight"; 
> >>> pinctrl-names = "default"; 
> >>> pinctrl-0 = <&bbcape_backlight_pins>; 
> >>> gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>; 
> >>> default-on; 
> >>> }; 
> >>> panel { 
> >>> status = "okay"; 
> >>> compatible = "ti,tilcdc,panel"; 
> >>> pinctrl-names = "default"; 
> >>> pinctrl-0 = <&bbcape_lcd_pins>; 
> >>> panel-info { 
> >>> ac-bias           = <255>; 
> >>> ac-bias-intrpt    = <0>; 
> >>> dma-burst-sz      = <16>; 
> >>> bpp               = <16>; 
> >>> fdd               = <0x80>; 
> >>> sync-edge         = <0>; 
> >>> sync-ctrl         = <1>; 
> >>> raster-order      = <0>; 
> >>> fifo-th           = <0>; 
> >>> }; 
> >>> display-timings { 
> >>> native-mode = <&timing0>; 
> >>> /* www.newhavendisplay.com/app_notes/OTA5180A.pdf */ 
> >>> timing0: 480x272 { 
> >>> clock-frequency = <9200000>; 
> >>> hactive = <480>; 
> >>> vactive = <272>; 
> >>> hfront-porch = <8>; 
> >>> hback-porch = <47>; 
> >>> hsync-len = <41>; 
> >>> vback-porch = <2>; 
> >>> vfront-porch = <3>; 
> >>> vsync-len = <10>; 
> >>> hsync-active = <0>; 
> >>> vsync-active = <0>; 
> >>> de-active = <1>; 
> >>> pixelclk-active = <0>; 
> >>> }; 
> >>> }; 
> >>> }; 
> >>> }; 
> >>> 
> >>> 
> >>> Thanks 
> >>> 
> >>> Cedric. 
> >> 
> >> -- 
> >> For more options, visit http://beagleboard.org/discuss 
> >> --- 
> >> You received this message because you are subscribed to a topic in the 
> >> Google Groups "BeagleBoard" group. 
> >> To unsubscribe from this topic, visit 
> >> https://groups.google.com/d/topic/beagleboard/wAcTyHqLfwg/unsubscribe. 
> >> To unsubscribe from this group and all its topics, send an email to 
> >> [email protected] <javascript:>. 
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > For more options, visit http://beagleboard.org/discuss 
> > --- 
> > You received this message because you are subscribed to a topic in the 
> > Google Groups "BeagleBoard" group. 
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/beagleboard/wAcTyHqLfwg/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> > [email protected] <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to