* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-12 0:02 Peter Seiderer
2015-01-12 4:55 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Peter Seiderer @ 2015-01-12 0:02 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Sun, Jan 11, 2015 at 03:23:09PM -0600, Lou Crittenden wrote:
> >Please do the following:
> >$ cd build_rpi_001
> >$ grep -E "^CONFIG_SPI|^CONFIG_GPIO|^
> >CONFIG_FB" build/linux-c256eb9968c8997dce47350d2075e4>2f1b3991d3/.config
>
> >Please send your output...
> The output of the command is located in the attachment named "output of
> grep -E "^CONFIG_SPi"
>
CONFIG_SPI=y
CONFIG_SPI_MASTER=y
CONFIG_SPI_BCM2708=m
CONFIG_SPI_SPIDEV=y
CONFIG_GPIO_DEVRES=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_SYSFS=y
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
CONFIG_FB_SYS_FOPS=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_BCM2708=y
CONFIG_FB_TFT=y
CONFIG_FB_TFT_ILI9340=m
CONFIG_FB_FLEX=m
CONFIG_FB_TFT_FBTFT_DEVICE=y
Looks good until 'CONFIG_FB_TFT_FBTFT_DEVICE=y', please change to 'CONFIG_FB_TFT_FBTFT_DEVICE=m'
(best done with make linux-menuconfig from buildroot, will trigger the right rebuild on
next make command).
The problem is with 'y' fbtft_device is bulltin and configuration hase to be done via kernel
commandline. If compiled as module fbtft_device.ko configuration can be done at module loading
time...
> the output of the command "find target/lib/modules" is located in the
> attachment "output_of_find"
>
Looks good, beside the misssing fbtft_device.ko (see above)...
> the output of the following commands are in the named attachments:
> lsmod: lsmod
>
> cat /proc/cmdline: no output. Also checked that directory, and it didn't
> contain anything.
>
> cat /etc/modules-load.d/fbtft.conf: fbtft.conf
>
Looks good...
> cat /etc/modprobe.d/00-fbtft.conf: 00-fbtft.conf
Looks good...
>
> find /lib/modules: findlibmodules
>
Looks good, beside the misssing fbtft_device.ko (see above)...
> insmod fbtft_device name=waveshare32b: I get "insmod: ERROR: could not load
> module fbtft_device: no such file or directory"
Sorry, shoold have been:
$ insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko name=waveshare32b
And should work when fbtft_device.ko module is build and copied to target....
>
> dmesg: dmesg
>
[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480
+bcm2708.boardrev=0x10 bcm2708.serial=0xd81a36af smsc95xx.macaddr=B8:27:EB:1A:36:AF bcm2708.disk_led_gpio=47
+bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000
+vc_mem.mem_size=0x20000000 dwc_otg.fiq_fix_enable=1 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0
+console=tty1 root=/dev/mmcblk0p2 rootwait
The following is missing 'fbcon=map:10 fbcon=font:VGA8x8', needed for automatic console output on the
new display (after fbtft_device.ko is laoded successul), add to cmdline.txt if you want this feature...
> ls -l /dev/fb*: dev_fb*
O.k., no fbtft_device.ko loaded, no second /dev/fb1 device entry....
Hope for more success after fbtft_device modules is enabled ;-)
Regards,
Peter
>
> ---------- Forwarded message ----------
> From: Peter Seiderer <ps.report@gmx.net>
> Date: Sun, Jan 11, 2015 at 8:04 AM
> Subject: Re: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> extension
> To: Lou Crittenden <loucrittenden63@gmail.com>
> Cc: buildroot at busybox.net
>
>
> Hello Lou,
>
> On Sat, Jan 10, 2015 at 08:00:15PM -0600, Lou Crittenden wrote:
> > Thanks for this info. I have some questions to ask:
> >
> > I saw that you have updated your patch. What did you do to it?
> >
>
> The downloaded patch via the described command:
>
> $ wget -O v3-linux-add-fbtft-kernel-extension.patch
> https://patchwork.ozlabs.org/patch/425126/mbox/
>
> was already my latest patch (Thomas did some changes on the committed
> patch, but
> introduced a bug, see [1][2]), but the downloaded one is good ;-).
>
> > Did you have to manually create the /etc/modules-load.d and
> /etc/modprobe.d
> > folders and the text files you named in your setup? Mine didn't have
> those.
> > I manually made the directories and text files as laid out but the device
> > still didn't work.
>
> Yes you have to create this two files with the described content (thats why
> I
> wrote 'add', otherwiese it would be 'change' ;-) ).
>
> But I do this advice 'blindly' because I own a different display device...
>
> >
> > How did you build the fbtft drivers in your menuconfig: as add-on modules
> > (with the option asterisked) or built-in (with the option checkmarked)?
> >
>
> I did enable the 'linux-menuconfig' SPI configs with 'y'/'*' (built in)
> and the FB_TFT ones with 'm'/'M' (modules)...
>
> Please do the following:
> $ cd build_rpi_001
> $ grep -E "^CONFIG_SPI|^CONFIG_GPIO|^CONFIG_FB"
> build/linux-c256eb9968c8997dce47350d2075e42f1b3991d3/.config
>
> Output should be like the following:
> CONFIG_SPI=y
> CONFIG_SPI_MASTER=y
> CONFIG_SPI_BCM2708=y
> CONFIG_GPIO_DEVRES=y
> CONFIG_GPIOLIB=y
> CONFIG_FB=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_SYS_FILLRECT=y
> CONFIG_FB_SYS_COPYAREA=y
> CONFIG_FB_SYS_IMAGEBLIT=y
> CONFIG_FB_SYS_FOPS=y
> CONFIG_FB_DEFERRED_IO=y
> CONFIG_FB_BACKLIGHT=y
> CONFIG_FB_BCM2708=y
> CONFIG_FB_TFT=y
> CONFIG_FB_TFT_ILI9340=m
> CONFIG_FB_TFT_FBTFT_DEVICE=m
>
> Please send your output...
>
> > I couldn't find a "waveshare32b" model in any driver list, so I'm using
> the
> > "flexfb" module that my factory image uses. Still no go.
>
> There is now waveshare32b module, only the fbtft_device module (a helper
> module for
> the various displays). If you load btft_device by hand,e.g.:
>
> $ insmod fbtft_device name=waveshare32b
>
> you give your display type via the module parameter 'name=waveshare32b'
>
> >
> > What I've done thus far:
> > I used lsmod on the flexfb.ko, and while the command goes through fine
> > without error, but nothing happens with the display (what am I missing
> > parameters wise?). I then ran dd if=/dev/urandom of=/dev/fb1. Nothing.
>
> flexfb is the 'old' universal module, you have to give a lot of parameters
> for your device, the way via fbtft_device is a shortcut/helper for this
> (and added recently to fbtft for your device [3]), see file
> build/linux-c256eb9968c8997dce47350d2075e42f1b3991d3/drivers/video/fbtft/fbtft_device.c:
>
> 1012 }, {
> 1013 .name = "waveshare32b",
> 1014 .spi = &(struct spi_board_info) {
> 1015 .modalias = "fb_ili9340",
> 1016 .max_speed_hz = 48000000,
> 1017 .mode = SPI_MODE_0,
> 1018 .platform_data = &(struct fbtft_platform_data)
> {
> 1019 .display = {
> 1020 .buswidth = 8,
> 1021 .backlight = 1,
> 1022 .init_sequence =
> waveshare32b_init_sequence,
> 1023 },
> 1024 .bgr = true,
> 1025 .gpios = (const struct fbtft_gpio []) {
> 1026 { "reset", 27 },
> 1027 { "dc", 22 },
> 1028 {},
> 1029 },
> 1030 }
> 1031 }
> 1032 }, {
>
> >
> > I ran insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/ili9340.ko.
> It
> > complains "cannot load module: no such file or directory" even if I use an
> > absolute path where "ili9340.ko" is located.
> >
>
> The module should be named 'fb_ili9340.ko'
>
> >
> > I have my buildroot .config file in the attachments if you wish to take a
> > look at my setup to compare and maybe edit/reupload.
> >
>
> The buildroot .config is o.k., both options are enabled:
> BR2_LINUX_KERNEL_EXT_FBTFT=y
> BR2_PACKAGE_FBTFT=y
>
> One more try for remote debugging, please send the output of the
> following commands from your buildroot build directory:
>
> $ cd build_rpi_001
> $ grep -E "^CONFIG_SPI|^CONFIG_GPIO|^CONFIG_FB"
> build/linux-c256eb9968c8997dce47350d2075e42f1b3991d3/.config
> $ find target/lib/modules
>
> And the output from the following commands from your Raspberry Pi device:
>
> $ lsmod
> $ cat /proc/cmdline
> $ cat /etc/modules-load.d/fbtft.conf
> $ cat /etc/modprobe.d/00-fbtft.conf
> $ find /lib/modules
> $ insmod fbtft_device name=waveshare32b
> $ dmesg
> $ ls -l /dev/fb*
>
> Regards,
> Peter
>
> [1] http://lists.busybox.net/pipermail/buildroot/2015-January/117057.html
> [2] http://lists.busybox.net/pipermail/buildroot/2015-January/117062.html
> [3]
> https://github.com/notro/fbtft/commit/e67014490a9df34b9a4bf04e49c50254aebc10a8
>
>
> > ---------- Forwarded message ----------
> > From: Peter Seiderer <ps.report@gmx.net>
> > Date: Wed, Jan 7, 2015 at 8:12 AM
> > Subject: Aw: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> > extension
> > To: Lou Crittenden <loucrittenden63@gmail.com>
> > Cc: buildroot at busybox.net
> >
> >
> > Hello Lou,
> >
> > > Gesendet: Mittwoch, 07. Januar 2015 um 14:06 Uhr
> > > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
> > > An: buildroot at busybox.net, "Peter Seiderer" <ps.report@gmx.net>
> > > Betreff: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> > extension
> > >
> > > Alright, I have the buildroot built and a resultant bootable system, but
> > the screen doesn't initialize. Did you have to
> > > create an /etc/modules file and the corresponding /etc/init.d script to
> > load the modules/drivers at boot or something?
> > >
> >
> > Sorry, forgot to mention this part in my 'instruction' e-mail (but a
> > description was already included in [1]).
> >
> > For your case the following configuration changes should be needed:
> >
> > On the sd-card boot partition:
> > - cmdline.txt: add 'fbcon=map:10 fbcon=font:VGA8x8'
> >
> > On the sd-card root partition:
> > - add /etc/modules-load.d/fbtft.conf with 'fbtft_device'
> > - add /etc/modprobe.d/00-fbtft.conf with 'options fbtft_device
> > name=waveshare32b'
> >
> > If this works for you its fine, if not try to load the fbtft_device module
> > via
> > insmod and play with the module parameters....and take a look at the
> > dmesg commnd output....on success a second frame buffer device /dev/fb1
> > should
> > be available (/dev/fb0 is the hdmi output)...
> >
> > $ dd if=/dev/urandom of=/dev/fb1
> >
> > should fill your waveshare device with random snow...
> >
> > Or take a look at [2] and [3], seems similare displays...
> >
> > Regards,
> > Peter
> >
> >
> > [1] http://lists.busybox.net/pipermail/buildroot/2014-December/116096.html
> > [2] https://github.com/notro/rpi-firmware/issues/6
> > [3]https://github.com/notro/fbtft/issues/215
> >
> > >
> > > ---------- Forwarded message ----------
> > > From: Lou Crittenden <loucrittenden63@gmail.com>
> > > Date: Mon, Jan 5, 2015 at 5:03 PM
> > > Subject: Re: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> extension
> > > To: Peter Seiderer <ps.report at gmx.net[ps.report@gmx.net]>,
> > buildroot at busybox.net[buildroot at busybox.net]
> > >
> > >
> > > Yes, I'm using a waveshare32b. I bought it from here:
> > http://www.ebay.com/itm/331320440420[http://www.ebay.com/itm/331320440420]
> > >
> > > I didn't know this was an ili9340 device. I've tried looking up the
> > controller type, but it's been difficult, as they are a
> > > little sketchy. I was able to enable this screen in raspbmc through the
> > use of the "flexfb" driver, as the factory raspbian
> > > image also uses this driver. The touchscreen controller is an ads7846.
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 0:02 [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension Peter Seiderer
@ 2015-01-12 4:55 ` Lou Crittenden
2015-01-12 7:29 ` Peter Seiderer
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-12 4:55 UTC (permalink / raw)
To: buildroot
Good news! The screen works, however the orientation is portrait instead of
landscape and I'd like it to be landscape. Also, how do I make this driver
load on boot so I do not have to keep loading "insmod
/lib/modules/3.12.28/kernel/
drivers/video/fbtft/fbtft_device.ko name=waveshare32b" every time, so I can
have this screen be the default? I also want to load the ads7846
touchscreen driver as well for touchscreen.
Again, thanks a bunch.
On Sun, Jan 11, 2015 at 6:02 PM, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Lou,
>
> On Sun, Jan 11, 2015 at 03:23:09PM -0600, Lou Crittenden wrote:
> > >Please do the following:
> > >$ cd build_rpi_001
> > >$ grep -E "^CONFIG_SPI|^CONFIG_GPIO|^
> > >CONFIG_FB" build/linux-c256eb9968c8997dce47350d2075e4>2f1b3991d3/.config
> >
> > >Please send your output...
> > The output of the command is located in the attachment named "output of
> > grep -E "^CONFIG_SPi"
> >
>
> CONFIG_SPI=y
> CONFIG_SPI_MASTER=y
> CONFIG_SPI_BCM2708=m
> CONFIG_SPI_SPIDEV=y
> CONFIG_GPIO_DEVRES=y
> CONFIG_GPIOLIB=y
> CONFIG_GPIO_SYSFS=y
> CONFIG_FB=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_SYS_FILLRECT=y
> CONFIG_FB_SYS_COPYAREA=y
> CONFIG_FB_SYS_IMAGEBLIT=y
> CONFIG_FB_SYS_FOPS=y
> CONFIG_FB_DEFERRED_IO=y
> CONFIG_FB_BACKLIGHT=y
> CONFIG_FB_BCM2708=y
> CONFIG_FB_TFT=y
> CONFIG_FB_TFT_ILI9340=m
> CONFIG_FB_FLEX=m
> CONFIG_FB_TFT_FBTFT_DEVICE=y
>
> Looks good until 'CONFIG_FB_TFT_FBTFT_DEVICE=y', please change to
> 'CONFIG_FB_TFT_FBTFT_DEVICE=m'
> (best done with make linux-menuconfig from buildroot, will trigger the
> right rebuild on
> next make command).
>
> The problem is with 'y' fbtft_device is bulltin and configuration hase to
> be done via kernel
> commandline. If compiled as module fbtft_device.ko configuration can be
> done at module loading
> time...
>
> > the output of the command "find target/lib/modules" is located in the
> > attachment "output_of_find"
> >
>
> Looks good, beside the misssing fbtft_device.ko (see above)...
>
> > the output of the following commands are in the named attachments:
> > lsmod: lsmod
> >
> > cat /proc/cmdline: no output. Also checked that directory, and it didn't
> > contain anything.
> >
> > cat /etc/modules-load.d/fbtft.conf: fbtft.conf
> >
>
> Looks good...
>
> > cat /etc/modprobe.d/00-fbtft.conf: 00-fbtft.conf
>
> Looks good...
>
> >
> > find /lib/modules: findlibmodules
> >
>
> Looks good, beside the misssing fbtft_device.ko (see above)...
>
> > insmod fbtft_device name=waveshare32b: I get "insmod: ERROR: could not
> load
> > module fbtft_device: no such file or directory"
>
> Sorry, shoold have been:
>
> $ insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> name=waveshare32b
>
> And should work when fbtft_device.ko module is build and copied to
> target....
>
> >
> > dmesg: dmesg
> >
>
> [ 0.000000] Kernel command line: dma.dmachans=0x7f35
> bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480
> +bcm2708.boardrev=0x10 bcm2708.serial=0xd81a36af
> smsc95xx.macaddr=B8:27:EB:1A:36:AF bcm2708.disk_led_gpio=47
> +bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000
> vc_mem.mem_base=0x1ec00000
> +vc_mem.mem_size=0x20000000 dwc_otg.fiq_fix_enable=1
> sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0
> +console=tty1 root=/dev/mmcblk0p2 rootwait
>
> The following is missing 'fbcon=map:10 fbcon=font:VGA8x8', needed for
> automatic console output on the
> new display (after fbtft_device.ko is laoded successul), add to
> cmdline.txt if you want this feature...
>
> > ls -l /dev/fb*: dev_fb*
>
> O.k., no fbtft_device.ko loaded, no second /dev/fb1 device entry....
>
> Hope for more success after fbtft_device modules is enabled ;-)
>
> Regards,
> Peter
>
> >
> > ---------- Forwarded message ----------
> > From: Peter Seiderer <ps.report@gmx.net>
> > Date: Sun, Jan 11, 2015 at 8:04 AM
> > Subject: Re: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft
> kernel
> > extension
> > To: Lou Crittenden <loucrittenden63@gmail.com>
> > Cc: buildroot at busybox.net
> >
> >
> > Hello Lou,
> >
> > On Sat, Jan 10, 2015 at 08:00:15PM -0600, Lou Crittenden wrote:
> > > Thanks for this info. I have some questions to ask:
> > >
> > > I saw that you have updated your patch. What did you do to it?
> > >
> >
> > The downloaded patch via the described command:
> >
> > $ wget -O v3-linux-add-fbtft-kernel-extension.patch
> > https://patchwork.ozlabs.org/patch/425126/mbox/
> >
> > was already my latest patch (Thomas did some changes on the committed
> > patch, but
> > introduced a bug, see [1][2]), but the downloaded one is good ;-).
> >
> > > Did you have to manually create the /etc/modules-load.d and
> > /etc/modprobe.d
> > > folders and the text files you named in your setup? Mine didn't have
> > those.
> > > I manually made the directories and text files as laid out but the
> device
> > > still didn't work.
> >
> > Yes you have to create this two files with the described content (thats
> why
> > I
> > wrote 'add', otherwiese it would be 'change' ;-) ).
> >
> > But I do this advice 'blindly' because I own a different display
> device...
> >
> > >
> > > How did you build the fbtft drivers in your menuconfig: as add-on
> modules
> > > (with the option asterisked) or built-in (with the option checkmarked)?
> > >
> >
> > I did enable the 'linux-menuconfig' SPI configs with 'y'/'*' (built in)
> > and the FB_TFT ones with 'm'/'M' (modules)...
> >
> > Please do the following:
> > $ cd build_rpi_001
> > $ grep -E "^CONFIG_SPI|^CONFIG_GPIO|^CONFIG_FB"
> > build/linux-c256eb9968c8997dce47350d2075e42f1b3991d3/.config
> >
> > Output should be like the following:
> > CONFIG_SPI=y
> > CONFIG_SPI_MASTER=y
> > CONFIG_SPI_BCM2708=y
> > CONFIG_GPIO_DEVRES=y
> > CONFIG_GPIOLIB=y
> > CONFIG_FB=y
> > CONFIG_FB_CFB_FILLRECT=y
> > CONFIG_FB_CFB_COPYAREA=y
> > CONFIG_FB_CFB_IMAGEBLIT=y
> > CONFIG_FB_SYS_FILLRECT=y
> > CONFIG_FB_SYS_COPYAREA=y
> > CONFIG_FB_SYS_IMAGEBLIT=y
> > CONFIG_FB_SYS_FOPS=y
> > CONFIG_FB_DEFERRED_IO=y
> > CONFIG_FB_BACKLIGHT=y
> > CONFIG_FB_BCM2708=y
> > CONFIG_FB_TFT=y
> > CONFIG_FB_TFT_ILI9340=m
> > CONFIG_FB_TFT_FBTFT_DEVICE=m
> >
> > Please send your output...
> >
> > > I couldn't find a "waveshare32b" model in any driver list, so I'm using
> > the
> > > "flexfb" module that my factory image uses. Still no go.
> >
> > There is now waveshare32b module, only the fbtft_device module (a helper
> > module for
> > the various displays). If you load btft_device by hand,e.g.:
> >
> > $ insmod fbtft_device name=waveshare32b
> >
> > you give your display type via the module parameter 'name=waveshare32b'
> >
> > >
> > > What I've done thus far:
> > > I used lsmod on the flexfb.ko, and while the command goes through fine
> > > without error, but nothing happens with the display (what am I missing
> > > parameters wise?). I then ran dd if=/dev/urandom of=/dev/fb1. Nothing.
> >
> > flexfb is the 'old' universal module, you have to give a lot of
> parameters
> > for your device, the way via fbtft_device is a shortcut/helper for this
> > (and added recently to fbtft for your device [3]), see file
> >
> build/linux-c256eb9968c8997dce47350d2075e42f1b3991d3/drivers/video/fbtft/fbtft_device.c:
> >
> > 1012 }, {
> > 1013 .name = "waveshare32b",
> > 1014 .spi = &(struct spi_board_info) {
> > 1015 .modalias = "fb_ili9340",
> > 1016 .max_speed_hz = 48000000,
> > 1017 .mode = SPI_MODE_0,
> > 1018 .platform_data = &(struct
> fbtft_platform_data)
> > {
> > 1019 .display = {
> > 1020 .buswidth = 8,
> > 1021 .backlight = 1,
> > 1022 .init_sequence =
> > waveshare32b_init_sequence,
> > 1023 },
> > 1024 .bgr = true,
> > 1025 .gpios = (const struct fbtft_gpio
> []) {
> > 1026 { "reset", 27 },
> > 1027 { "dc", 22 },
> > 1028 {},
> > 1029 },
> > 1030 }
> > 1031 }
> > 1032 }, {
> >
> > >
> > > I ran insmod
> /lib/modules/3.12.28/kernel/drivers/video/fbtft/ili9340.ko.
> > It
> > > complains "cannot load module: no such file or directory" even if I
> use an
> > > absolute path where "ili9340.ko" is located.
> > >
> >
> > The module should be named 'fb_ili9340.ko'
> >
> > >
> > > I have my buildroot .config file in the attachments if you wish to
> take a
> > > look at my setup to compare and maybe edit/reupload.
> > >
> >
> > The buildroot .config is o.k., both options are enabled:
> > BR2_LINUX_KERNEL_EXT_FBTFT=y
> > BR2_PACKAGE_FBTFT=y
> >
> > One more try for remote debugging, please send the output of the
> > following commands from your buildroot build directory:
> >
> > $ cd build_rpi_001
> > $ grep -E "^CONFIG_SPI|^CONFIG_GPIO|^CONFIG_FB"
> > build/linux-c256eb9968c8997dce47350d2075e42f1b3991d3/.config
> > $ find target/lib/modules
> >
> > And the output from the following commands from your Raspberry Pi device:
> >
> > $ lsmod
> > $ cat /proc/cmdline
> > $ cat /etc/modules-load.d/fbtft.conf
> > $ cat /etc/modprobe.d/00-fbtft.conf
> > $ find /lib/modules
> > $ insmod fbtft_device name=waveshare32b
> > $ dmesg
> > $ ls -l /dev/fb*
> >
> > Regards,
> > Peter
> >
> > [1]
> http://lists.busybox.net/pipermail/buildroot/2015-January/117057.html
> > [2]
> http://lists.busybox.net/pipermail/buildroot/2015-January/117062.html
> > [3]
> >
> https://github.com/notro/fbtft/commit/e67014490a9df34b9a4bf04e49c50254aebc10a8
> >
> >
> > > ---------- Forwarded message ----------
> > > From: Peter Seiderer <ps.report@gmx.net>
> > > Date: Wed, Jan 7, 2015 at 8:12 AM
> > > Subject: Aw: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> > > extension
> > > To: Lou Crittenden <loucrittenden63@gmail.com>
> > > Cc: buildroot at busybox.net
> > >
> > >
> > > Hello Lou,
> > >
> > > > Gesendet: Mittwoch, 07. Januar 2015 um 14:06 Uhr
> > > > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
> > > > An: buildroot at busybox.net, "Peter Seiderer" <ps.report@gmx.net>
> > > > Betreff: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> > > extension
> > > >
> > > > Alright, I have the buildroot built and a resultant bootable system,
> but
> > > the screen doesn't initialize. Did you have to
> > > > create an /etc/modules file and the corresponding /etc/init.d script
> to
> > > load the modules/drivers at boot or something?
> > > >
> > >
> > > Sorry, forgot to mention this part in my 'instruction' e-mail (but a
> > > description was already included in [1]).
> > >
> > > For your case the following configuration changes should be needed:
> > >
> > > On the sd-card boot partition:
> > > - cmdline.txt: add 'fbcon=map:10 fbcon=font:VGA8x8'
> > >
> > > On the sd-card root partition:
> > > - add /etc/modules-load.d/fbtft.conf with 'fbtft_device'
> > > - add /etc/modprobe.d/00-fbtft.conf with 'options fbtft_device
> > > name=waveshare32b'
> > >
> > > If this works for you its fine, if not try to load the fbtft_device
> module
> > > via
> > > insmod and play with the module parameters....and take a look at the
> > > dmesg commnd output....on success a second frame buffer device /dev/fb1
> > > should
> > > be available (/dev/fb0 is the hdmi output)...
> > >
> > > $ dd if=/dev/urandom of=/dev/fb1
> > >
> > > should fill your waveshare device with random snow...
> > >
> > > Or take a look at [2] and [3], seems similare displays...
> > >
> > > Regards,
> > > Peter
> > >
> > >
> > > [1]
> http://lists.busybox.net/pipermail/buildroot/2014-December/116096.html
> > > [2] https://github.com/notro/rpi-firmware/issues/6
> > > [3]https://github.com/notro/fbtft/issues/215
> > >
> > > >
> > > > ---------- Forwarded message ----------
> > > > From: Lou Crittenden <loucrittenden63@gmail.com>
> > > > Date: Mon, Jan 5, 2015 at 5:03 PM
> > > > Subject: Re: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel
> > extension
> > > > To: Peter Seiderer <ps.report at gmx.net[ps.report@gmx.net]>,
> > > buildroot at busybox.net[buildroot at busybox.net]
> > > >
> > > >
> > > > Yes, I'm using a waveshare32b. I bought it from here:
> > >
> http://www.ebay.com/itm/331320440420[http://www.ebay.com/itm/331320440420]
> > > >
> > > > I didn't know this was an ili9340 device. I've tried looking up the
> > > controller type, but it's been difficult, as they are a
> > > > little sketchy. I was able to enable this screen in raspbmc through
> the
> > > use of the "flexfb" driver, as the factory raspbian
> > > > image also uses this driver. The touchscreen controller is an
> ads7846.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150111/599114ff/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 4:55 ` Lou Crittenden
@ 2015-01-12 7:29 ` Peter Seiderer
2015-01-12 7:39 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Peter Seiderer @ 2015-01-12 7:29 UTC (permalink / raw)
To: buildroot
Hello Lou,
> Gesendet:?Montag, 12. Januar 2015 um 05:55 Uhr
> Von:?"Lou Crittenden" <loucrittenden63@gmail.com>
> An:?"Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
> Betreff:?Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft kernel extension
>
> Good news! The screen works, however the orientation is portrait instead of landscape and I'd
> like it to be landscape. Also, how do I make this driver load on boot so I do not have to
> keep loading "insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko name=waveshare32b"
> every time, so I can have this screen be the default? I also want to load the ads7846
> touchscreen driver as well for touchscreen.
The rotation part is the easy one, try
$ insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko name=waveshare32b rotation=90
The automatic loading should work with the /etc/modules-load.d/fbtft.conf and /etc/modprobe.d/00-fbtft.conf
entries (do not forget to add rotation=90 to 00-fbtft-conf), but I have to take a closer look at your
buildroot config whats missing or is different from my one, needs some time ;-)
For the touchscreen try [1]...
> Again, thanks a bunch.
Your welcome,
Peter
[1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 7:29 ` Peter Seiderer
@ 2015-01-12 7:39 ` Lou Crittenden
2015-01-12 7:48 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-12 7:39 UTC (permalink / raw)
To: buildroot
Here's my latest buildroot config for your consideration. At least we know
it works.
On Mon, Jan 12, 2015 at 1:29 AM, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Lou,
>
> > Gesendet: Montag, 12. Januar 2015 um 05:55 Uhr
> > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
> > An: "Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
> > Betreff: Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add fbtft
> kernel extension
> >
> > Good news! The screen works, however the orientation is portrait instead
> of landscape and I'd
> > like it to be landscape. Also, how do I make this driver load on boot so
> I do not have to
> > keep loading "insmod
> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> name=waveshare32b"
> > every time, so I can have this screen be the default? I also want to
> load the ads7846
> > touchscreen driver as well for touchscreen.
>
> The rotation part is the easy one, try
>
> $ insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> name=waveshare32b rotation=90
>
> The automatic loading should work with the /etc/modules-load.d/fbtft.conf
> and /etc/modprobe.d/00-fbtft.conf
> entries (do not forget to add rotation=90 to 00-fbtft-conf), but I have to
> take a closer look at your
> buildroot config whats missing or is different from my one, needs some
> time ;-)
>
> For the touchscreen try [1]...
>
> > Again, thanks a bunch.
>
> Your welcome,
> Peter
>
> [1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150112/d81811f4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 79732 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150112/d81811f4/attachment-0001.obj>
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 7:39 ` Lou Crittenden
@ 2015-01-12 7:48 ` Lou Crittenden
0 siblings, 0 replies; 22+ messages in thread
From: Lou Crittenden @ 2015-01-12 7:48 UTC (permalink / raw)
To: buildroot
Oh, I forgot to enable the TOUCHSCREEN_ADS7846 option. Is this [y] or [m]?
I chose [y].
On Mon, Jan 12, 2015 at 1:39 AM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> Here's my latest buildroot config for your consideration. At least we know
> it works.
>
> On Mon, Jan 12, 2015 at 1:29 AM, Peter Seiderer <ps.report@gmx.net> wrote:
>
>> Hello Lou,
>>
>> > Gesendet: Montag, 12. Januar 2015 um 05:55 Uhr
>> > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
>> > An: "Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
>> > Betreff: Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add
>> fbtft kernel extension
>> >
>> > Good news! The screen works, however the orientation is portrait
>> instead of landscape and I'd
>> > like it to be landscape. Also, how do I make this driver load on boot
>> so I do not have to
>> > keep loading "insmod
>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>> name=waveshare32b"
>> > every time, so I can have this screen be the default? I also want to
>> load the ads7846
>> > touchscreen driver as well for touchscreen.
>>
>> The rotation part is the easy one, try
>>
>> $ insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>> name=waveshare32b rotation=90
>>
>> The automatic loading should work with the /etc/modules-load.d/fbtft.conf
>> and /etc/modprobe.d/00-fbtft.conf
>> entries (do not forget to add rotation=90 to 00-fbtft-conf), but I have
>> to take a closer look at your
>> buildroot config whats missing or is different from my one, needs some
>> time ;-)
>>
>> For the touchscreen try [1]...
>>
>> > Again, thanks a bunch.
>>
>> Your welcome,
>> Peter
>>
>> [1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150112/74824d77/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-12 22:56 Peter Seiderer
2015-01-12 23:30 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Peter Seiderer @ 2015-01-12 22:56 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Mon, Jan 12, 2015 at 01:48:02AM -0600, Lou Crittenden wrote:
> Oh, I forgot to enable the TOUCHSCREEN_ADS7846 option. Is this [y] or [m]?
> I chose [y].
I would chose [m]...but use my patch from [1], it will enable all
kernel-configs automatically...
You need the ads7846_device.ko module in addition, see [2] or take
a closer look at the patch...
Regards,
Peter
[1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
[2] https://github.com/notro/fbtft_tools/wiki/ads7846_device
>
> On Mon, Jan 12, 2015 at 1:39 AM, Lou Crittenden <loucrittenden63@gmail.com>
> wrote:
>
> > Here's my latest buildroot config for your consideration. At least we know
> > it works.
> >
> > On Mon, Jan 12, 2015 at 1:29 AM, Peter Seiderer <ps.report@gmx.net> wrote:
> >
> >> Hello Lou,
> >>
> >> > Gesendet: Montag, 12. Januar 2015 um 05:55 Uhr
> >> > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
> >> > An: "Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
> >> > Betreff: Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add
> >> fbtft kernel extension
> >> >
> >> > Good news! The screen works, however the orientation is portrait
> >> instead of landscape and I'd
> >> > like it to be landscape. Also, how do I make this driver load on boot
> >> so I do not have to
> >> > keep loading "insmod
> >> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> >> name=waveshare32b"
> >> > every time, so I can have this screen be the default? I also want to
> >> load the ads7846
> >> > touchscreen driver as well for touchscreen.
> >>
> >> The rotation part is the easy one, try
> >>
> >> $ insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> >> name=waveshare32b rotation=90
> >>
> >> The automatic loading should work with the /etc/modules-load.d/fbtft.conf
> >> and /etc/modprobe.d/00-fbtft.conf
> >> entries (do not forget to add rotation=90 to 00-fbtft-conf), but I have
> >> to take a closer look at your
> >> buildroot config whats missing or is different from my one, needs some
> >> time ;-)
> >>
> >> For the touchscreen try [1]...
> >>
> >> > Again, thanks a bunch.
> >>
> >> Your welcome,
> >> Peter
> >>
> >> [1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
> >>
> >
> >
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 22:56 Peter Seiderer
@ 2015-01-12 23:30 ` Lou Crittenden
2015-01-12 23:33 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-12 23:30 UTC (permalink / raw)
To: buildroot
I did another make with TOUCHSCREEN_ADS7846 option as m this time, and now
I have the ads7846_device.ko file. I also applied the patch and we'll see
how it goes. I hope Thomas P. didn't get you down on that day.
On Mon, Jan 12, 2015 at 4:56 PM, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Lou,
>
> On Mon, Jan 12, 2015 at 01:48:02AM -0600, Lou Crittenden wrote:
> > Oh, I forgot to enable the TOUCHSCREEN_ADS7846 option. Is this [y] or
> [m]?
> > I chose [y].
>
> I would chose [m]...but use my patch from [1], it will enable all
> kernel-configs automatically...
>
> You need the ads7846_device.ko module in addition, see [2] or take
> a closer look at the patch...
>
> Regards,
> Peter
>
> [1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
> [2] https://github.com/notro/fbtft_tools/wiki/ads7846_device
> >
> > On Mon, Jan 12, 2015 at 1:39 AM, Lou Crittenden <
> loucrittenden63 at gmail.com>
> > wrote:
> >
> > > Here's my latest buildroot config for your consideration. At least we
> know
> > > it works.
> > >
> > > On Mon, Jan 12, 2015 at 1:29 AM, Peter Seiderer <ps.report@gmx.net>
> wrote:
> > >
> > >> Hello Lou,
> > >>
> > >> > Gesendet: Montag, 12. Januar 2015 um 05:55 Uhr
> > >> > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
> > >> > An: "Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
> > >> > Betreff: Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add
> > >> fbtft kernel extension
> > >> >
> > >> > Good news! The screen works, however the orientation is portrait
> > >> instead of landscape and I'd
> > >> > like it to be landscape. Also, how do I make this driver load on
> boot
> > >> so I do not have to
> > >> > keep loading "insmod
> > >> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> > >> name=waveshare32b"
> > >> > every time, so I can have this screen be the default? I also want to
> > >> load the ads7846
> > >> > touchscreen driver as well for touchscreen.
> > >>
> > >> The rotation part is the easy one, try
> > >>
> > >> $ insmod
> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> > >> name=waveshare32b rotation=90
> > >>
> > >> The automatic loading should work with the
> /etc/modules-load.d/fbtft.conf
> > >> and /etc/modprobe.d/00-fbtft.conf
> > >> entries (do not forget to add rotation=90 to 00-fbtft-conf), but I
> have
> > >> to take a closer look at your
> > >> buildroot config whats missing or is different from my one, needs some
> > >> time ;-)
> > >>
> > >> For the touchscreen try [1]...
> > >>
> > >> > Again, thanks a bunch.
> > >>
> > >> Your welcome,
> > >> Peter
> > >>
> > >> [1]
> http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
> > >>
> > >
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150112/cd46e4d3/attachment-0001.html>
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 23:30 ` Lou Crittenden
@ 2015-01-12 23:33 ` Lou Crittenden
2015-01-13 5:58 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-12 23:33 UTC (permalink / raw)
To: buildroot
here's the output of the patch job:
lou at lou:~/tmp/buildroot-2014.11$ patch -p 1 < '/home/lou/ads7846.patch'
patching file linux/linux.mk
Hunk #1 succeeded at 194 (offset -2 lines).
patching file package/Config.in
Hunk #1 succeeded at 284 (offset -2 lines).
patching file package/ads7846-device/Config.in
patching file package/ads7846-device/ads7846-device.mk
Were these the files you want to patch?
On Mon, Jan 12, 2015 at 5:30 PM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> I did another make with TOUCHSCREEN_ADS7846 option as m this time, and
> now I have the ads7846_device.ko file. I also applied the patch and we'll
> see how it goes. I hope Thomas P. didn't get you down on that day.
>
> On Mon, Jan 12, 2015 at 4:56 PM, Peter Seiderer <ps.report@gmx.net> wrote:
>
>> Hello Lou,
>>
>> On Mon, Jan 12, 2015 at 01:48:02AM -0600, Lou Crittenden wrote:
>> > Oh, I forgot to enable the TOUCHSCREEN_ADS7846 option. Is this [y] or
>> [m]?
>> > I chose [y].
>>
>> I would chose [m]...but use my patch from [1], it will enable all
>> kernel-configs automatically...
>>
>> You need the ads7846_device.ko module in addition, see [2] or take
>> a closer look at the patch...
>>
>> Regards,
>> Peter
>>
>> [1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
>> [2] https://github.com/notro/fbtft_tools/wiki/ads7846_device
>> >
>> > On Mon, Jan 12, 2015 at 1:39 AM, Lou Crittenden <
>> loucrittenden63 at gmail.com>
>> > wrote:
>> >
>> > > Here's my latest buildroot config for your consideration. At least we
>> know
>> > > it works.
>> > >
>> > > On Mon, Jan 12, 2015 at 1:29 AM, Peter Seiderer <ps.report@gmx.net>
>> wrote:
>> > >
>> > >> Hello Lou,
>> > >>
>> > >> > Gesendet: Montag, 12. Januar 2015 um 05:55 Uhr
>> > >> > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
>> > >> > An: "Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
>> > >> > Betreff: Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add
>> > >> fbtft kernel extension
>> > >> >
>> > >> > Good news! The screen works, however the orientation is portrait
>> > >> instead of landscape and I'd
>> > >> > like it to be landscape. Also, how do I make this driver load on
>> boot
>> > >> so I do not have to
>> > >> > keep loading "insmod
>> > >> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>> > >> name=waveshare32b"
>> > >> > every time, so I can have this screen be the default? I also want
>> to
>> > >> load the ads7846
>> > >> > touchscreen driver as well for touchscreen.
>> > >>
>> > >> The rotation part is the easy one, try
>> > >>
>> > >> $ insmod
>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>> > >> name=waveshare32b rotation=90
>> > >>
>> > >> The automatic loading should work with the
>> /etc/modules-load.d/fbtft.conf
>> > >> and /etc/modprobe.d/00-fbtft.conf
>> > >> entries (do not forget to add rotation=90 to 00-fbtft-conf), but I
>> have
>> > >> to take a closer look at your
>> > >> buildroot config whats missing or is different from my one, needs
>> some
>> > >> time ;-)
>> > >>
>> > >> For the touchscreen try [1]...
>> > >>
>> > >> > Again, thanks a bunch.
>> > >>
>> > >> Your welcome,
>> > >> Peter
>> > >>
>> > >> [1]
>> http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
>> > >>
>> > >
>> > >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150112/cfa6e2aa/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-12 23:33 ` Lou Crittenden
@ 2015-01-13 5:58 ` Lou Crittenden
0 siblings, 0 replies; 22+ messages in thread
From: Lou Crittenden @ 2015-01-13 5:58 UTC (permalink / raw)
To: buildroot
As for the drivers starting up @ boot, I followed the advice of this page:
http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
(I have busybox enabled) and attempted to make a simple script in the
/etc/init.d/ folder called fbtft, but no go.
here it is (and I did make sure to run chmod +x on it to make it
executable):
#!/bin/sh
exec insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
name=waveshare32b rotate=270
exec insmod /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
On Mon, Jan 12, 2015 at 5:33 PM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> here's the output of the patch job:
>
> lou at lou:~/tmp/buildroot-2014.11$ patch -p 1 < '/home/lou/ads7846.patch'
> patching file linux/linux.mk
> Hunk #1 succeeded at 194 (offset -2 lines).
> patching file package/Config.in
> Hunk #1 succeeded at 284 (offset -2 lines).
> patching file package/ads7846-device/Config.in
> patching file package/ads7846-device/ads7846-device.mk
>
>
> Were these the files you want to patch?
>
> On Mon, Jan 12, 2015 at 5:30 PM, Lou Crittenden <loucrittenden63@gmail.com
> > wrote:
>
>> I did another make with TOUCHSCREEN_ADS7846 option as m this time, and
>> now I have the ads7846_device.ko file. I also applied the patch and
>> we'll see how it goes. I hope Thomas P. didn't get you down on that day.
>>
>> On Mon, Jan 12, 2015 at 4:56 PM, Peter Seiderer <ps.report@gmx.net>
>> wrote:
>>
>>> Hello Lou,
>>>
>>> On Mon, Jan 12, 2015 at 01:48:02AM -0600, Lou Crittenden wrote:
>>> > Oh, I forgot to enable the TOUCHSCREEN_ADS7846 option. Is this [y] or
>>> [m]?
>>> > I chose [y].
>>>
>>> I would chose [m]...but use my patch from [1], it will enable all
>>> kernel-configs automatically...
>>>
>>> You need the ads7846_device.ko module in addition, see [2] or take
>>> a closer look at the patch...
>>>
>>> Regards,
>>> Peter
>>>
>>> [1]
>>> http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
>>> [2] https://github.com/notro/fbtft_tools/wiki/ads7846_device
>>> >
>>> > On Mon, Jan 12, 2015 at 1:39 AM, Lou Crittenden <
>>> loucrittenden63 at gmail.com>
>>> > wrote:
>>> >
>>> > > Here's my latest buildroot config for your consideration. At least
>>> we know
>>> > > it works.
>>> > >
>>> > > On Mon, Jan 12, 2015 at 1:29 AM, Peter Seiderer <ps.report@gmx.net>
>>> wrote:
>>> > >
>>> > >> Hello Lou,
>>> > >>
>>> > >> > Gesendet: Montag, 12. Januar 2015 um 05:55 Uhr
>>> > >> > Von: "Lou Crittenden" <loucrittenden63@gmail.com>
>>> > >> > An: "Peter Seiderer" <ps.report@gmx.net>, buildroot at busybox.net
>>> > >> > Betreff: Re: Fwd: Fwd: Fwd: Fwd: [Buildroot] [PATCH v3] linux: add
>>> > >> fbtft kernel extension
>>> > >> >
>>> > >> > Good news! The screen works, however the orientation is portrait
>>> > >> instead of landscape and I'd
>>> > >> > like it to be landscape. Also, how do I make this driver load on
>>> boot
>>> > >> so I do not have to
>>> > >> > keep loading "insmod
>>> > >> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>>> > >> name=waveshare32b"
>>> > >> > every time, so I can have this screen be the default? I also want
>>> to
>>> > >> load the ads7846
>>> > >> > touchscreen driver as well for touchscreen.
>>> > >>
>>> > >> The rotation part is the easy one, try
>>> > >>
>>> > >> $ insmod
>>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>>> > >> name=waveshare32b rotation=90
>>> > >>
>>> > >> The automatic loading should work with the
>>> /etc/modules-load.d/fbtft.conf
>>> > >> and /etc/modprobe.d/00-fbtft.conf
>>> > >> entries (do not forget to add rotation=90 to 00-fbtft-conf), but I
>>> have
>>> > >> to take a closer look at your
>>> > >> buildroot config whats missing or is different from my one, needs
>>> some
>>> > >> time ;-)
>>> > >>
>>> > >> For the touchscreen try [1]...
>>> > >>
>>> > >> > Again, thanks a bunch.
>>> > >>
>>> > >> Your welcome,
>>> > >> Peter
>>> > >>
>>> > >> [1]
>>> http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
>>> > >>
>>> > >
>>> > >
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150112/edb392a1/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-13 19:49 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-13 19:49 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Mon, Jan 12, 2015 at 05:30:22PM -0600, Lou Crittenden wrote:
> I did another make with TOUCHSCREEN_ADS7846 option as m this time, and now
> I have the ads7846_device.ko file. I also applied the patch and we'll see
> how it goes. I hope Thomas P. didn't get you down on that day.
No the linux kernel CONFIG_TOUCHSCREEN_ADS7846=m buills only the
'basic' ads7846.ko kernel module. You need the additional
ads7846_device.ko kernel module which will configure your basic
ads7846.ko module. Therefore the buildroot patch which will
build the ads7846_device.ko module for you (and will do the
right kernel config additions)....
Regards,
Peter
>
> On Mon, Jan 12, 2015 at 4:56 PM, Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Hello Lou,
> >
> > On Mon, Jan 12, 2015 at 01:48:02AM -0600, Lou Crittenden wrote:
> > > Oh, I forgot to enable the TOUCHSCREEN_ADS7846 option. Is this [y] or
> > [m]?
> > > I chose [y].
> >
> > I would chose [m]...but use my patch from [1], it will enable all
> > kernel-configs automatically...
> >
> > You need the ads7846_device.ko module in addition, see [2] or take
> > a closer look at the patch...
> >
> > Regards,
> > Peter
> >
> > [1] http://lists.busybox.net/pipermail/buildroot/2015-January/116799.html
> > [2] https://github.com/notro/fbtft_tools/wiki/ads7846_device
> > >
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-13 19:56 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-13 19:56 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Mon, Jan 12, 2015 at 05:33:12PM -0600, Lou Crittenden wrote:
> here's the output of the patch job:
>
> lou at lou:~/tmp/buildroot-2014.11$ patch -p 1 < '/home/lou/ads7846.patch'
> patching file linux/linux.mk
> Hunk #1 succeeded at 194 (offset -2 lines).
> patching file package/Config.in
> Hunk #1 succeeded at 284 (offset -2 lines).
> patching file package/ads7846-device/Config.in
> patching file package/ads7846-device/ads7846-device.mk
>
>
> Were these the files you want to patch?
Yes, now you have to enable the buildroot option 'BR2_PACKAGE_ADS7846_DEVICE'
and start a buildroot build (best complete rebuild, second best force
a rebuild of the linux kernel and modules)...
After this you should have a ads7846.ko module and an ads7846_device.ko module...
Regards,
Peter
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-13 20:01 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-13 20:01 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Mon, Jan 12, 2015 at 05:30:22PM -0600, Lou Crittenden wrote:
> I did another make with TOUCHSCREEN_ADS7846 option as m this time, and now
> I have the ads7846_device.ko file. I also applied the patch and we'll see
> how it goes. I hope Thomas P. didn't get you down on that day.
Thanks, no problem, Thomas is doing a great job as buildroot maintainer and
his patch reviews lead to very improved patch/buildroot results...
Regards,
Peter
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-13 20:58 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-13 20:58 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
> As for the drivers starting up @ boot, I followed the advice of this page:
> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
> (I have busybox enabled) and attempted to make a simple script in the
> /etc/init.d/ folder called fbtft, but no go.
>
> here it is (and I did make sure to run chmod +x on it to make it
> executable):
>
> #!/bin/sh
>
> exec insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> name=waveshare32b rotate=270
>
> exec insmod /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
>
Your script should be named '/etc/init.d/S30fbtft', only scripts starting with 'S??' will
be called on startup (see '/etc/init.d/rcS')...
My method did not work for you because I used the systemd init system, yours is the busybox init system,
sorry for the confusion...
Regards,
Peter
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-13 21:41 Peter Seiderer
2015-01-13 23:19 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Peter Seiderer @ 2015-01-13 21:41 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
> As for the drivers starting up @ boot, I followed the advice of this page:
> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
> (I have busybox enabled) and attempted to make a simple script in the
> /etc/init.d/ folder called fbtft, but no go.
>
> here it is (and I did make sure to run chmod +x on it to make it
> executable):
>
> #!/bin/sh
>
> exec insmod /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> name=waveshare32b rotate=270
>
> exec insmod /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
>
The following script '/etc/init.d/S30fbtft' should work:
--- begin ----
#!/bin/sh
#
# Start waveshare32b (fbtft_device, ads7846_device)
#
case "$1" in
start)
echo -n "Starting waveshare32b: "
modprobe fbtft_device name=waveshare32b rotate=270
# from https://github.com/notro/fbtft/issues/181
modprobe ads7846_device model=7846 cs=1 gpio_pendown=17 speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900
# from http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=95231
# modprobe ads7846_device model=7846 cs=1 gpio_pendown=17 speed=1000000 keep_vref_on=1 swap_xy=0
echo "OK"
;;
stop)
echo -n "Stopping waveshare32b: "
rmmod fbtft_device
rmmod fb_ili9340
rmmod ads7846_device
rmmod ads7846
echo "OK"
;;
restart|reload)
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac
exit $?
--- end ---
For testing use
$ /etc/init.d/S30fbtft start
or
$ /etc/init.d/S30fbtft stop
On success there should be a second framebuffer device /dev/fb1 and an additional
input device e.g. /dev/input/event3
For testing the the touch I use
$ cat /dev/input/event3 | hexdump
or
$ evtest
which shows all input event devices with name and gives nice human readable output
(your have to enable the buildroot package first)...
Regards,
Peter
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-13 21:41 Peter Seiderer
@ 2015-01-13 23:19 ` Lou Crittenden
2015-01-14 1:20 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-13 23:19 UTC (permalink / raw)
To: buildroot
We're getting closer, but no cigar yet.
The script runs at boot.
I ran /etc/init.d/S30fbtft start to start the script and it outputs:
starting waveshare: OK
then outputs:
FATAL: module fbtft_device not found.
and the screen doesn't initialize.
The error also shows up while booting up.
I can also run modprobe fbtft_device name=waveshare32b and I get the same
error message.
On Tue, Jan 13, 2015 at 3:41 PM, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Lou,
>
> On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
> > As for the drivers starting up @ boot, I followed the advice of this
> page:
> >
> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
> > (I have busybox enabled) and attempted to make a simple script in the
> > /etc/init.d/ folder called fbtft, but no go.
> >
> > here it is (and I did make sure to run chmod +x on it to make it
> > executable):
> >
> > #!/bin/sh
> >
> > exec insmod
> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
> > name=waveshare32b rotate=270
> >
> > exec insmod
> /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
> >
>
> The following script '/etc/init.d/S30fbtft' should work:
> --- begin ----
> #!/bin/sh
> #
> # Start waveshare32b (fbtft_device, ads7846_device)
> #
>
> case "$1" in
> start)
> echo -n "Starting waveshare32b: "
> modprobe fbtft_device name=waveshare32b rotate=270
> # from https://github.com/notro/fbtft/issues/181
> modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
> speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60
> x_min=200 x_max=3900 y_min=200 y_max=3900
> # from
> http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=95231
> # modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
> speed=1000000 keep_vref_on=1 swap_xy=0
> echo "OK"
> ;;
> stop)
> echo -n "Stopping waveshare32b: "
> rmmod fbtft_device
> rmmod fb_ili9340
> rmmod ads7846_device
> rmmod ads7846
> echo "OK"
> ;;
> restart|reload)
> ;;
> *)
> echo "Usage: $0 {start|stop|restart}"
> exit 1
> esac
>
> exit $?
> --- end ---
>
> For testing use
> $ /etc/init.d/S30fbtft start
> or
> $ /etc/init.d/S30fbtft stop
>
> On success there should be a second framebuffer device /dev/fb1 and an
> additional
> input device e.g. /dev/input/event3
>
> For testing the the touch I use
> $ cat /dev/input/event3 | hexdump
> or
> $ evtest
> which shows all input event devices with name and gives nice human
> readable output
> (your have to enable the buildroot package first)...
>
> Regards,
> Peter
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150113/82dad166/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-13 23:19 ` Lou Crittenden
@ 2015-01-14 1:20 ` Lou Crittenden
2015-01-14 1:37 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-14 1:20 UTC (permalink / raw)
To: buildroot
NEVERMIND NEVERMIND! Your script works! It turns out I forgot to enable
the fbtft_device drivers in make linuxconfig. I ran a "make clean all"
beforehand and forgot I had to run make linuxconfig then run make all.
On Tue, Jan 13, 2015 at 5:19 PM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> We're getting closer, but no cigar yet.
>
> The script runs at boot.
>
> I ran /etc/init.d/S30fbtft start to start the script and it outputs:
>
> starting waveshare: OK
>
> then outputs:
>
> FATAL: module fbtft_device not found.
>
> and the screen doesn't initialize.
>
> The error also shows up while booting up.
>
> I can also run modprobe fbtft_device name=waveshare32b and I get the same
> error message.
>
>
>
>
> On Tue, Jan 13, 2015 at 3:41 PM, Peter Seiderer <ps.report@gmx.net> wrote:
>
>> Hello Lou,
>>
>> On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
>> > As for the drivers starting up @ boot, I followed the advice of this
>> page:
>> >
>> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
>> > (I have busybox enabled) and attempted to make a simple script in the
>> > /etc/init.d/ folder called fbtft, but no go.
>> >
>> > here it is (and I did make sure to run chmod +x on it to make it
>> > executable):
>> >
>> > #!/bin/sh
>> >
>> > exec insmod
>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>> > name=waveshare32b rotate=270
>> >
>> > exec insmod
>> /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
>> >
>>
>> The following script '/etc/init.d/S30fbtft' should work:
>> --- begin ----
>> #!/bin/sh
>> #
>> # Start waveshare32b (fbtft_device, ads7846_device)
>> #
>>
>> case "$1" in
>> start)
>> echo -n "Starting waveshare32b: "
>> modprobe fbtft_device name=waveshare32b rotate=270
>> # from https://github.com/notro/fbtft/issues/181
>> modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>> speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60
>> x_min=200 x_max=3900 y_min=200 y_max=3900
>> # from
>> http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=95231
>> # modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>> speed=1000000 keep_vref_on=1 swap_xy=0
>> echo "OK"
>> ;;
>> stop)
>> echo -n "Stopping waveshare32b: "
>> rmmod fbtft_device
>> rmmod fb_ili9340
>> rmmod ads7846_device
>> rmmod ads7846
>> echo "OK"
>> ;;
>> restart|reload)
>> ;;
>> *)
>> echo "Usage: $0 {start|stop|restart}"
>> exit 1
>> esac
>>
>> exit $?
>> --- end ---
>>
>> For testing use
>> $ /etc/init.d/S30fbtft start
>> or
>> $ /etc/init.d/S30fbtft stop
>>
>> On success there should be a second framebuffer device /dev/fb1 and an
>> additional
>> input device e.g. /dev/input/event3
>>
>> For testing the the touch I use
>> $ cat /dev/input/event3 | hexdump
>> or
>> $ evtest
>> which shows all input event devices with name and gives nice human
>> readable output
>> (your have to enable the buildroot package first)...
>>
>> Regards,
>> Peter
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150113/6135d7cc/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-14 1:20 ` Lou Crittenden
@ 2015-01-14 1:37 ` Lou Crittenden
2015-01-14 1:53 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-14 1:37 UTC (permalink / raw)
To: buildroot
I looked at my configuration and in the make config evtest was not enabled,
so I have to enable it so I can test my touchscreen.
Again, thanks for all the info!
Just curious: How long have you been working in embedded systems and
linux???
On Tue, Jan 13, 2015 at 7:20 PM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> NEVERMIND NEVERMIND! Your script works! It turns out I forgot to enable
> the fbtft_device drivers in make linuxconfig. I ran a "make clean all"
> beforehand and forgot I had to run make linuxconfig then run make all.
>
>
>
> On Tue, Jan 13, 2015 at 5:19 PM, Lou Crittenden <loucrittenden63@gmail.com
> > wrote:
>
>> We're getting closer, but no cigar yet.
>>
>> The script runs at boot.
>>
>> I ran /etc/init.d/S30fbtft start to start the script and it outputs:
>>
>> starting waveshare: OK
>>
>> then outputs:
>>
>> FATAL: module fbtft_device not found.
>>
>> and the screen doesn't initialize.
>>
>> The error also shows up while booting up.
>>
>> I can also run modprobe fbtft_device name=waveshare32b and I get the
>> same error message.
>>
>>
>>
>>
>> On Tue, Jan 13, 2015 at 3:41 PM, Peter Seiderer <ps.report@gmx.net>
>> wrote:
>>
>>> Hello Lou,
>>>
>>> On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
>>> > As for the drivers starting up @ boot, I followed the advice of this
>>> page:
>>> >
>>> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
>>> > (I have busybox enabled) and attempted to make a simple script in the
>>> > /etc/init.d/ folder called fbtft, but no go.
>>> >
>>> > here it is (and I did make sure to run chmod +x on it to make it
>>> > executable):
>>> >
>>> > #!/bin/sh
>>> >
>>> > exec insmod
>>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>>> > name=waveshare32b rotate=270
>>> >
>>> > exec insmod
>>> /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
>>> >
>>>
>>> The following script '/etc/init.d/S30fbtft' should work:
>>> --- begin ----
>>> #!/bin/sh
>>> #
>>> # Start waveshare32b (fbtft_device, ads7846_device)
>>> #
>>>
>>> case "$1" in
>>> start)
>>> echo -n "Starting waveshare32b: "
>>> modprobe fbtft_device name=waveshare32b rotate=270
>>> # from https://github.com/notro/fbtft/issues/181
>>> modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>>> speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60
>>> x_min=200 x_max=3900 y_min=200 y_max=3900
>>> # from
>>> http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=95231
>>> # modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>>> speed=1000000 keep_vref_on=1 swap_xy=0
>>> echo "OK"
>>> ;;
>>> stop)
>>> echo -n "Stopping waveshare32b: "
>>> rmmod fbtft_device
>>> rmmod fb_ili9340
>>> rmmod ads7846_device
>>> rmmod ads7846
>>> echo "OK"
>>> ;;
>>> restart|reload)
>>> ;;
>>> *)
>>> echo "Usage: $0 {start|stop|restart}"
>>> exit 1
>>> esac
>>>
>>> exit $?
>>> --- end ---
>>>
>>> For testing use
>>> $ /etc/init.d/S30fbtft start
>>> or
>>> $ /etc/init.d/S30fbtft stop
>>>
>>> On success there should be a second framebuffer device /dev/fb1 and an
>>> additional
>>> input device e.g. /dev/input/event3
>>>
>>> For testing the the touch I use
>>> $ cat /dev/input/event3 | hexdump
>>> or
>>> $ evtest
>>> which shows all input event devices with name and gives nice human
>>> readable output
>>> (your have to enable the buildroot package first)...
>>>
>>> Regards,
>>> Peter
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150113/813d4a04/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-14 1:37 ` Lou Crittenden
@ 2015-01-14 1:53 ` Lou Crittenden
2015-01-14 22:22 ` Lou Crittenden
0 siblings, 1 reply; 22+ messages in thread
From: Lou Crittenden @ 2015-01-14 1:53 UTC (permalink / raw)
To: buildroot
I run evtest, then it shows the available inputs, /dev/input*, then asks me
what one to run [0-2]. In my case it is /dev/input2, so I choose 2. I then
touch the screen and it shows a bunch of info about pressure and a bunch of
random numbers. I now know the touchscreen is working.
On Tue, Jan 13, 2015 at 7:37 PM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> I looked at my configuration and in the make config evtest was not
> enabled, so I have to enable it so I can test my touchscreen.
>
> Again, thanks for all the info!
>
> Just curious: How long have you been working in embedded systems and
> linux???
>
> On Tue, Jan 13, 2015 at 7:20 PM, Lou Crittenden <loucrittenden63@gmail.com
> > wrote:
>
>> NEVERMIND NEVERMIND! Your script works! It turns out I forgot to enable
>> the fbtft_device drivers in make linuxconfig. I ran a "make clean all"
>> beforehand and forgot I had to run make linuxconfig then run make all.
>>
>>
>>
>> On Tue, Jan 13, 2015 at 5:19 PM, Lou Crittenden <
>> loucrittenden63 at gmail.com> wrote:
>>
>>> We're getting closer, but no cigar yet.
>>>
>>> The script runs at boot.
>>>
>>> I ran /etc/init.d/S30fbtft start to start the script and it outputs:
>>>
>>> starting waveshare: OK
>>>
>>> then outputs:
>>>
>>> FATAL: module fbtft_device not found.
>>>
>>> and the screen doesn't initialize.
>>>
>>> The error also shows up while booting up.
>>>
>>> I can also run modprobe fbtft_device name=waveshare32b and I get the
>>> same error message.
>>>
>>>
>>>
>>>
>>> On Tue, Jan 13, 2015 at 3:41 PM, Peter Seiderer <ps.report@gmx.net>
>>> wrote:
>>>
>>>> Hello Lou,
>>>>
>>>> On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
>>>> > As for the drivers starting up @ boot, I followed the advice of this
>>>> page:
>>>> >
>>>> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
>>>> > (I have busybox enabled) and attempted to make a simple script in the
>>>> > /etc/init.d/ folder called fbtft, but no go.
>>>> >
>>>> > here it is (and I did make sure to run chmod +x on it to make it
>>>> > executable):
>>>> >
>>>> > #!/bin/sh
>>>> >
>>>> > exec insmod
>>>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>>>> > name=waveshare32b rotate=270
>>>> >
>>>> > exec insmod
>>>> /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
>>>> >
>>>>
>>>> The following script '/etc/init.d/S30fbtft' should work:
>>>> --- begin ----
>>>> #!/bin/sh
>>>> #
>>>> # Start waveshare32b (fbtft_device, ads7846_device)
>>>> #
>>>>
>>>> case "$1" in
>>>> start)
>>>> echo -n "Starting waveshare32b: "
>>>> modprobe fbtft_device name=waveshare32b rotate=270
>>>> # from https://github.com/notro/fbtft/issues/181
>>>> modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>>>> speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60
>>>> x_min=200 x_max=3900 y_min=200 y_max=3900
>>>> # from
>>>> http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=95231
>>>> # modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>>>> speed=1000000 keep_vref_on=1 swap_xy=0
>>>> echo "OK"
>>>> ;;
>>>> stop)
>>>> echo -n "Stopping waveshare32b: "
>>>> rmmod fbtft_device
>>>> rmmod fb_ili9340
>>>> rmmod ads7846_device
>>>> rmmod ads7846
>>>> echo "OK"
>>>> ;;
>>>> restart|reload)
>>>> ;;
>>>> *)
>>>> echo "Usage: $0 {start|stop|restart}"
>>>> exit 1
>>>> esac
>>>>
>>>> exit $?
>>>> --- end ---
>>>>
>>>> For testing use
>>>> $ /etc/init.d/S30fbtft start
>>>> or
>>>> $ /etc/init.d/S30fbtft stop
>>>>
>>>> On success there should be a second framebuffer device /dev/fb1 and an
>>>> additional
>>>> input device e.g. /dev/input/event3
>>>>
>>>> For testing the the touch I use
>>>> $ cat /dev/input/event3 | hexdump
>>>> or
>>>> $ evtest
>>>> which shows all input event devices with name and gives nice human
>>>> readable output
>>>> (your have to enable the buildroot package first)...
>>>>
>>>> Regards,
>>>> Peter
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150113/1ec1ca2e/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
2015-01-14 1:53 ` Lou Crittenden
@ 2015-01-14 22:22 ` Lou Crittenden
0 siblings, 0 replies; 22+ messages in thread
From: Lou Crittenden @ 2015-01-14 22:22 UTC (permalink / raw)
To: buildroot
So far, so good! The screen is still working great, as well as the
touchscreen driver. Once again, Thanks a bunch for helping me out on this.
Do you take donations?
On Tue, Jan 13, 2015 at 7:53 PM, Lou Crittenden <loucrittenden63@gmail.com>
wrote:
> I run evtest, then it shows the available inputs, /dev/input*, then asks
> me what one to run [0-2]. In my case it is /dev/input2, so I choose 2. I
> then touch the screen and it shows a bunch of info about pressure and a
> bunch of random numbers. I now know the touchscreen is working.
>
> On Tue, Jan 13, 2015 at 7:37 PM, Lou Crittenden <loucrittenden63@gmail.com
> > wrote:
>
>> I looked at my configuration and in the make config evtest was not
>> enabled, so I have to enable it so I can test my touchscreen.
>>
>> Again, thanks for all the info!
>>
>> Just curious: How long have you been working in embedded systems and
>> linux???
>>
>> On Tue, Jan 13, 2015 at 7:20 PM, Lou Crittenden <
>> loucrittenden63 at gmail.com> wrote:
>>
>>> NEVERMIND NEVERMIND! Your script works! It turns out I forgot to enable
>>> the fbtft_device drivers in make linuxconfig. I ran a "make clean all"
>>> beforehand and forgot I had to run make linuxconfig then run make all.
>>>
>>>
>>>
>>> On Tue, Jan 13, 2015 at 5:19 PM, Lou Crittenden <
>>> loucrittenden63 at gmail.com> wrote:
>>>
>>>> We're getting closer, but no cigar yet.
>>>>
>>>> The script runs at boot.
>>>>
>>>> I ran /etc/init.d/S30fbtft start to start the script and it outputs:
>>>>
>>>> starting waveshare: OK
>>>>
>>>> then outputs:
>>>>
>>>> FATAL: module fbtft_device not found.
>>>>
>>>> and the screen doesn't initialize.
>>>>
>>>> The error also shows up while booting up.
>>>>
>>>> I can also run modprobe fbtft_device name=waveshare32b and I get the
>>>> same error message.
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jan 13, 2015 at 3:41 PM, Peter Seiderer <ps.report@gmx.net>
>>>> wrote:
>>>>
>>>>> Hello Lou,
>>>>>
>>>>> On Mon, Jan 12, 2015 at 11:58:16PM -0600, Lou Crittenden wrote:
>>>>> > As for the drivers starting up @ boot, I followed the advice of this
>>>>> page:
>>>>> >
>>>>> http://unix.stackexchange.com/questions/59018/create-and-control-start-up-scripts-in-busybox
>>>>> > (I have busybox enabled) and attempted to make a simple script in the
>>>>> > /etc/init.d/ folder called fbtft, but no go.
>>>>> >
>>>>> > here it is (and I did make sure to run chmod +x on it to make it
>>>>> > executable):
>>>>> >
>>>>> > #!/bin/sh
>>>>> >
>>>>> > exec insmod
>>>>> /lib/modules/3.12.28/kernel/drivers/video/fbtft/fbtft_device.ko
>>>>> > name=waveshare32b rotate=270
>>>>> >
>>>>> > exec insmod
>>>>> /lib/modules/3.12.28/kernel/drivers/input/touchscreen/ads7846.ko
>>>>> >
>>>>>
>>>>> The following script '/etc/init.d/S30fbtft' should work:
>>>>> --- begin ----
>>>>> #!/bin/sh
>>>>> #
>>>>> # Start waveshare32b (fbtft_device, ads7846_device)
>>>>> #
>>>>>
>>>>> case "$1" in
>>>>> start)
>>>>> echo -n "Starting waveshare32b: "
>>>>> modprobe fbtft_device name=waveshare32b rotate=270
>>>>> # from https://github.com/notro/fbtft/issues/181
>>>>> modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>>>>> speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60
>>>>> x_min=200 x_max=3900 y_min=200 y_max=3900
>>>>> # from
>>>>> http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=95231
>>>>> # modprobe ads7846_device model=7846 cs=1 gpio_pendown=17
>>>>> speed=1000000 keep_vref_on=1 swap_xy=0
>>>>> echo "OK"
>>>>> ;;
>>>>> stop)
>>>>> echo -n "Stopping waveshare32b: "
>>>>> rmmod fbtft_device
>>>>> rmmod fb_ili9340
>>>>> rmmod ads7846_device
>>>>> rmmod ads7846
>>>>> echo "OK"
>>>>> ;;
>>>>> restart|reload)
>>>>> ;;
>>>>> *)
>>>>> echo "Usage: $0 {start|stop|restart}"
>>>>> exit 1
>>>>> esac
>>>>>
>>>>> exit $?
>>>>> --- end ---
>>>>>
>>>>> For testing use
>>>>> $ /etc/init.d/S30fbtft start
>>>>> or
>>>>> $ /etc/init.d/S30fbtft stop
>>>>>
>>>>> On success there should be a second framebuffer device /dev/fb1 and an
>>>>> additional
>>>>> input device e.g. /dev/input/event3
>>>>>
>>>>> For testing the the touch I use
>>>>> $ cat /dev/input/event3 | hexdump
>>>>> or
>>>>> $ evtest
>>>>> which shows all input event devices with name and gives nice human
>>>>> readable output
>>>>> (your have to enable the buildroot package first)...
>>>>>
>>>>> Regards,
>>>>> Peter
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150114/640ee75e/attachment.html>
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-16 19:24 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-16 19:24 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Tue, Jan 13, 2015 at 07:20:26PM -0600, Lou Crittenden wrote:
> NEVERMIND NEVERMIND! Your script works! It turns out I forgot to enable
> the fbtft_device drivers in make linuxconfig. I ran a "make clean all"
> beforehand and forgot I had to run make linuxconfig then run make all.
>
Thats good news....
Regards,
Peter
>
>
> On Tue, Jan 13, 2015 at 5:19 PM, Lou Crittenden <loucrittenden63@gmail.com>
> wrote:
>
> > We're getting closer, but no cigar yet.
> >
> > The script runs at boot.
> >
> > I ran /etc/init.d/S30fbtft start to start the script and it outputs:
> >
> > starting waveshare: OK
> >
> > then outputs:
> >
> > FATAL: module fbtft_device not found.
> >
> > and the screen doesn't initialize.
> >
> > The error also shows up while booting up.
> >
> > I can also run modprobe fbtft_device name=waveshare32b and I get the same
> > error message.
> >
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-16 19:27 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-16 19:27 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Tue, Jan 13, 2015 at 07:37:03PM -0600, Lou Crittenden wrote:
> I looked at my configuration and in the make config evtest was not enabled,
> so I have to enable it so I can test my touchscreen.
>
> Again, thanks for all the info!
>
Your welcome...
> Just curious: How long have you been working in embedded systems and
> linux???
>
Working with Linux back to the 90's, embedded systems more and more recently...
Regards,
Peter
^ permalink raw reply [flat|nested] 22+ messages in thread
* [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension
@ 2015-01-16 19:34 Peter Seiderer
0 siblings, 0 replies; 22+ messages in thread
From: Peter Seiderer @ 2015-01-16 19:34 UTC (permalink / raw)
To: buildroot
Hello Lou,
On Wed, Jan 14, 2015 at 04:22:04PM -0600, Lou Crittenden wrote:
> So far, so good! The screen is still working great, as well as the
> touchscreen driver. Once again, Thanks a bunch for helping me out on this.
You where lucky I tried to enable similare display/touch with buildroot
at the same time ;-)
> Do you take donations?
>
Thanks, but testing and giving feedback for buildroot patches is enough
support ;-), its a spare time/fun project from my side (at least the
raspberry pi support, but sometimes I use buildroot for money earning
jobs as well)...
Regards,
Peter
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2015-01-16 19:34 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-01-12 0:02 [Buildroot] Fwd: Fwd: Fwd: Fwd: [PATCH v3] linux: add fbtft kernel extension Peter Seiderer
2015-01-12 4:55 ` Lou Crittenden
2015-01-12 7:29 ` Peter Seiderer
2015-01-12 7:39 ` Lou Crittenden
2015-01-12 7:48 ` Lou Crittenden
2015-01-12 22:56 Peter Seiderer
2015-01-12 23:30 ` Lou Crittenden
2015-01-12 23:33 ` Lou Crittenden
2015-01-13 5:58 ` Lou Crittenden
2015-01-13 19:49 Peter Seiderer
2015-01-13 19:56 Peter Seiderer
2015-01-13 20:01 Peter Seiderer
2015-01-13 20:58 Peter Seiderer
2015-01-13 21:41 Peter Seiderer
2015-01-13 23:19 ` Lou Crittenden
2015-01-14 1:20 ` Lou Crittenden
2015-01-14 1:37 ` Lou Crittenden
2015-01-14 1:53 ` Lou Crittenden
2015-01-14 22:22 ` Lou Crittenden
2015-01-16 19:24 Peter Seiderer
2015-01-16 19:27 Peter Seiderer
2015-01-16 19:34 Peter Seiderer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.