All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: franco ariel <fran.millocs@live.com.ar>
Cc: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [HELP] Needed with Downstream Kernel and U-Boot Compilation for Khadas VIM3
Date: Sat, 27 Jul 2024 16:19:45 +0200	[thread overview]
Message-ID: <20240727161945.1d175cb4@windsurf> (raw)
In-Reply-To: <SJ0PR19MB54157D4CF26D0AAB3D719D54D0B52@SJ0PR19MB5415.namprd19.prod.outlook.com>

Hello Franco,

On Sat, 27 Jul 2024 08:05:26 +0000
franco ariel <fran.millocs@live.com.ar> wrote:

> I am seeking help with building a downstream kernel and U-Boot for the Khadas VIM3. Specifically, I am attempting to compile the following repositories and branches:
> 
>   *   Kernel: (https://github.com/khadas/linux.git) khadas-vims-5.4.y<https://github.com/khadas/linux.git> branch
>   *   U-Boot: (https://github.com/khadas/u-boot.git)  khadas-vims-v2015.01<https://github.com/khadas/u-boot.git> branch
> 
> The primary reason for this endeavor is the lack of support for suspend to RAM and resume in the mainline kernel. I have noticed that the Khadas kernel includes the "AMLOGIC_GX_SUSPEND" option, which facilitates suspend compatibility.

Thanks for reaching out to the Buildroot community. However, you should
ask a specific question: what have you tried, what doesn't work?

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-27 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27  8:05 [Buildroot] [HELP] Needed with Downstream Kernel and U-Boot Compilation for Khadas VIM3 franco ariel
2024-07-27 14:19 ` Thomas Petazzoni via buildroot [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=20240727161945.1d175cb4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fran.millocs@live.com.ar \
    --cc=thomas.petazzoni@bootlin.com \
    /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.