https://redmine.graphics-muse.org/https://redmine.graphics-muse.org/favicon.ico?16278048512013-10-18T15:14:20ZGraphics Muse Issue TrackerPiBox - Action Item #231: kernel config cleanuphttps://redmine.graphics-muse.org/issues/231?journal_id=7652013-10-18T15:14:20ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Category</strong> set to <i>03 - Linux Kernel</i></li><li><strong>Assignee</strong> set to <i>Hammel</i></li><li><strong>Target version</strong> set to <i>2.0 - Harkonnen</i></li></ul> PiBox - Action Item #231: kernel config cleanuphttps://redmine.graphics-muse.org/issues/231?journal_id=8942014-01-05T01:13:04ZHammelmjhammel@graphics-muse.org
<ul></ul><p>When I get around to this I should have a method of building just the Media Server kernel since this would be a stripped down version of the PiBox Development Platform, which should have nearly everything in it.</p> PiBox - Action Item #231: kernel config cleanuphttps://redmine.graphics-muse.org/issues/231?journal_id=10932014-03-31T03:19:33ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul>Looking through dmesg to see boot times I found the following things:
<ol>
<li>A bunch of eth drivers are compiled in. Only smsc95xx needs to be enabled and even that could be a loadable module.</li>
<li>bcm2708_spi takes 3.5 seconds to load</li>
<li>sda1 (ext4) takes 9 seconds to load</li>
<li>wlan0 takes 8 seconds to load</li>
<li>X (and the fbtft) takes 17 seconds to load</li>
</ol> PiBox - Action Item #231: kernel config cleanuphttps://redmine.graphics-muse.org/issues/231?journal_id=24742019-03-03T18:35:46ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Immediate</i></li><li><strong>Target version</strong> changed from <i>2.0 - Harkonnen</i> to <i>1.1.0 - Upgrades</i></li><li><strong>Severity</strong> changed from <i>03 - Medium</i> to <i>04 - Low</i></li></ul><p>Bumping this to 1.1.0 release because the kernel config has so much cruft in it that PiBox just doesn't need, like all those eth drivers. This is because I switched, a while back, to using the defconfig for the Pis. Now I need to switch back to a trimmed down kernel so save both disk and memory space.</p> PiBox - Action Item #231: kernel config cleanuphttps://redmine.graphics-muse.org/issues/231?journal_id=26512020-02-06T22:22:00ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>10</i> to <i>100</i></li></ul><p>There is a breakdown of the <a href="https://raspberrypi.stackexchange.com/a/24093" class="external">required config options available</a>. This might be a good stripped down version to start with, just to see if it boots.</p>
<p>I looked through the config file for what drivers are compiled in (=y). There are a few areas I could turn off, but a few things, like the eth drivers, may not have any affect according to kconfig descriptions. Also, the kernel is 5M, which is not tiny but it's not bad given all it has to do for something like a media system.</p>
<p>So I'm going to leave the config alone for how. It's not really a problem and the boot time issues are external to the config, at least as of now.</p>
<p>Closing issue.</p>