Adding modules to Kernel in LEDE distribution
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source
So far things I have done:
make menuconfig
and selected the required options
I also configured the kernel to load the staging drivers
make kernel_menuconfig
Device drivers -> Graphics support -> Frame buffer Devices
<*> Support for frame buffer devices
Device drivers -> Staging drivers
<*> Support for small TFT LCD display modules
<M> FB driver for the ST7735R LCD Controller
<M> Generic FB driver for TFT LCD displays
<M> Module to for adding FBTFT devices
Then I compile
make -j5 V=s
This is the output of the make process output.txt
I flash my device with the bin generated.
sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin
But when is time to use the module, it doesn't work, I've tried all of this:
insmod fb_defio
insmod fb
insmod fbtft
modeprobe fbtft
fbtft_device
and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
Am I missing something? Sorry I'm new with LEDE and Linux Kernel compilation
linux linux-kernel openwrt
asked Dec 14 '17 at 13:36
utiq
101
migrated from stackoverflow.com Dec 15 '17 at 6:02
This question came from our site for professional and enthusiast programmers.
add a comment |Â
up vote
0
down vote
favorite
So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source
So far things I have done:
make menuconfig
and selected the required options
I also configured the kernel to load the staging drivers
make kernel_menuconfig
Device drivers -> Graphics support -> Frame buffer Devices
<*> Support for frame buffer devices
Device drivers -> Staging drivers
<*> Support for small TFT LCD display modules
<M> FB driver for the ST7735R LCD Controller
<M> Generic FB driver for TFT LCD displays
<M> Module to for adding FBTFT devices
Then I compile
make -j5 V=s
This is the output of the make process output.txt
I flash my device with the bin generated.
sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin
But when is time to use the module, it doesn't work, I've tried all of this:
insmod fb_defio
insmod fb
insmod fbtft
modeprobe fbtft
fbtft_device
and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
Am I missing something? Sorry I'm new with LEDE and Linux Kernel compilation
linux linux-kernel openwrt
asked Dec 14 '17 at 13:36
utiq
101
migrated from stackoverflow.com Dec 15 '17 at 6:02
This question came from our site for professional and enthusiast programmers.
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source
So far things I have done:
make menuconfig
and selected the required options
I also configured the kernel to load the staging drivers
make kernel_menuconfig
Device drivers -> Graphics support -> Frame buffer Devices
<*> Support for frame buffer devices
Device drivers -> Staging drivers
<*> Support for small TFT LCD display modules
<M> FB driver for the ST7735R LCD Controller
<M> Generic FB driver for TFT LCD displays
<M> Module to for adding FBTFT devices
Then I compile
make -j5 V=s
This is the output of the make process output.txt
I flash my device with the bin generated.
sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin
But when is time to use the module, it doesn't work, I've tried all of this:
insmod fb_defio
insmod fb
insmod fbtft
modeprobe fbtft
fbtft_device
and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
Am I missing something? Sorry I'm new with LEDE and Linux Kernel compilation
linux linux-kernel openwrt
asked Dec 14 '17 at 13:36
utiq
101
So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source
So far things I have done:
make menuconfig
and selected the required options
I also configured the kernel to load the staging drivers
make kernel_menuconfig
Device drivers -> Graphics support -> Frame buffer Devices
<*> Support for frame buffer devices
Device drivers -> Staging drivers
<*> Support for small TFT LCD display modules
<M> FB driver for the ST7735R LCD Controller
<M> Generic FB driver for TFT LCD displays
<M> Module to for adding FBTFT devices
Then I compile
make -j5 V=s
This is the output of the make process output.txt
I flash my device with the bin generated.
sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin
But when is time to use the module, it doesn't work, I've tried all of this:
insmod fb_defio
insmod fb
insmod fbtft
modeprobe fbtft
fbtft_device
and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
Am I missing something? Sorry I'm new with LEDE and Linux Kernel compilation
linux linux-kernel openwrt
asked Dec 14 '17 at 13:36
utiq
101
asked Dec 14 '17 at 13:36
utiq
101
asked Dec 14 '17 at 13:36
utiq
101
asked Dec 14 '17 at 13:36
utiq
101
101
migrated from stackoverflow.com Dec 15 '17 at 6:02
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Dec 15 '17 at 6:02
This question came from our site for professional and enthusiast programmers.
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
In make kernel_menuconfig
Go to FBTFT driver and press y,
Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.
answered Dec 14 '17 at 17:47
VivekD
111
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
In make kernel_menuconfig
Go to FBTFT driver and press y,
Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.
answered Dec 14 '17 at 17:47
VivekD
111
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
add a comment |Â
up vote
0
down vote
In make kernel_menuconfig
Go to FBTFT driver and press y,
Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.
answered Dec 14 '17 at 17:47
VivekD
111
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
add a comment |Â
up vote
0
down vote
up vote
0
down vote
In make kernel_menuconfig
Go to FBTFT driver and press y,
Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.
answered Dec 14 '17 at 17:47
VivekD
111
In make kernel_menuconfig
Go to FBTFT driver and press y,
Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.
answered Dec 14 '17 at 17:47
VivekD
111
answered Dec 14 '17 at 17:47
VivekD
111
answered Dec 14 '17 at 17:47
VivekD
111
answered Dec 14 '17 at 17:47
VivekD
111
111
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
add a comment |Â
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices†kernel config option)
– utiq
Dec 14 '17 at 22:33
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
– VivekD
Dec 15 '17 at 11:14
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
– utiq
Dec 15 '17 at 16:03
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f410985%2fadding-modules-to-kernel-in-lede-distribution%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password