[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems



On Sun, Sep 10, 2023 at 05:13:52PM +0200, Ben Hutchings wrote:
> On Sat, 2023-09-09 at 11:13 +0200, Paul Gevers wrote:
> > Hi Salvatore,
> > 
> > On 09-09-2023 10:15, Salvatore Bonaccorso wrote:
> > > but should have been support for armel been
> > > dropped earlier and should we do it for trixie
> > 
> > The kernel for armel went over some hardware limits before (I was 
> > affected with my NAS, where I couldn't upgrade the kernel to bullseye as 
> > documented in the release notes [1]). Is the current situation reaching 
> > the limit for all armel devices, or "just" for some and are the others 
> > probably fine for some years to come?
> 
> The issue exists with many devices supported by the "marvell" flavour.
> We also have an "rpi" flavour for armel that supports Raspberry Pi
> models with Arm v6 CPUs, and that doesn't have any size limits that
> we've needed to worry about yet.

I happily delayed the issue by changing the layout of the mtd partitions
of my QNAP with a nice script [0]. It's able to handle a good number
of models and I think it's a great solution for the short/medium term.

> > If we're now reaching the final limit and if it was foreseeable that we 
> > would reach that limit, then yes it would have made sense to drop armel 
> > *before* the bookworm release, but alas. If the kernel team can't 
> > support the kernel on armel, than armel shouldn't be a release 
> > architecture for trixie. If it's only some devices, than we "just" need 
> > to communicate that clearly.
> [...]
> 
> I would be quite happy to drop the "marvell" flavour for trixie.  The
> size limits are a recurring problem, and the supported SoCs and devices
> seem to have been out of production for a long time.  In contrast, the
> Raspberry Pi models with v6 CPUs are still in production.

I would find reasonable if trixie dropped "marvell" flavor. The bell
for the armel QNAP devices has been warning for years already, anybody
caring of their data should move it somewhere else.

> (I do have my doubts as to whether it will be possible to continue
> supporting a useful user-space for armel, but I certainly can't speak
> authoritatively about that.)
> 
> Ben.
> 
> -- 
> Ben Hutchings - Debian developer, member of kernel, installer and LTS
> teams

[0] https://github.com/amouiche/qnap_mtd_resize_for_bullseye

-- 
rsa4096: 3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13
ed25519: FFB4 0CC3 7F2E 091D F7DA  356E CC79 2832 ED38 CB05

Attachment: signature.asc
Description: PGP signature


Reply to: