Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #60229
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Re: armel/marvell kernel size |
| Date | 2018-02-17 13:50 +0100 |
| Message-ID | <vka6d-72h-5@gated-at.bofh.it> (permalink) |
| References | <uCG9P-4Kh-1@gated-at.bofh.it> <v99ZT-mH-5@gated-at.bofh.it> <vaKNH-5y0-13@gated-at.bofh.it> <vbbEf-5Ms-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2017-10-20 16:10 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2017-10-23 17:40 +0200
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2017-10-26 23:10 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2017-10-29 18:20 +0100
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-01-18 05:30 +0100
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-01-22 15:00 +0100
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-01-23 19:40 +0100
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-01-26 19:00 +0100
Re: armel/marvell kernel size Salvatore Bonaccorso <carnil@debian.org> - 2018-02-17 13:50 +0100
Re: armel/marvell kernel size Bastian Blank <waldi@debian.org> - 2018-02-17 14:20 +0100
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-03-22 13:00 +0100
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-03-22 13:00 +0100
Re: armel/marvell kernel size Rogério Brito <rbrito@gmail.com> - 2018-03-22 19:20 +0100
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-23 00:10 +0100
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-24 03:00 +0100
Re: armel/marvell kernel size Rogério Brito <rbrito@gmail.com> - 2018-03-27 07:50 +0200
Re: armel/marvell kernel size Stefan Monnier <monnier@iro.umontreal.ca> - 2018-03-27 14:40 +0200
Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 22:30 +0200
Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-03-27 22:50 +0200
Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 23:30 +0200
Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-03-28 11:30 +0200
Re: armel/marvell kernel size Federico Pietro Briata <federico@briata.org> - 2018-03-28 14:30 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-01 15:30 +0200
Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-04-03 08:00 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-07 16:20 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-07 17:00 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-13 02:10 +0200
Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-15 18:30 +0200
Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-04-02 01:50 +0200
Re: armel/marvell kernel size Stefan Monnier <monnier@iro.umontreal.ca> - 2018-03-27 23:30 +0200
Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-27 21:10 +0200
Re: armel not to be released anymore? (was: armel/marvell kernel size) Ben Hutchings <ben@decadent.org.uk> - 2018-03-27 21:30 +0200
armel not to be released anymore? (was: armel/marvell kernel size) "W. Martin Borgert" <debacle@debian.org> - 2018-03-27 21:40 +0200
Re: armel not to be released anymore? (was: armel/marvell kernel size) Paul Wise <pabs@debian.org> - 2018-03-28 06:40 +0200
Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 22:50 +0200
csiph-web