I suppose because I thought one of the stated aims of Raspbian was to as much like an official debian distribution as possible and all the debian distributions I've had experience of (i386 & armel) have included a packaged default kernel that handles most configurations "out the box". I can see why the foundation would like a small quick loading kernel as their default but not why Raspbian would.SirLagz wrote:Why not just roll your own kernel with the features you need if you already know how to do it ?
Thanks, I guess I'll be investigating that some time soon...Lorian wrote:For the foundation's build they seem to maintain two .config's:
# find . -name *bcmrpi*config -print
The cut-down one builds to about 4Mb and the default one builds to about 6Mb on disk.
This is the intention with the Raspbian kernel. To track the Debian kernel features as close as possible. However, as the kernel package is developed, this will very likely be an iterative process. First, get something working with the changes from the Foundation layered over Debian kernel source. Then refine the configuration to towards alignment with Debian kernel features.chrisw2 wrote:I suppose because I thought one of the stated aims of Raspbian was to as much like an official debian distribution as possible and all the debian distributions I've had experience of (i386 & armel) have included a packaged default kernel that handles most configurations "out the box". I can see why the foundation would like a small quick loading kernel as their default but not why Raspbian would.
Some kernel options are specific to the board in questionchrisw2 wrote: I have no expertise in kernel compilation (although I have done it in the past) but my reasoning was that a stock debian armel kernel from the official debian repositry installed, for instance, on an NSLU2 seems to include a lot of the things asked for in this thread (eg: iptables. NFS kernel server). I, perhaps foolishly, thought it would be easier to add the Raspberry Pi specific stuff to that, than to start with the cut down foundation kernel and add stuff to it as people gradually discover exactly what is missing over a period of time.
Okay, I'll bite... can I be of use to create the proposed config? I might need some guidance on occasions though. Please let me know.plugwash wrote:...
The ideal would be for someone to go through bootc's kernel configuration and the debian kernel configuration from another board, compare them and based on that propose a config that is as debian like as possible but meeting our other constraints. I get the impression that will be a lot of work though.
Code: Select all
Is the format below okay?plugwash wrote:When asking for features can you please tell me the exact options you want setting in the kernel configuration.
I've wondered about u-boot. It's pretty much the standard way almost all other ARM devices boot. I'll have to think some more about it as I'm not really sure what it offers. If it included USB storage drivers it could also facilitate booting an installing from USB media -- although I think u-boot itself will always have to reside on an SD card.jerry.tk wrote:Regarding kernel packaging vs. FAT fs: seems there is some progress in porting U-Boot to RasPi. It already loads kernel from tftp and maybe after a few more iterations it will be able to boot kernel from SD card ext3 partition. I think it would solve some problems with kernel packaging and also installer would profit from that. Not mentioning that we could move to more sane partitioning scheme.
What do you guys think?
What I actually want are actual setting names in the kernel config filechrisw2 wrote: Is the format below okay?
Currently I have set1) Add support for NFS kernel server:
File Systems --->
Network File Systems --->
<M> NFS Server Support
<M> NFS Server Support for NFS version 3
<M> NFS Server Support for NFS version 3 ACL protocol extension
<M> NFS Server Support for NFS version 4
Curently I have set2) Add support for SCSI Tape devices:
Device Drivers --->
SCSI Device Support --->
<M> SCSI Tape Support
currently I have set3) Add support for iptables:
Networking Support --->
Networking Options --->
Network Packet Filtering Framework (netfilter) --->
IP: Netfilter Configuration --->
<M> IP Tables Support
That is great news! Chapeau!plugwash wrote:BTW i'm now building what I hope will be the first kernel to be uploaded to raspbian.
Thank you for this (and all your other work!).plugwash wrote: ...
I think this covers what you have asked for.
which quickly convinced me to stick to using menuconfig and not mess with with things I didn't understand. For any future requests I guess the best way will be to compare & extract the differences between the .config before running menuconfig and .config afterwards.# Automatically generated file; DO NOT EDIT.
This sounds like a bug. Perhaps we can ask them to reverse this firmware change?plugwash wrote: Firstly the latest Pi fimware will no longer boot compressed images, so i'm having to try and adjust the debian packaging to produce an uncompressed kernel.
I doubt it, afaict the kernel basically doesn't contain any floating point codeLuke Wilkinson wrote: Is the stock foundation kernel significantly slowing things down by being built with softpf?
The firmware itself doesn't care about what floating point abi the linux userlandnis using. The closed-source userland libaries for interfacing with the firmware do need seperate builds for hardfloat distros, fortunately the foundation are now providing those.has anyone solved the issue of the closed source firmware being softfp, and will it play nicely with raspbian?
Users browsing this forum: No registered users and 37 guests