Re: armel/marvell kernel size
Hi Roger,
On Tue, Jan 23, 2018 at 06:30:23PM +0000, Ben Hutchings wrote:
> On Mon, 2018-01-22 at 22:38 +0900, Roger Shimizu wrote:
> > Dear Ben,
> >
> > Thanks for keeping armel things rolling for a few releases!
> >
> > On Thu, Jan 18, 2018 at 1:22 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > > On Fri, 2017-10-20 at 15:07 +0100, Ben Hutchings wrote:
> > > > Sadly, linux has again failed to build on armel in experimental due to
> > > > the image size growing too large.
> > >
> > > It's happened again. The compressed image is 1% over the limit.
> >
> > Yes, it's time again.
> >
> > I tried the "CRYPTO_MANAGER2" stuff you mentioned before.
> > Unfortunately, I didn't make it built as module, except after
> > disabling CONFIG_NET, which seems quite ridiculous.
> >
> > Do you know any other option, BTW?
> > I'll continue trying for a while.
>
> There's an upstream change in cfg80211 that enables direct-loading of
> wireless rules, which requires public key crypto in the kernel. There
> doesn't appear to be any option to disable that mode, even though we
> don't need it because crda still works. Maybe you could disable
> wireless networking completely?
>
> Some options that could possibly be changed from y to m:
>
> - I2C, I2C_CHARDEV, I2C_MV64XXX. initramfs-tools should include I2C
> drivers to the initramfs if needed, but I'm not certain.
>
> - MTD, MTD_CMDLINE_PARTS, etc. But I'm pretty sure this will break
> some systems unless initramfs-tools is updated to include and load the
> cmdlinepart module.
>
> - RTC_DRV_MV (and disable RTC_HCTOSYS). There's a udev rule that
> should load the system clock from the first RTC if its driver is a
> module.
>
> - SPI_ORION. initramfs-tools should include this in the initramfs if
> needed, but I'm not certain.
>
> Some options that could possibly be disabled:
>
> - AUDIT. This is quite a niche feature.
>
> Also try comparing the complete configs over time and looking for
> symbols newly set to y.
Did you had a chance to look at Ben's suggestions or ideas?
We would like to ideally upload a 4.15.x based version to unstable
(currently imported 4.15.4).
Regards,
Salvatore
Reply to: