← Back to team overview

ac100 team mailing list archive

Re: kernel config differences between default and Ubuntu

 

Thank,
Just to clarify, when you say 'not needed, kill it'  you mean it
should be disabled in paz00_defconfig right? :)
The Ubuntu packaging branch does not have them enabled
Jani

On Tue, Jan 10, 2012 at 7:41 PM, Marc Dietrich <marvin24@xxxxxx> wrote:
> On Tuesday 10 January 2012 17:16:26 Jani Monoses wrote:
>> Hello,
>>
>> There are still quite a few config options that were never synced up
>> or were dropped compared to the default paz00 config in the git ac100
>> kernel tree.
>>
>> I ran this command locally
>> diff -u <(grep "^CONF" arch/arm/configs/paz00_defconfig|cut -f1
>> -d=|sort) <(grep "^CONF" debian.linaro/config/config.common.ubuntu|cut
>> -f 1 -d=|sort ) |grep "-"
>>
>> and got this:
>>
>> Any in particular that should absolutely be there? I could just add
>> them all I guess but wanted to make sure they are all intended and to
>> know why
>> certain settings are on. For istance I am not sure the various
>> debugging options are set in other Ubuntu kernels and I want to keep
>> the delta low
>> DEV_DM had build issues when I switched to the 3.0 tree, and have not
>> tried since, hence it being off.
>> IIRC PCI was not needed either but it is enabled by default in defconfig.
>>
>> Any input is welcome :)
>>
>> -CONFIG_ARM_ERRATA_751472
>
> Our SoC is affected by this erratum, so it should be enabled
>
>> -CONFIG_BATTERY_BQ20Z75
>
> We don't have this, kill it.
>
>> -CONFIG_BLK_DEV_DM
>> -CONFIG_BOOTPARAM_HUNG_TASK_PANIC
>> -CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC
>
> I think these can be killed
>
>> -CONFIG_CHARGER_GPIO
>
> We don't have this, kill it.
>
>> -CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND
>
> I think we want PERFORMANCE here, ondemand will be actived later in the boot
> process.
>
>> -CONFIG_CRYPTO_USER_API_HASH
>> -CONFIG_CRYPTO_USER_API_SKCIPHER
>
> kill these
>
>> -CONFIG_DEBUG_DEVRES
>> -CONFIG_DEBUG_SPINLOCK
>> -CONFIG_DEBUG_SPINLOCK_SLEEP
>
> These are not necessary.
>
>> -CONFIG_DM_VERITY
>> -CONFIG_DM_VERITY_CHROMEOS
>
> What's that? Maybe ChromeOS specific -> kill
>
>> @@ -90,236 +393,1245 @@
>> -CONFIG_HIGHMEM
>
> not sure about this one, wait for an expert ...
>
>> -CONFIG_KERNEL_LZO
>
> yes, I prefer LZO over GZ because it uncompresses faster AFAIK, increasing
> boot speed. I leave it up to you.
>
>> -CONFIG_KEYS_DEBUG_PROC_KEYS
>> -CONFIG_LOCKUP_DETECTOR
>
> debugging stuff ... not needed for release
>
>> -CONFIG_MEDIA_CONTROLLER
>
> looks like our camera does not need it -> kill
>
>> -CONFIG_MMC_SDHCI_OF
>
> well, no OpenFirmware yet -> kill
>
>> -CONFIG_MODULE_FORCE_UNLOAD
>> -CONFIG_NET_KEY
>> -CONFIG_NFS_FSCACHE
>> -CONFIG_NFS_USE_NEW_IDMAPPER
>> -CONFIG_NFS_V4_1
>> -CONFIG_NL80211_TESTMODE
>> -CONFIG_PREEMPT_VOLUNTARY
>> -CONFIG_RD_XZ
>> -CONFIG_SCSI_SPI_ATTRS
>> -CONFIG_SECCOMP_FILTER
>> -CONFIG_SERIAL_OF_PLATFORM
>> -CONFIG_SLAB
>
> well, I leave these up to you. Personally, I like nfs ...
> SERIAL_OF_PLATFORM is not needed
> and memory allocator, preemption ... ask someone else ;-)
>
>> -CONFIG_TEGRA_DEBUG_UARTB
>
> mmh, should be UARTA
>
>> -CONFIG_TEGRA_PCI
>
> please leave this on (for powermgnmt reasons)
>
>> -CONFIG_USB_DEVICEFS
>> -CONFIG_USB_MON
>
> double kill
>
>> -CONFIG_USB_OTG
>
> mmh, I don't know if it is working. Well if someone wants to try, he need to
> build his own kernel anyway -> zap it
>
>> -CONFIG_VIDEO_HELPER_CHIPS_AUTO
>
> I wanted to get rid of the various tuners. In fact we need none of them. But
> somehow this didn't worked, kernel still compiles the tuners. Maybe try
> without?
>
>
> Marc
>


Follow ups

References