Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Hasan Karaman <hk@hasankaraman.dev>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] FBTFT extension does not work out of the box
Date: Sat, 24 Jun 2023 09:30:37 +0200	[thread overview]
Message-ID: <20230624093037.1501a619@gmx.net> (raw)
In-Reply-To: <9bdad434-d2a1-0988-8d17-3cd2f23448c2@hasankaraman.dev>

Hello Hasan,

On Fri, 23 Jun 2023 21:22:50 +0300, Hasan Karaman <hk@hasankaraman.dev> wrote:

> What I do is:
>
> make orangepi_zero_defconfig
>
> make menuconfig
>
> Kernel > Linux Kernel Extensions > FB TFT Drivers
>
> https://github.com/notro/fbtft cannot be compiled with mainline kernel.
> So I use my modified version of fbtft driver:
>
> https://github.com/grizzlei/fbtft
>
> And when I replace
> buildoot/output/build/linux-6.1.14/drivers/video/fbdev/fbtft with my
> code, this time i get compilation errors caused by CONFIG_FB_DEFERRED_IO
> macro not being defined. Does FBTFT support depend on other features?
>

Maybe do not use the out of tree version, use the kernel mainline one
(drivers/staging/fbtft) as stated here [1]:

	2015-01-19
	The FBTFT drivers are now in the Linux kernel staging tree:
	https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/fbtft?h=staging-testing
	Development in this github repo has ceased.

Regards,
Peter

[1] https://github.com/notro/fbtft/commit/855b2908380e8ca996768bf94cb4d8573690bc30
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-06-24  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 18:22 [Buildroot] FBTFT extension does not work out of the box Hasan Karaman
2023-06-24  7:30 ` Peter Seiderer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230624093037.1501a619@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=hk@hasankaraman.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox