Re: [Buildroot] [PATCH] package/wilc-driver: bump version to 2024.04

[Kris Bahnsen via buildroot <buildroot@buildroot.org>]

On Mon, 2024-07-15 at 21:24 +0200, Thomas Petazzoni wrote:
> On Mon, 15 Jul 2024 11:25:13 -0700
> Kris Bahnsen via buildroot <buildroot@buildroot.org> wrote:
> 
> > Be advised that this does NOT support "up to" Linux 6.6. The latest
> > updates from Microchip drop any backwards compatibility support,
> > which
> > is why we have not pushed this up to Buildroot yet.
> > 
> > I think this only will support kernels 6.2~6.6 and currently do not
> > believe it will compile against upstream Linux 6.9 (I tested it a
> > while
> > ago but don't remember the outcome as it wasn't important).
> > 
> > As I mentioned in my previous email responding to build failures,
> > we're
> > working on a solution to be able to handle backwards compatibility
> > with
> > 'backports' but are first catching up on other tasks.
> 
> So what can we do in the mean time? Support a few versions of the
> driver, and let the user chose?

At this time the driver that is in Buildroot, with the patches
submitted by Giulio, I believe will compile up to Linux 6.4. Most of
the testing we did on the latest driver updates was for Linux 6.6
(latest LTS), which did not cleanly compile with the existing patches
from Giulio which is why we pulled in the latest updates from
Microchip.

This patch could be modified to support the older linux4microchip-
2021.10-1 tag on Linux <= 6.4, and linux4microchip-2024.04 tag for
Linux == 6.6 But I'm not sure the best way to go about that other than
adding a Config 'choice' to select between the two, but that would put
the burden on the user to select the correct option.

But the issue also remains that it currently does not compile against
6.9 (I just confirmed this via a test) which I am not greenlit to put
time in to patching the driver solely for 6.9 at this time.

We are working on upstreaming platform support for many of our
products, but with how fiddly the WILC3000 driver is, we're going to
focus on that first so I hope to have a real solution sooner rather
than later.

> 
> Thomas


_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot