Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

2014-12-05 Thread John Crispin 
yes, 3.14 is baseline for CC


On 05/12/2014 09:45, Claudio Thomas wrote:
> Hi, do I understand it correctly. For CC is 3.14 planed? Thanks, 
> Claudio
> 
> -- Reviewing OpenWrt BB for Xmodus Systems XM1710E GSM/UMTS Router 
> 
> 
> On 05.12.2014 09:07, John Crispin wrote:
>> i intentionally don't set a date. i have done so in the past and
>> got ranted at for not being on time. this happened with AA and BB
>> so CC is illusive and will be ready when ready. all i will say is
>> that i am already working on it, but you noticed that yourself
>> :)
>> 
>> 
>> On 05/12/2014 02:20, Karl P wrote:
>>> That's the second[2] email I've seen that hints at some sort
>>> of formal date being known for CC, or some plan, or some
>>> detail.
>>> 
>>> It would be appreciated if this magical special knowledge was 
>>> shared a little wider.  I haven't seen _any_ emails or irc 
>>> conversations about _any_ dates or guidelines for any upcoming 
>>> release.  I can't see any release branches.  I don't know
>>> where else I should be looking.
>>> 
>>> Is there some release guidelines that I should know about?
>>> Have there been decisions taken by anyone?  I'm not asking to
>>> be involved in the decision making process, but I would very
>>> much like to know when decisions have been made.
>>> 
>>> Sincerely, Karl P
>>> 
>>> 
>>> 
>>> [2]http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg27746.html
>>>
>>>
>>>
>>>
>>>
>>> 
On 12/04/2014 10:53 PM, John Crispin wrote:
 great, oxnas will now be part of CC :)
 
 On 04/12/2014 23:51, Daniel Golle wrote:
> This reverts commit
> c81de5fd193802d511b42eb7b108aac17136 on
> https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git
> which removed patches and config for 3.14.
> 
> [arm_introduce-dma-fiq-irq-broadcast patch was renamed to 
> match 3.18]
> 
> Signed-off-by: Daniel Golle  --- 
> target/linux/oxnas/config-3.14 | 349 
> + 
> .../010-arm_introduce-dma-fiq-irq-broadcast.patch  |  62
>  ...-obtain-reset-controller-from-device-tree.patch |
> 99 ++ .../250-add-plxtech-vendor-prefix.patch
> |  12 + .../300-introduce-oxnas-platform.patch
> |  79 +
> .../oxnas/patches-3.14/310-oxnas-clocksource.patch |  24 ++
> .../oxnas/patches-3.14/320-oxnas-irqchip.patch |  40 
> +++ .../oxnas/patches-3.14/330-oxnas-pinctrl.patch |
> 32 ++ .../linux/oxnas/patches-3.14/340-oxnas-pcie.patch  |
> 23 ++ .../linux/oxnas/patches-3.14/350-oxnas-reset.patch |
> 20 ++ .../linux/oxnas/patches-3.14/400-oxnas-nand.patch  |
> 28 ++ .../linux/oxnas/patches-3.14/500-oxnas-sata.patch  |
> 30 ++ .../linux/oxnas/patches-3.14/800-oxnas-ehci.patch  |
> 30 ++ .../linux/oxnas/patches-3.14/900-more-boards.patch |
> 16 + 14 files changed, 844 insertions(+) create mode 100644
>  target/linux/oxnas/config-3.14 create mode 100644 
> target/linux/oxnas/patches-3.14/010-arm_introduce-dma-fiq-irq-broadcast.patch
>
>
>
>>
> 
create mode 100644
 target/linux/oxnas/patches-3.14/100-obtain-reset-controller-from-device-tree.patch

>>
 
create mode 100644
> target/linux/oxnas/patches-3.14/250-add-plxtech-vendor-prefix.patch
>
>
>>
> 
create mode 100644
 target/linux/oxnas/patches-3.14/300-introduce-oxnas-platform.patch
>>
 
create mode 100644
> target/linux/oxnas/patches-3.14/310-oxnas-clocksource.patch
>
> 
create mode 100644
> target/linux/oxnas/patches-3.14/320-oxnas-irqchip.patch
> create mode 100644 
> target/linux/oxnas/patches-3.14/330-oxnas-pinctrl.patch
> create mode 100644 
> target/linux/oxnas/patches-3.14/340-oxnas-pcie.patch
> create mode 100644 
> target/linux/oxnas/patches-3.14/350-oxnas-reset.patch
> create mode 100644 
> target/linux/oxnas/patches-3.14/400-oxnas-nand.patch
> create mode 100644 
> target/linux/oxnas/patches-3.14/500-oxnas-sata.patch
> create mode 100644 
> target/linux/oxnas/patches-3.14/800-oxnas-ehci.patch create
>  mode 100644 
> target/linux/oxnas/patches-3.14/900-more-boards.patch
> 
> diff --git a/target/linux/oxnas/config-3.14 
> b/target/linux/oxnas/config-3.14 new file mode 100644 index
>  000..727d81e --- /dev/null +++ 
> b/target/linux/oxnas/config-3.14 @@ -0,0 +1,349 @@ 
> +CONFIG_ALIGNMENT_TRAP=y +# CONFIG_APM_EMULATION is not set
>  +CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y 
> +CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y 
> +CONFIG_ARCH_HAS_RESET_CONTROLLER=y 
> +CONFIG_ARCH_HAS_TICK_BROADCAST=y 
> +CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y 
> +CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y +# 
> CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set 
> +CONFIG_ARCH_NR_GPIO=0 +CONFIG_ARCH_OXNAS=y 
> +CONFIG_ARCH_REQUIRE_GPIOLIB=y +# 
> CONFIG_ARCH_SELECT_MEMORY_MODEL is not set +# 
>

Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

2014-12-05 Thread Claudio Thomas 
Hi, do I understand it correctly. For CC is 3.14 planed?
Thanks,
Claudio

--
Reviewing OpenWrt BB for Xmodus Systems XM1710E GSM/UMTS Router


On 05.12.2014 09:07, John Crispin wrote:
> i intentionally don't set a date. i have done so in the past and got
> ranted at for not being on time. this happened with AA and BB so CC is
> illusive and will be ready when ready. all i will say is that i am
> already working on it, but you noticed that yourself :)
>
>
> On 05/12/2014 02:20, Karl P wrote:
>> That's the second[2] email I've seen that hints at some sort of
>> formal date being known for CC, or some plan, or some detail.
>>
>> It would be appreciated if this magical special knowledge was
>> shared a little wider.  I haven't seen _any_ emails or irc
>> conversations about _any_ dates or guidelines for any upcoming
>> release.  I can't see any release branches.  I don't know where
>> else I should be looking.
>>
>> Is there some release guidelines that I should know about?  Have
>> there been decisions taken by anyone?  I'm not asking to be
>> involved in the decision making process, but I would very much like
>> to know when decisions have been made.
>>
>> Sincerely, Karl P
>>
>>
>>
>> [2]http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg27746.html
>>
>>
>>
>>
>> On 12/04/2014 10:53 PM, John Crispin wrote:
>>> great, oxnas will now be part of CC :)
>>>
>>> On 04/12/2014 23:51, Daniel Golle wrote:
 This reverts commit c81de5fd193802d511b42eb7b108aac17136
 on https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git which
 removed patches and config for 3.14.

 [arm_introduce-dma-fiq-irq-broadcast patch was renamed to
 match 3.18]

 Signed-off-by: Daniel Golle  --- 
 target/linux/oxnas/config-3.14 | 349 
 + 
 .../010-arm_introduce-dma-fiq-irq-broadcast.patch  |  62  
 ...-obtain-reset-controller-from-device-tree.patch |  99
 ++ .../250-add-plxtech-vendor-prefix.patch|  12
 + .../300-introduce-oxnas-platform.patch |  79
 + .../oxnas/patches-3.14/310-oxnas-clocksource.patch |  24
 ++ .../oxnas/patches-3.14/320-oxnas-irqchip.patch |  40
 +++ .../oxnas/patches-3.14/330-oxnas-pinctrl.patch |  32
 ++ .../linux/oxnas/patches-3.14/340-oxnas-pcie.patch  |  23 ++ 
 .../linux/oxnas/patches-3.14/350-oxnas-reset.patch |  20 ++ 
 .../linux/oxnas/patches-3.14/400-oxnas-nand.patch  |  28 ++ 
 .../linux/oxnas/patches-3.14/500-oxnas-sata.patch  |  30 ++ 
 .../linux/oxnas/patches-3.14/800-oxnas-ehci.patch  |  30 ++ 
 .../linux/oxnas/patches-3.14/900-more-boards.patch |  16 + 14
 files changed, 844 insertions(+) create mode 100644 
 target/linux/oxnas/config-3.14 create mode 100644 
 target/linux/oxnas/patches-3.14/010-arm_introduce-dma-fiq-irq-broadcast.patch



> create mode 100644
>>> target/linux/oxnas/patches-3.14/100-obtain-reset-controller-from-device-tree.patch
>>>
> create mode 100644
 target/linux/oxnas/patches-3.14/250-add-plxtech-vendor-prefix.patch


> create mode 100644
>>> target/linux/oxnas/patches-3.14/300-introduce-oxnas-platform.patch
> create mode 100644
 target/linux/oxnas/patches-3.14/310-oxnas-clocksource.patch
 create mode 100644 
 target/linux/oxnas/patches-3.14/320-oxnas-irqchip.patch create
 mode 100644
 target/linux/oxnas/patches-3.14/330-oxnas-pinctrl.patch create
 mode 100644 
 target/linux/oxnas/patches-3.14/340-oxnas-pcie.patch create
 mode 100644
 target/linux/oxnas/patches-3.14/350-oxnas-reset.patch create 
 mode 100644
 target/linux/oxnas/patches-3.14/400-oxnas-nand.patch create
 mode 100644 
 target/linux/oxnas/patches-3.14/500-oxnas-sata.patch create
 mode 100644
 target/linux/oxnas/patches-3.14/800-oxnas-ehci.patch create 
 mode 100644
 target/linux/oxnas/patches-3.14/900-more-boards.patch

 diff --git a/target/linux/oxnas/config-3.14 
 b/target/linux/oxnas/config-3.14 new file mode 100644 index 
 000..727d81e --- /dev/null +++ 
 b/target/linux/oxnas/config-3.14 @@ -0,0 +1,349 @@ 
 +CONFIG_ALIGNMENT_TRAP=y +# CONFIG_APM_EMULATION is not set 
 +CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y 
 +CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y 
 +CONFIG_ARCH_HAS_RESET_CONTROLLER=y 
 +CONFIG_ARCH_HAS_TICK_BROADCAST=y 
 +CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y 
 +CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y +# 
 CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set 
 +CONFIG_ARCH_NR_GPIO=0 +CONFIG_ARCH_OXNAS=y 
 +CONFIG_ARCH_REQUIRE_GPIOLIB=y +#
 CONFIG_ARCH_SELECT_MEMORY_MODEL is not set +#
 CONFIG_ARCH_SPARSEMEM_DEFAULT is not set 
 +CONFIG_ARCH_SUSPEND_POSSIBLE=y
 +CONFIG_ARCH_USE_BUILTIN_BSWAP=y 
 +CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y 
 +CONFIG_ARCH_WANT_GENERAL_HUGETLB=y 
 +CONFIG_ARCH_WANT_IPC_PARSE

Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

2014-12-05 Thread John Crispin 
i intentionally don't set a date. i have done so in the past and got
ranted at for not being on time. this happened with AA and BB so CC is
illusive and will be ready when ready. all i will say is that i am
already working on it, but you noticed that yourself :)


On 05/12/2014 02:20, Karl P wrote:
> That's the second[2] email I've seen that hints at some sort of
> formal date being known for CC, or some plan, or some detail.
> 
> It would be appreciated if this magical special knowledge was
> shared a little wider.  I haven't seen _any_ emails or irc
> conversations about _any_ dates or guidelines for any upcoming
> release.  I can't see any release branches.  I don't know where
> else I should be looking.
> 
> Is there some release guidelines that I should know about?  Have
> there been decisions taken by anyone?  I'm not asking to be
> involved in the decision making process, but I would very much like
> to know when decisions have been made.
> 
> Sincerely, Karl P
> 
> 
> 
> [2]http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg27746.html
>
> 
> 
> 
> On 12/04/2014 10:53 PM, John Crispin wrote:
>> great, oxnas will now be part of CC :)
>> 
>> On 04/12/2014 23:51, Daniel Golle wrote:
>>> This reverts commit c81de5fd193802d511b42eb7b108aac17136
>>> on https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git which
>>> removed patches and config for 3.14.
>>> 
>>> [arm_introduce-dma-fiq-irq-broadcast patch was renamed to
>>> match 3.18]
>>> 
>>> Signed-off-by: Daniel Golle  --- 
>>> target/linux/oxnas/config-3.14 | 349 
>>> + 
>>> .../010-arm_introduce-dma-fiq-irq-broadcast.patch  |  62  
>>> ...-obtain-reset-controller-from-device-tree.patch |  99
>>> ++ .../250-add-plxtech-vendor-prefix.patch|  12
>>> + .../300-introduce-oxnas-platform.patch |  79
>>> + .../oxnas/patches-3.14/310-oxnas-clocksource.patch |  24
>>> ++ .../oxnas/patches-3.14/320-oxnas-irqchip.patch |  40
>>> +++ .../oxnas/patches-3.14/330-oxnas-pinctrl.patch |  32
>>> ++ .../linux/oxnas/patches-3.14/340-oxnas-pcie.patch  |  23 ++ 
>>> .../linux/oxnas/patches-3.14/350-oxnas-reset.patch |  20 ++ 
>>> .../linux/oxnas/patches-3.14/400-oxnas-nand.patch  |  28 ++ 
>>> .../linux/oxnas/patches-3.14/500-oxnas-sata.patch  |  30 ++ 
>>> .../linux/oxnas/patches-3.14/800-oxnas-ehci.patch  |  30 ++ 
>>> .../linux/oxnas/patches-3.14/900-more-boards.patch |  16 + 14
>>> files changed, 844 insertions(+) create mode 100644 
>>> target/linux/oxnas/config-3.14 create mode 100644 
>>> target/linux/oxnas/patches-3.14/010-arm_introduce-dma-fiq-irq-broadcast.patch
>>>
>>>
>>>
>>
>>> 
create mode 100644
>> target/linux/oxnas/patches-3.14/100-obtain-reset-controller-from-device-tree.patch
>>
>>>
>> 
create mode 100644
>>> target/linux/oxnas/patches-3.14/250-add-plxtech-vendor-prefix.patch
>>>
>>>
>>
>>> 
create mode 100644
>> target/linux/oxnas/patches-3.14/300-introduce-oxnas-platform.patch
>>>
>> 
create mode 100644
>>> target/linux/oxnas/patches-3.14/310-oxnas-clocksource.patch
>>> create mode 100644 
>>> target/linux/oxnas/patches-3.14/320-oxnas-irqchip.patch create
>>> mode 100644
>>> target/linux/oxnas/patches-3.14/330-oxnas-pinctrl.patch create
>>> mode 100644 
>>> target/linux/oxnas/patches-3.14/340-oxnas-pcie.patch create
>>> mode 100644
>>> target/linux/oxnas/patches-3.14/350-oxnas-reset.patch create 
>>> mode 100644
>>> target/linux/oxnas/patches-3.14/400-oxnas-nand.patch create
>>> mode 100644 
>>> target/linux/oxnas/patches-3.14/500-oxnas-sata.patch create
>>> mode 100644
>>> target/linux/oxnas/patches-3.14/800-oxnas-ehci.patch create 
>>> mode 100644
>>> target/linux/oxnas/patches-3.14/900-more-boards.patch
>>> 
>>> diff --git a/target/linux/oxnas/config-3.14 
>>> b/target/linux/oxnas/config-3.14 new file mode 100644 index 
>>> 000..727d81e --- /dev/null +++ 
>>> b/target/linux/oxnas/config-3.14 @@ -0,0 +1,349 @@ 
>>> +CONFIG_ALIGNMENT_TRAP=y +# CONFIG_APM_EMULATION is not set 
>>> +CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y 
>>> +CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y 
>>> +CONFIG_ARCH_HAS_RESET_CONTROLLER=y 
>>> +CONFIG_ARCH_HAS_TICK_BROADCAST=y 
>>> +CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y 
>>> +CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y +# 
>>> CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set 
>>> +CONFIG_ARCH_NR_GPIO=0 +CONFIG_ARCH_OXNAS=y 
>>> +CONFIG_ARCH_REQUIRE_GPIOLIB=y +#
>>> CONFIG_ARCH_SELECT_MEMORY_MODEL is not set +#
>>> CONFIG_ARCH_SPARSEMEM_DEFAULT is not set 
>>> +CONFIG_ARCH_SUSPEND_POSSIBLE=y
>>> +CONFIG_ARCH_USE_BUILTIN_BSWAP=y 
>>> +CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y 
>>> +CONFIG_ARCH_WANT_GENERAL_HUGETLB=y 
>>> +CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y +CONFIG_ARM=y +# 
>>> CONFIG_ARM_CPU_SUSPEND is not set +CONFIG_ARM_GIC=y 
>>> +CONFIG_ARM_L1_CACHE_SHIFT=5 +CONFIG_ARM_NR_BANKS=8 
>>> +CONFIG_ARM_PATCH_PHYS_VIRT=y +CONFIG_ARM_THUMB=y 
>>> +CONFIG_ARM_UNWIND=y +CONFIG_ATA=y +CONFIG_AUTO_ZRELADDR=y +# 
>>> CONFIG_BLK_DEV_INITRD is not set +CONFIG_BLK_DE

[OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

2014-12-04 Thread Karl P 
That's the second[2] email I've seen that hints at some sort of formal date 
being known for CC, or some plan, or some detail.


It would be appreciated if this magical special knowledge was shared a little 
wider.  I haven't seen _any_ emails or irc conversations about _any_ dates or 
guidelines for any upcoming release.  I can't see any release branches.  I don't 
know where else I should be looking.


Is there some release guidelines that I should know about?  Have there been 
decisions taken by anyone?  I'm not asking to be involved in the decision making 
process, but I would very much like to know when decisions have been made.


Sincerely,
Karl P



[2]http://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg27746.html


On 12/04/2014 10:53 PM, John Crispin wrote:

great, oxnas will now be part of CC :)

On 04/12/2014 23:51, Daniel Golle wrote:

This reverts commit c81de5fd193802d511b42eb7b108aac17136 on
https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git which removed
patches and config for 3.14.

[arm_introduce-dma-fiq-irq-broadcast patch was renamed to match
3.18]

Signed-off-by: Daniel Golle  ---
target/linux/oxnas/config-3.14 | 349
+
.../010-arm_introduce-dma-fiq-irq-broadcast.patch  |  62 
...-obtain-reset-controller-from-device-tree.patch |  99 ++
.../250-add-plxtech-vendor-prefix.patch|  12 +
.../300-introduce-oxnas-platform.patch |  79 +
.../oxnas/patches-3.14/310-oxnas-clocksource.patch |  24 ++
.../oxnas/patches-3.14/320-oxnas-irqchip.patch |  40 +++
.../oxnas/patches-3.14/330-oxnas-pinctrl.patch |  32 ++
.../linux/oxnas/patches-3.14/340-oxnas-pcie.patch  |  23 ++
.../linux/oxnas/patches-3.14/350-oxnas-reset.patch |  20 ++
.../linux/oxnas/patches-3.14/400-oxnas-nand.patch  |  28 ++
.../linux/oxnas/patches-3.14/500-oxnas-sata.patch  |  30 ++
.../linux/oxnas/patches-3.14/800-oxnas-ehci.patch  |  30 ++
.../linux/oxnas/patches-3.14/900-more-boards.patch |  16 + 14 files
changed, 844 insertions(+) create mode 100644
target/linux/oxnas/config-3.14 create mode 100644
target/linux/oxnas/patches-3.14/010-arm_introduce-dma-fiq-irq-broadcast.patch



create mode 100644
target/linux/oxnas/patches-3.14/100-obtain-reset-controller-from-device-tree.patch

create mode 100644
target/linux/oxnas/patches-3.14/250-add-plxtech-vendor-prefix.patch



create mode 100644
target/linux/oxnas/patches-3.14/300-introduce-oxnas-platform.patch

create mode 100644
target/linux/oxnas/patches-3.14/310-oxnas-clocksource.patch create
mode 100644
target/linux/oxnas/patches-3.14/320-oxnas-irqchip.patch create mode
100644 target/linux/oxnas/patches-3.14/330-oxnas-pinctrl.patch
create mode 100644
target/linux/oxnas/patches-3.14/340-oxnas-pcie.patch create mode
100644 target/linux/oxnas/patches-3.14/350-oxnas-reset.patch create
mode 100644 target/linux/oxnas/patches-3.14/400-oxnas-nand.patch
create mode 100644
target/linux/oxnas/patches-3.14/500-oxnas-sata.patch create mode
100644 target/linux/oxnas/patches-3.14/800-oxnas-ehci.patch create
mode 100644 target/linux/oxnas/patches-3.14/900-more-boards.patch

diff --git a/target/linux/oxnas/config-3.14
b/target/linux/oxnas/config-3.14 new file mode 100644 index
000..727d81e --- /dev/null +++
b/target/linux/oxnas/config-3.14 @@ -0,0 +1,349 @@
+CONFIG_ALIGNMENT_TRAP=y +# CONFIG_APM_EMULATION is not set
+CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
+CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
+CONFIG_ARCH_HAS_RESET_CONTROLLER=y
+CONFIG_ARCH_HAS_TICK_BROADCAST=y
+CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
+CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y +#
CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set
+CONFIG_ARCH_NR_GPIO=0 +CONFIG_ARCH_OXNAS=y
+CONFIG_ARCH_REQUIRE_GPIOLIB=y +# CONFIG_ARCH_SELECT_MEMORY_MODEL
is not set +# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
+CONFIG_ARCH_SUSPEND_POSSIBLE=y +CONFIG_ARCH_USE_BUILTIN_BSWAP=y
+CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
+CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
+CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y +CONFIG_ARM=y +#
CONFIG_ARM_CPU_SUSPEND is not set +CONFIG_ARM_GIC=y
+CONFIG_ARM_L1_CACHE_SHIFT=5 +CONFIG_ARM_NR_BANKS=8
+CONFIG_ARM_PATCH_PHYS_VIRT=y +CONFIG_ARM_THUMB=y
+CONFIG_ARM_UNWIND=y +CONFIG_ATA=y +CONFIG_AUTO_ZRELADDR=y +#
CONFIG_BLK_DEV_INITRD is not set +CONFIG_BLK_DEV_SD=y
+CONFIG_BOOTPARAM_HUNG_TASK_PANIC=y
+CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=1
+CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=y
+CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1 +# CONFIG_CACHE_L2X0 is
not set +CONFIG_CLKDEV_LOOKUP=y +CONFIG_CLKSRC_MMIO=y
+CONFIG_CLKSRC_OF=y +CONFIG_CLKSRC_RPS_TIMER=y
+CONFIG_CLONE_BACKWARDS=y +CONFIG_CMDLINE="console=ttyS0,115200n8
earlyprintk=serial" +CONFIG_COMMON_CLK=y +CONFIG_COMPACTION=y
+CONFIG_CONSOLE_POLL=y +CONFIG_COREDUMP=y +CONFIG_CPU_32v6=y
+CONFIG_CPU_32v6K=y +CONFIG_CPU_ABRT_EV6=y +#
CONFIG_CPU_BPREDICT_DISABLE is not set +CONFIG_CPU_CACHE_V6=y
+CONFIG_CPU_CACHE_VIPT=y +CONFIG_CPU_COPY_V6=y +CONFIG_CPU_CP15=y
+CONFIG_CPU_CP15_MMU=y +CONFIG_CPU_HAS_ASID=y +#
CONFIG_CPU_ICACHE_DI