On Fri, Jan 19, 2024 at 05:33:23PM +0100, Arnd Bergmann wrote:
> Right, though changing the kernel package to support this
> sounds easier than changing the installer to use a
> foreign architecture kernel package.
Well. It is a "dpkg --add-architecture" in the right spot of
base-installer/debian
On Sat, Jan 13, 2024 at 04:31:35PM +, Dimitri John Ledkov wrote:
> On Fri, 12 Jan 2024, 22:36 Bastian Blank, wrote:
> > On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote:
> > > Disabling debug symbols, enabling debug symbol zstd compression, using
> &g
On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote:
> Disabling debug symbols, enabling debug symbol zstd compression, using
> split debug symbols (disabled BTF usage) should help here.
Disabling debug symbols does not help.
Bastian
> Sent from Ubuntu Pro
> https://ubuntu.com/pr
On Thu, Jan 11, 2024 at 10:50:31AM +0100, John Paul Adrian Glaubitz wrote:
> > As it is now, we will not be able to provide a kernel for maybe all
> > 32bit architectures for Trixie.
> I don't think that this would be a reasonable decision. We're preparing to
> switch
> 32-bit architectures over t
Hi
On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote:
> Disabling debug symbols, enabling debug symbol zstd compression, using
> split debug symbols (disabled BTF usage) should help here.
Okay, maybe more workarounds exist. But none of them look really
promising.
> Separately,
Hi
Linux 6.7 fails to build on at least i386 and armhf. Even it now
manages to make the compiler fail to allocate memory:
| cc1: out of memory allocating 135266296 bytes after a total of 235675648 bytes
Right now both fail on the same driver, so a short team workaround would
be to disable it. B
[dropped some recipients, this mail is not about d-i and the problem at
hand]
Hi
On Wed, Jan 10, 2024 at 08:34:27AM +0100, Arnd Bergmann wrote:
> The most important ARMv5 platform is now probably at91, as
> Microchip still releases new sam9 chips[1] and is going to
> keep supporting it for a whil
Hi
With Linux 6.6 we dropped the Marvell specific kernel image, as it
was not known to work on any of the available devices. We still have
another armel kernel left, the one of the Raspberry Pi 0 and 1, which
uses an ARMv6 CPU.
This also removed all the udebs from armel, which makes many d-i
com
On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote:
> - kernel-image-* packages are now shipping /boot/vmlinuz-* (or
> /boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz
> (respectively /boot/vmlinux).
This was even dependent on architecture. A lot of secondary
Hi
On Sat, Sep 09, 2023 at 11:13:56AM +0200, Paul Gevers wrote:
> 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 kern
On Fri, Apr 27, 2018 at 05:37:25AM +0200, John Paul Adrian Glaubitz wrote:
> Since there are still some repositories that we need for debian-ports
> in the attic, I was wondering whether we should take care of the
> attic stuff and move it over to salsa or github.
Could you show a list? Just migr
On Wed, Jan 27, 2010 at 10:47:55PM +0200, Riku Voipio wrote:
> There is a major problem with gcc 4.4 and armel - the ABI of va_list
> changed (for c++ libraries). We need to decide one of the following:
What exactly have changed? The ABI (as said in the sentence before) or
the mangling.
> 1) li
12 matches
Mail list logo
