From: Tanvir Roshid <tanvir.roshid@codethink.co.uk>
To: linux-embedded@vger.kernel.org
Subject: Re: Linux Kernel (megi patches for PinePhone Pro)
Date: Tue, 12 Mar 2024 16:34:18 +0000 [thread overview]
Message-ID: <cfaa5c50-fc76-4766-8ace-4c92820d3baa@codethink.co.uk> (raw)
In-Reply-To: <a5b7e74f-fad6-4a07-a2cc-614cdb75046e@codethink.co.uk>
On 12/03/2024 16:30, Tanvir Roshid wrote:
> Hi,
>
> I hope you are well.
>
> I wanted to post this message to discuss the megous kernel and
> communicate with the embedded Linux community. This post is my first
> attempt at using the Linux mailing list, so forgive me if I make any
> mistakes.
>
> For context, the megous kernel is a fork of the Torvald kernel
> containing patches to enable the PinePhone and PinePhone Pro to boot
> correctly.
>
> The megous kernel disappeared earlier this year. We have spent the
> better part of the year getting the phones to boot with the upstream
> kernel for GNOME OS. We successfully confirmed working boards using
> patches found on this repo:
> -
> https://gitlab.com/pine64-org/linux/-/tree/linux-pinephonepro-6.6.y?ref_type=heads
>
> The work is visible here:
> - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/2455
>
> I am aware that a new fork replacing the megous kernel exists here:
> - https://github.com/sailfish-on-dontbeevil/kernel-megi
>
> The GNOME community would prefer not to rely on a custom kernel and
> use the upstream version to avoid a repeat of the megous kernel and
> its disappearance. Recently, the patches have understandably failed to
> apply to the new kernel. We would prefer not to upstream these patches
> for long-term maintainability versus continuous maintenance.
Apologies; my sentence was not clear here. I mean to state "We would
prefer to upstream these patches for long-term maintainability versus
continuous maintenance. "
>
> My question to the embedded community is:
> - What is preventing the upstream kernel from integrating these patches?
>
> From research (https://news.ycombinator.com/item?id=30015412), I can
> see that these patches present problems. However, we would like to
> know more specifics to eventually upstream these patches via
> additional work.
>
> Kind regards,
> Tanvir Roshid
>
>
prev parent reply other threads:[~2024-03-12 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:30 Linux Kernel (megi patches for PinePhone Pro) Tanvir Roshid
2024-03-12 16:34 ` Tanvir Roshid [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=cfaa5c50-fc76-4766-8ace-4c92820d3baa@codethink.co.uk \
--to=tanvir.roshid@codethink.co.uk \
--cc=linux-embedded@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).