All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <foss@0leil.net>
To: Khem Raj <raj.khem@gmail.com>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: Quentin Schulz <foss+yocto@0leil.net>,
	Trevor Woerner <twoerner@gmail.com>,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] [meta-rockchip][PATCH] kernel: linux-yocto: fix broken Ethernet MAC controller on RK3399 on 5.14 >= version <= 5.14.11
Date: Tue, 16 Nov 2021 19:03:29 +0100	[thread overview]
Message-ID: <69C8168A-27F2-4B12-9592-264E80EFBC2D@0leil.net> (raw)
In-Reply-To: <CAMKF1soUeJES6ZG-wvng3VDfW_unw_7Fo4KSPWr3Cr8uR9T=eA@mail.gmail.com>



On November 16, 2021 6:45:05 PM GMT+01:00, Khem Raj <raj.khem@gmail.com> wrote:
>On Tue, Nov 16, 2021 at 9:12 AM Quentin Schulz <
>quentin.schulz@theobroma-systems.com> wrote:
>
>> On Tue, Nov 16, 2021 at 09:08:41AM -0800, Khem Raj wrote:
>> > On Tue, Nov 16, 2021 at 9:04 AM Quentin Schulz
>> > <quentin.schulz@theobroma-systems.com> wrote:
>> > >
>> > > On Tue, Nov 16, 2021 at 09:00:42AM -0800, Khem Raj wrote:
>> > > > On Tue, Nov 16, 2021 at 7:52 AM Quentin Schulz
>> > > > <quentin.schulz@theobroma-systems.com> wrote:
>> > > > >
>> > > > > From Linux kernel v5.14 to v5.14.11 (both included), the Ethernet
>> MAC
>> > > > > controller found on RK3399 is not working.
>> > > > >
>> > > > > A fix is available in v5.14.12 and later (available also in v5.15)
>> > > > > which is provided here and applied to linux-yocto source tree if
>> > > > > linux-yocto version is of the impacted ones.
>> > > > >
>> > > > > The conditional patching is unfortunately required because
>> Honister 3.4
>> > > > > has linux-yocto v5.14.9 and Honister 3.4.1 will have at least
>> > > > > linux-yocto v5.14.14.
>> > > >
>> > > > Patching piece below looks quite a bit.
>> > > > lets just fix v5.14.14 and dont worry about 3.4
>> > > >
>> > >
>> > > v5.14.14 is already fixed. The only release currently is 3.4 and I hit
>> > > that issue, hence the patch.
>> > > I assume not everybody is updating to 3.4.1 when it's out, I've seen
>> > > people running behind dot releases.
>> > > What's bothering you?
>> >
>> > once dot release is out then thats whats maintained not the original
>> > release since they are incremental.
>> > the anon python to apply a patch. Can you explain why we want to patch
>> > applied this way ?
>> >
>>
>> I could define a python function and use it like this:
>> SRC_URI:append:rk3399 = "${@rk3399_fix_mac(d)}"
>>
>> Would that work better for you?
>
>
>I am not yet convinced why should we have such version specific patch
>

If you could explain what's *really* bothering you, I could try to find a proper explanation or agree with you but it's a bit too vague to me right now. Anyway, I'll do some guesses in the next paragraphs.

Because Ethernet does not work for all RK3399-based boards in the latest and only release of Honister?

meta-rockchip is the BSP layer for Rockchip based devices, if not there, where should I put this patch?

Or are we just going to say "Ethernet does not work, we know" to people asking instead of having this patch in? Obviously you could tell them to upgrade their oe-core/poky git repo to rolling honister or 3.4.1 once it's out but having this patch in avoid those questions.

I understand we're talking about policy here. I am not fond of this patch either but Ethernet is quite critical on boards which don't have WiFi for example. I don't have anything better to suggest to fix this in the *latest* release.

Cheers
Quentin
>>
>>
>> Cheers,
>> Quentin
>>


  reply	other threads:[~2021-11-16 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211116153256.3639663-1-quentin.schulz@theobroma-systems.com>
2021-11-16 17:00 ` [yocto] [meta-rockchip][PATCH] kernel: linux-yocto: fix broken Ethernet MAC controller on RK3399 on 5.14 >= version <= 5.14.11 Khem Raj
     [not found]   ` <20211116170406.abau3j6liwsdonbp@fedora>
2021-11-16 17:08     ` Khem Raj
     [not found]       ` <20211116171242.7dyycd3d2qwb4ske@fedora>
2021-11-16 17:45         ` Khem Raj
2021-11-16 18:03           ` Quentin Schulz [this message]
2021-11-16 18:50             ` Khem Raj
     [not found]               ` <20211213090032.dy47s56sykoikbfc@fedora>
2021-12-13 15:04                 ` Khem Raj
2021-12-13 17:18                   ` Quentin Schulz
2021-12-13 17:35                     ` Khem Raj
2021-12-13 22:30                       ` Trevor Woerner

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=69C8168A-27F2-4B12-9592-264E80EFBC2D@0leil.net \
    --to=foss@0leil.net \
    --cc=foss+yocto@0leil.net \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=raj.khem@gmail.com \
    --cc=twoerner@gmail.com \
    --cc=yocto@lists.yoctoproject.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.