All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Albert Jose Silva Tovar <albertsilva.26@hotmail.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Pantalla tactil - hycon-hy46xx.c
Date: Sat, 30 Apr 2022 23:42:24 +0200	[thread overview]
Message-ID: <84cb64cf-fed9-fc33-a811-b6d60a8d49a3@benettiengineering.com> (raw)
In-Reply-To: <ROAP284MB12483B83EF9C7269C235ABD988FC9@ROAP284MB1248.BRAP284.PROD.OUTLOOK.COM>

Hi Albert,

I add Buildroot ML in Cc since it's in a good part Buildroot related and 
other people can help too,

On 29/04/22 14:28, Albert Jose Silva Tovar wrote:
> Good afternoon Julio,
> 
> I am writing to you because of a contribution you made on this website:
> https://github.com/torvalds/linux/blob/master/drivers/input/touchscreen/hycon-hy46xx.c 
> <https://github.com/torvalds/linux/blob/master/drivers/input/touchscreen/hycon-hy46xx.c>
> 
> I would like to ask you a question! I have a builroot OS and I would 
> like to integrate this drivers to it, the sources that you use, in 
> principle where would I have to put them or what would be the process of 
> adapting the driver?

I think you're using a Linux version without the hycon driver, so what 
you can do is to patch the kernel you're using by adding the patch to 
Buildroot for Linux.

So you have to:
1. clone kernel git and checkout the version you're using or directly 
use your own kernel repository if any
2. clone mainline kernel
3. extract my patches from the cloned mainline kernel with:
"git format-patch" command
4. copy the patches to your buildroot/board/company/linux like this:
 
https://github.com/buildroot/buildroot/tree/master/board/seeed/stm32mp157c-odyssey/patches
5. use the BR2_GLOBAL_PATCH_DIR variable in your Buildroot defconfig, 
like this:
 
https://github.com/buildroot/buildroot/blob/master/configs/stm32mp157c_odyssey_defconfig#L3
6. rebuild Buildroot

That is the way I would do it.

Which Linux version are you using?

Feel free to ask me more help also regarding the driver itself if you 
encounter problems with back-porting my patches.

Best regards
-- 
Giulio Benetti
Benetti Engineering sas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2022-04-30 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ROAP284MB12483B83EF9C7269C235ABD988FC9@ROAP284MB1248.BRAP284.PROD.OUTLOOK.COM>
2022-04-30 21:42 ` Giulio Benetti [this message]
     [not found] <ROAP284MB1248F81EBC538A6664E4DBC088FE9@ROAP284MB1248.BRAP284.PROD.OUTLOOK.COM>
2022-05-01 16:57 ` [Buildroot] Pantalla tactil - hycon-hy46xx.c Giulio Benetti

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=84cb64cf-fed9-fc33-a811-b6d60a8d49a3@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=albertsilva.26@hotmail.com \
    --cc=buildroot@buildroot.org \
    /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 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.