Message ID | 1450196875-6739-1-git-send-email-ynvich@gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Tuesday 15 December 2015 19:27:50 Sergei Ianovich wrote: > .../devicetree/bindings/vendor-prefixes.txt | 1 + > arch/arm/boot/dts/Makefile | 3 + > arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts | 50 ++++ > arch/arm/boot/dts/pxa27x-lp8x4x.dts | 259 +++++++++++++++++++++ > arch/arm/configs/lp8x4x_defconfig | 176 ++++++++++++++ > I had not noticed earlier that you are adding a new defconfig file. PXA is already the platform with the most defconfig files, and I'd rather like to see that reduced than increased. Is there a chance you could merge this one with some of the existing files into one configuration that handles them all? Arnd
On Tue, 2015-12-15 at 17:32 +0100, Arnd Bergmann wrote: > On Tuesday 15 December 2015 19:27:50 Sergei Ianovich wrote: > > .../devicetree/bindings/vendor-prefixes.txt | 1 + > > arch/arm/boot/dts/Makefile | 3 + > > arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts | 50 ++++ > > arch/arm/boot/dts/pxa27x-lp8x4x.dts | 259 > > +++++++++++++++++++++ > > arch/arm/configs/lp8x4x_defconfig | 176 > > ++++++++++++++ > > > > I had not noticed earlier that you are adding a new defconfig file. > PXA is > already the platform with the most defconfig files, and I'd rather > like > to see that reduced than increased. > > Is there a chance you could merge this one with some of the existing > files > into one configuration that handles them all? There are several board-specific devices on LP8x4x: custom FPGA, custom UART, custom IRQ on FPGA, custom parallel bus for industrial IO. The defconfig file could alert potential users to this fact. If this is not a sufficient reason to have a defconfig file, it can be dropped. I use the full .config anyway :)
On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote: > On Tue, 2015-12-15 at 17:32 +0100, Arnd Bergmann wrote: > > On Tuesday 15 December 2015 19:27:50 Sergei Ianovich wrote: > > > .../devicetree/bindings/vendor-prefixes.txt | 1 + > > > arch/arm/boot/dts/Makefile | 3 + > > > arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts | 50 ++++ > > > arch/arm/boot/dts/pxa27x-lp8x4x.dts | 259 > > > +++++++++++++++++++++ > > > arch/arm/configs/lp8x4x_defconfig | 176 > > > ++++++++++++++ > > > > > > > I had not noticed earlier that you are adding a new defconfig file. > > PXA is > > already the platform with the most defconfig files, and I'd rather > > like > > to see that reduced than increased. > > > > Is there a chance you could merge this one with some of the existing > > files > > into one configuration that handles them all? > > There are several board-specific devices on LP8x4x: custom FPGA, custom > UART, custom IRQ on FPGA, custom parallel bus for industrial IO. The > defconfig file could alert potential users to this fact. If this is not > a sufficient reason to have a defconfig file, it can be dropped. > > I use the full .config anyway I would like those drivers to be enabled in some defconfig, so we get compile-time coverage, but we generally stopped having one-config-per-board files. Maybe we can have a pxa_defconfig file that enables lots of boards and then we remove the individual configs? We don't have to remove them all at once, but it would make me very happy if we could at least kill off some of the ones that are not used regularly. Arnd
On Tue, 2015-12-15 at 18:02 +0100, Arnd Bergmann wrote: > On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote: > > There are several board-specific devices on LP8x4x: custom FPGA, > > custom > > UART, custom IRQ on FPGA, custom parallel bus for industrial IO. The > > defconfig file could alert potential users to this fact. If this is > > not > > a sufficient reason to have a defconfig file, it can be dropped. > > > > I use the full .config anyway > > I would like those drivers to be enabled in some defconfig, so we get > compile-time coverage, but we generally stopped having one-config-per- > board > files. > > Maybe we can have a pxa_defconfig file that enables lots of boards > and then we remove the individual configs? We don't have to remove > them all at once, but it would make me very happy if we could at > least kill off some of the ones that are not used regularly. lp8x4x seems to be the first pxa board which requires DT. We can create pxa27x-dt_defconfig which selects: 1. PXA27X_DT 2. PXA_FB and 8250_PXA to enable console 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC 4. all optional pxa stuff as modules 5. all stuff on supported pxa boards as modules If #5 is extended when support for new boards is added, it should be possible to run any supported pxa27x board with pxa27x_defconfig.
Sergei Ianovich <ynvich@gmail.com> writes: > On Tue, 2015-12-15 at 18:02 +0100, Arnd Bergmann wrote: >> On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote: >> > There are several board-specific devices on LP8x4x: custom FPGA, >> > custom >> > UART, custom IRQ on FPGA, custom parallel bus for industrial IO. The >> > defconfig file could alert potential users to this fact. If this is >> > not >> > a sufficient reason to have a defconfig file, it can be dropped. >> > >> > I use the full .config anyway >> >> I would like those drivers to be enabled in some defconfig, so we get >> compile-time coverage, but we generally stopped having one-config-per- >> board >> files. >> >> Maybe we can have a pxa_defconfig file that enables lots of boards >> and then we remove the individual configs? We don't have to remove >> them all at once, but it would make me very happy if we could at >> least kill off some of the ones that are not used regularly. Yeah, I'd be happy too, that would simplify also my life. Actually I was thinking of 2 defconfigs : - one for platform_data based boards pxa2xx - one for DT only boards pxa2xx > lp8x4x seems to be the first pxa board which requires DT. Most probably AFAIK. > We can create pxa27x-dt_defconfig which selects: > 1. PXA27X_DT > 2. PXA_FB and 8250_PXA to enable console > 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC If you put MMC_PXA, one can argue why not any MTD device used on pxa devices, such as pxa2xx-flash or docg3/docg4, etc ... I won't argue, I'm just pondering about the right choice. > 4. all optional pxa stuff as modules > 5. all stuff on supported pxa boards as modules > If #5 is extended when support for new boards is added, it should be > possible to run any supported pxa27x board with pxa27x_defconfig. I'm very eager to see a patch on that. I can feed my Jenkins with it, it would greatly help me catch issues earlier. Moreover it would for free test it on lubbock, mainstone and mioa701. If there was one also for pxa3xx, I would launch it on zylonite cm-x300 ... (that's a bonus, I know :)) Cheers.
On Tue, 2015-12-15 at 19:06 +0100, Robert Jarzmik wrote: > > > > Maybe we can have a pxa_defconfig file that enables lots of boards > > > and then we remove the individual configs? We don't have to remove > > > them all at once, but it would make me very happy if we could at > > > least kill off some of the ones that are not used regularly. > Yeah, I'd be happy too, that would simplify also my life. > > Actually I was thinking of 2 defconfigs : > - one for platform_data based boards pxa2xx > - one for DT only boards pxa2xx I sincerely hope that dealing with ancient platform_data defconfigs is out of the scope this patch. > > lp8x4x seems to be the first pxa board which requires DT. > Most probably AFAIK. > > > We can create pxa27x-dt_defconfig which selects: > > 1. PXA27X_DT > > 2. PXA_FB and 8250_PXA to enable console > > 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC > If you put MMC_PXA, one can argue why not any MTD device used on pxa > devices, > such as pxa2xx-flash or docg3/docg4, etc ... I won't argue, I'm just > pondering > about the right choice. Great point. We should enable MTD for sure. There is no PXA-specific MTD drivers, however. That's why MTD failed the grep test. > > 4. all optional pxa stuff as modules > > 5. all stuff on supported pxa boards as modules > > > If #5 is extended when support for new boards is added, it should be > > possible to run any supported pxa27x board with pxa27x_defconfig. > > I'm very eager to see a patch on that. I can feed my Jenkins with it, > it would > greatly help me catch issues earlier. Moreover it would for free test > it on > lubbock, mainstone and mioa701. If there was one also for pxa3xx, I > would launch > it on zylonite cm-x300 ... (that's a bonus, I know :)) > Updated plan: 1. MACH_PXA27X_DT 2. PXA_FB and 8250_PXA to enable console 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC 3.1. MTD, MTD_CFI, MTD_PHYSMAP_OF and JFFS2_FS to enable boot from MTD 4. all optional pxa stuff as modules 5. all stuff on supported pxa boards as modules 6. supported boards should boot the kernel built with `pxa27x-dt_defconfig` after `make olddefconfig` It is probably a good idea to put this plan somewhere in Documentation/ and to have a comment about that in the defconfig itself. Is the plan acceptable?
On Tuesday 15 December 2015 21:50:13 Sergei Ianovich wrote: > On Tue, 2015-12-15 at 19:06 +0100, Robert Jarzmik wrote: > > > 4. all optional pxa stuff as modules > > > 5. all stuff on supported pxa boards as modules > > > > > If #5 is extended when support for new boards is added, it should be > > > possible to run any supported pxa27x board with pxa27x_defconfig. > > > > I'm very eager to see a patch on that. I can feed my Jenkins with it, > > it would > > greatly help me catch issues earlier. Moreover it would for free test > > it on > > lubbock, mainstone and mioa701. If there was one also for pxa3xx, I > > would launch > > it on zylonite cm-x300 ... (that's a bonus, I know :)) > > > > Updated plan: > 1. MACH_PXA27X_DT > 2. PXA_FB and 8250_PXA to enable console > 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC > 3.1. MTD, MTD_CFI, MTD_PHYSMAP_OF and JFFS2_FS to enable boot from MTD > 4. all optional pxa stuff as modules > 5. all stuff on supported pxa boards as modules > 6. supported boards should boot the kernel built with > `pxa27x-dt_defconfig` after `make olddefconfig` > > It is probably a good idea to put this plan somewhere in Documentation/ > and to have a comment about that in the defconfig itself. > > Is the plan acceptable? Sounds good to me. Arnd
Arnd Bergmann <arnd@arndb.de> writes: > On Tuesday 15 December 2015 21:50:13 Sergei Ianovich wrote: >> On Tue, 2015-12-15 at 19:06 +0100, Robert Jarzmik wrote: >> Updated plan: >> 1. MACH_PXA27X_DT >> 2. PXA_FB and 8250_PXA to enable console What about gpio-pxa ? And maybe pinctrl-pxa27x (only in linux-next by now) ? Can a pxafb work without gpio-pxa ? Also usually for pxafb you have pwm and pwm_bl to see something. >> 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC >> 3.1. MTD, MTD_CFI, MTD_PHYSMAP_OF and JFFS2_FS to enable boot from MTD Ok. Is pxa2xx-pcmcia out of scope ? I seem to remember we have several boards where pcmcia is the rootfs (even if that is a small mess right now I still have to work on). Or do we consider pcmcia as obsolete ? >> 4. all optional pxa stuff as modules >> 5. all stuff on supported pxa boards as modules >> 6. supported boards should boot the kernel built with >> `pxa27x-dt_defconfig` after `make olddefconfig` >> >> It is probably a good idea to put this plan somewhere in Documentation/ >> and to have a comment about that in the defconfig itself. >> >> Is the plan acceptable? > > Sounds good to me. Sounds good to me too. Cheers.
On Tuesday 15 December 2015 21:01:35 Robert Jarzmik wrote: > Arnd Bergmann <arnd@arndb.de> writes: > > > On Tuesday 15 December 2015 21:50:13 Sergei Ianovich wrote: > >> On Tue, 2015-12-15 at 19:06 +0100, Robert Jarzmik wrote: > >> Updated plan: > >> 1. MACH_PXA27X_DT > >> 2. PXA_FB and 8250_PXA to enable console > What about gpio-pxa ? And maybe pinctrl-pxa27x (only in linux-next by now) ? Can > a pxafb work without gpio-pxa ? Also usually for pxafb you have pwm and pwm_bl > to see something. > > >> 3. MMC, MMC_PXA and EXT4_FS to enable boot from MMC > >> 3.1. MTD, MTD_CFI, MTD_PHYSMAP_OF and JFFS2_FS to enable boot from MTD > Ok. Is pxa2xx-pcmcia out of scope ? I seem to remember we have several boards > where pcmcia is the rootfs (even if that is a small mess right now I still have > to work on). Or do we consider pcmcia as obsolete ? I'm definitely fine with tossing in everything that is PXA specific, even if it's rarely used. If someone wants a smaller kernel, they can still start out with the defconfig and disable stuff they don't need, which tends to be easier than the opposite, and it gives us compile-time coverage with the autobuilders that compile every defconfig. Arnd
Arnd Bergmann <arnd@arndb.de> writes: > I would like those drivers to be enabled in some defconfig, so we get > compile-time coverage, but we generally stopped having one-config-per-board > files. > > Maybe we can have a pxa_defconfig file that enables lots of boards > and then we remove the individual configs? We don't have to remove > them all at once, but it would make me very happy if we could at > least kill off some of the ones that are not used regularly. I'll take that part, the pxa_defconfig which covers all pxa boards in arch/arm/mach-pxa. I have a prototype, which of course doesn't boot on any of my pxa platforms (breaks in the very early bootstrap code I think, DEBUG_LL is the next stage). Actually I've not even looked if a single kernel covering pxa2xx and pxa3xx is possible (since recently clock handling was a blocker). Once I have something that at least shows me a sign of life, I'll submit an RFC patch. This work will be orthogonal to Sergei's one, as it is aimed at having one defconfig compiling all mach-pxa/*.c files and the drivers referenced by them. This won't allow removing defconfig files until I have a good idea why my boards are not booting (lubbock, mainstone, mioa701, zylonite, cm-x300). Cheers.
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt index 55df1d4..2f1b078 100644 --- a/Documentation/devicetree/bindings/vendor-prefixes.txt +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt @@ -109,6 +109,7 @@ honeywell Honeywell hp Hewlett Packard i2se I2SE GmbH ibm International Business Machines (IBM) +icpdas ICP DAS CO., LTD. idt Integrated Device Technologies, Inc. iom Iomega Corporation img Imagination Technologies Ltd. diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile index 30bbc37..ed182ea 100644 --- a/arch/arm/boot/dts/Makefile +++ b/arch/arm/boot/dts/Makefile @@ -499,6 +499,9 @@ dtb-$(CONFIG_ARCH_ORION5X) += \ orion5x-rd88f5182-nas.dtb dtb-$(CONFIG_ARCH_PRIMA2) += \ prima2-evb.dtb +dtb-$(CONFIG_MACH_PXA27X_DT) += \ + pxa27x-lp8x4x.dtb \ + pxa27x-lp8x4x-i105.dtb dtb-$(CONFIG_ARCH_QCOM) += \ qcom-apq8064-cm-qs600.dtb \ qcom-apq8064-ifc6410.dtb \ diff --git a/arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts b/arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts new file mode 100644 index 0000000..903f5c7 --- /dev/null +++ b/arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts @@ -0,0 +1,50 @@ +/* Device tree for ICP DAS LP-8x4x i105 flavor */ + +#include "pxa27x-lp8x4x.dts" + +/ { + extbus { + flash@0 { + compatible = "cfi-flash"; + reg = <0 0 0x04000000>; + bank-width = <4>; + device-width = <2>; + + partitions { + #address-cells = <1>; + #size-cells = <1>; + fs@0 { + label = "u-boot"; + reg = <0 0x40000>; + }; + fs@40000 { + label = "settings"; + reg = <0x40000 0x40000>; + }; + fs@80000 { + label = "device_tree"; + reg = <0x80000 0x40000>; + }; + fs@c0000 { + label = "kernel"; + reg = <0xc0000 0x2c0000>; + }; + fs@300000 { + label = "root_fs"; + reg = <0x380000 0x3c80000>; + }; + }; + }; + + flash@1 { + compatible = "cfi-flash"; + reg = <1 0x0 0x02000000>; + bank-width = <2>; + device-width = <1>; + partitions { + #address-cells = <1>; + #size-cells = <1>; + }; + }; + }; +}; diff --git a/arch/arm/boot/dts/pxa27x-lp8x4x.dts b/arch/arm/boot/dts/pxa27x-lp8x4x.dts new file mode 100644 index 0000000..7f33912c --- /dev/null +++ b/arch/arm/boot/dts/pxa27x-lp8x4x.dts @@ -0,0 +1,259 @@ +/* Device tree for ICP DAS LP-8x4x */ +/dts-v1/; + +#include "pxa27x.dtsi" + +/ { + model = "ICP DAS LP-8x4x programmable automation controller"; + compatible = "icpdas,lp8x4x", "marvell,pxa270"; + + aliases { + ethernet0 = ð0; + ethernet1 = ð1; + }; + + memory { + reg = <0xa0000000 0x08000000>; + }; + + regulators { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <0>; + + vmmc: regulator@0 { + compatible = "regulator-fixed"; + reg = <0>; + regulator-name = "vmmc"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + }; + }; + + pxabus { + pxairq: interrupt-controller@40d00000 { + marvell,intc-priority; + marvell,intc-nr-irqs = <34>; + }; + + gpio: gpio@40e00000 { + interrupts = <8>, <9>, <10>; + interrupt-names = "gpio0", "gpio1", "gpio_mux"; + }; + + uart@40100000 { + status = "okay"; + }; + + uart@40200000 { + status = "okay"; + }; + + uart@40700000 { + status = "okay"; + }; + + mmc0: mmc@41100000 { + vmmc-supply = <&vmmc>; + status = "okay"; + }; + + usb0: ohci@4c000000 { + marvell,port-mode = <3>; + marvell,oc-mode-perport; + marvell,enable-port1; + status = "okay"; + }; + + leds { + compatible = "gpio-leds"; + + status { + gpios = <&gpio 84 1>; + linux,default-trigger = "heartbeat"; + }; + }; + + i2c: i2c-gpio { + compatible = "i2c-gpio"; + gpios = <&gpio 22 0 /* sda */ + &gpio 12 0 /* scl */>; + i2c-gpio,delay-us = <1>; + i2c-gpio,timeout-ms = <1>; + #address-cells = <1>; + #size-cells = <0>; + + eeprom@50 { + compatible = "atmel,24c128"; + reg = <0x50>; + pagesize = <64>; + }; + }; + + w1: w1-gpio { + compatible = "w1-gpio"; + gpios = <&gpio 83 0>; + }; + }; + + extbus { + /* + * PXA27x synchrous, static and + * variable-latency IO interfaces + */ + compatible = "simple-bus"; + + #address-cells = <2>; /* first cell is nCS, second is address */ + #size-cells = <1>; + ranges = <0 0 0 0x04000000 + 1 0 0x04000000 0x04000000 + 2 0 0x08000000 0x04000000 + 3 0 0x0c000000 0x04000000 + 4 0 0x10000000 0x04000000 + 5 0 0x14000000 0x04000000>; + + flash@0 { + compatible = "cfi-flash"; + reg = <0 0 0x02000000>; + bank-width = <4>; + device-width = <2>; + + partitions { + #address-cells = <1>; + #size-cells = <1>; + fs@0 { + label = "u-boot"; + reg = <0 0x40000>; + }; + fs@40000 { + label = "settings"; + reg = <0x40000 0x40000>; + }; + fs@80000 { + label = "device_tree"; + reg = <0x80000 0x40000>; + }; + fs@c0000 { + label = "kernel"; + reg = <0xc0000 0x240000>; + }; + fs@300000 { + label = "root_fs"; + reg = <0x300000 0x1d00000>; + }; + }; + }; + + flash@1 { + compatible = "cfi-flash"; + reg = <1 0x0 0x01000000>; + bank-width = <2>; + device-width = <1>; + partitions { + #address-cells = <1>; + #size-cells = <1>; + }; + }; + + netio@3 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0 3 0 0x02000000>; + interrupt-parent = <&gpio>; + + eth0: eth@0 { + compatible = "davicom,dm9000"; + reg = <0x0 0x2 + 0x4000 0x2>; + interrupts = <9 IRQ_TYPE_EDGE_RISING>; + status = "okay"; + }; + + eth1: eth@1000000 { + compatible = "davicom,dm9000"; + reg = <0x1000000 0x2 + 0x1004000 0x2>; + interrupts = <82 IRQ_TYPE_EDGE_RISING>; + status = "okay"; + }; + }; + + fpga@5 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0 5 0x3000000 0x10000>; + interrupt-parent = <&fpgairq>; + + rtc@901c { + compatible = "dallas,rtc-ds1302"; + reg = <0x901c 0x1>; + status = "okay"; + }; + + sram@a000 { + compatible = "icpdas,sram-lp8x4x"; + reg = <0xa000 0x1000 + 0x901e 0x1>; + + partitions { + #address-cells = <1>; + #size-cells = <1>; + }; + }; + + fpgairq: irq@9006 { + compatible = "icpdas,irq-lp8x4x"; + reg = <0x9006 0x16>; + interrupt-parent = <&gpio>; + interrupts = <3 IRQ_TYPE_EDGE_FALLING>; + #interrupt-cells = <1>; + interrupt-controller; + status = "okay"; + }; + + uart@9050 { + compatible = "icpdas,uart-lp8x4x"; + reg = <0x9050 0x10 + 0x9030 0x02>; + interrupts = <13>; + status = "okay"; + }; + + uart@9060 { + compatible = "icpdas,uart-lp8x4x"; + reg = <0x9060 0x10 + 0x9032 0x02>; + interrupts = <14>; + status = "okay"; + }; + + uart@9070 { + compatible = "icpdas,uart-lp8x4x"; + reg = <0x9070 0x10 + 0x9034 0x02>; + interrupts = <15>; + status = "okay"; + }; + + backplane { + compatible = "icpdas,backplane-lp8x4x"; + reg = <0x0 0x2 + 0x1000 0x10 + 0x2000 0x10 + 0x3000 0x10 + 0x4000 0x10 + 0x5000 0x10 + 0x6000 0x10 + 0x7000 0x10 + 0x8000 0x10 + 0x9002 0x2 + 0x9004 0x2 + 0x9046 0x2>; + eeprom-gpios = <&gpio 4 0>; + }; + }; + }; +}; diff --git a/arch/arm/configs/lp8x4x_defconfig b/arch/arm/configs/lp8x4x_defconfig new file mode 100644 index 0000000..0eb87df --- /dev/null +++ b/arch/arm/configs/lp8x4x_defconfig @@ -0,0 +1,176 @@ +# CONFIG_LOCALVERSION_AUTO is not set +# CONFIG_SWAP is not set +CONFIG_SYSVIPC=y +CONFIG_NO_HZ=y +CONFIG_HIGH_RES_TIMERS=y +CONFIG_RCU_BOOST=y +CONFIG_LOG_BUF_SHIFT=14 +CONFIG_NAMESPACES=y +# CONFIG_UTS_NS is not set +# CONFIG_IPC_NS is not set +CONFIG_CC_OPTIMIZE_FOR_SIZE=y +# CONFIG_UID16 is not set +# CONFIG_SHMEM is not set +CONFIG_EMBEDDED=y +# CONFIG_COMPAT_BRK is not set +CONFIG_SLOB=y +CONFIG_JUMP_LABEL=y +CONFIG_MODULES=y +CONFIG_MODULE_UNLOAD=y +CONFIG_MODVERSIONS=y +# CONFIG_LBDAF is not set +CONFIG_BLK_CMDLINE_PARSER=y +CONFIG_PARTITION_ADVANCED=y +# CONFIG_EFI_PARTITION is not set +# CONFIG_IOSCHED_DEADLINE is not set +CONFIG_ARCH_PXA=y +CONFIG_MACH_PXA27X_DT=y +# CONFIG_ARM_THUMB is not set +CONFIG_PREEMPT=y +CONFIG_AEABI=y +# CONFIG_COMPACTION is not set +# CONFIG_CROSS_MEMORY_ATTACH is not set +CONFIG_ZBOOT_ROM_TEXT=0x0 +CONFIG_ZBOOT_ROM_BSS=0x0 +CONFIG_CMDLINE="init=/sbin/init root=/dev/mmcblk0p1 rw rootfstype=ext4 console=ttyS0,115200 mem=128M rootwait" +# CONFIG_SUSPEND is not set +CONFIG_NET=y +CONFIG_PACKET=y +CONFIG_UNIX=y +CONFIG_INET=y +CONFIG_IP_PNP=y +CONFIG_IP_PNP_BOOTP=y +CONFIG_BRIDGE=m +CONFIG_BRIDGE_VLAN_FILTERING=y +CONFIG_VLAN_8021Q=m +CONFIG_VLAN_8021Q_GVRP=y +CONFIG_VLAN_8021Q_MVRP=y +# CONFIG_WIRELESS is not set +CONFIG_DEVTMPFS=y +CONFIG_DEVTMPFS_MOUNT=y +# CONFIG_FW_LOADER is not set +CONFIG_MTD=y +CONFIG_MTD_CMDLINE_PARTS=y +CONFIG_MTD_BLOCK=y +CONFIG_MTD_CFI=y +CONFIG_MTD_CFI_ADV_OPTIONS=y +CONFIG_MTD_CFI_GEOMETRY=y +CONFIG_MTD_CFI_INTELEXT=y +CONFIG_MTD_PHYSMAP_OF=y +CONFIG_MTD_SRAM_LP8X4X=y +CONFIG_PROC_DEVICETREE=y +CONFIG_BLK_DEV_LOOP=y +CONFIG_BLK_DEV_LOOP_MIN_COUNT=2 +CONFIG_EEPROM_AT24=m +CONFIG_LP8X4X_BUS=m +CONFIG_SCSI=y +# CONFIG_SCSI_PROC_FS is not set +CONFIG_BLK_DEV_SD=y +# CONFIG_SCSI_LOWLEVEL is not set +CONFIG_NETDEVICES=y +CONFIG_BONDING=m +CONFIG_MACVLAN=m +CONFIG_MACVTAP=m +CONFIG_TUN=m +# CONFIG_NET_VENDOR_ARC is not set +# CONFIG_NET_CADENCE is not set +# CONFIG_NET_VENDOR_BROADCOM is not set +# CONFIG_NET_VENDOR_CIRRUS is not set +CONFIG_DM9000=y +CONFIG_DM9000_FORCE_SIMPLE_PHY_POLL=y +# CONFIG_NET_VENDOR_FARADAY is not set +# CONFIG_NET_VENDOR_INTEL is not set +# CONFIG_NET_VENDOR_MARVELL is not set +# CONFIG_NET_VENDOR_MICREL is not set +# CONFIG_NET_VENDOR_NATSEMI is not set +# CONFIG_NET_VENDOR_SEEQ is not set +# CONFIG_NET_VENDOR_SMSC is not set +# CONFIG_NET_VENDOR_STMICRO is not set +# CONFIG_NET_VENDOR_VIA is not set +# CONFIG_NET_VENDOR_WIZNET is not set +CONFIG_PPP=m +CONFIG_PPP_BSDCOMP=m +CONFIG_PPP_DEFLATE=m +CONFIG_PPPOE=m +CONFIG_PPP_ASYNC=m +CONFIG_PPP_SYNC_TTY=m +CONFIG_SLIP=m +CONFIG_SLIP_COMPRESSED=y +# CONFIG_WLAN is not set +CONFIG_INPUT_MOUSEDEV_SCREEN_X=800 +CONFIG_INPUT_MOUSEDEV_SCREEN_Y=600 +CONFIG_INPUT_EVDEV=y +# CONFIG_INPUT_KEYBOARD is not set +# CONFIG_INPUT_MOUSE is not set +# CONFIG_SERIO is not set +# CONFIG_DEVKMEM is not set +CONFIG_SERIAL_8250=y +# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set +CONFIG_SERIAL_8250_CONSOLE=y +CONFIG_SERIAL_8250_NR_UARTS=40 +CONFIG_SERIAL_8250_RUNTIME_UARTS=40 +CONFIG_SERIAL_8250_EXTENDED=y +CONFIG_SERIAL_8250_MANY_PORTS=y +CONFIG_SERIAL_8250_SHARE_IRQ=y +CONFIG_SERIAL_8250_PXA=y +CONFIG_SERIAL_8250_LP8X4X=m +CONFIG_HW_RANDOM=y +CONFIG_I2C=m +# CONFIG_I2C_COMPAT is not set +CONFIG_I2C_GPIO=m +CONFIG_W1=m +CONFIG_W1_MASTER_GPIO=m +CONFIG_W1_SLAVE_SMEM=m +# CONFIG_HWMON is not set +CONFIG_WATCHDOG=y +CONFIG_SA1100_WATCHDOG=m +CONFIG_REGULATOR=y +CONFIG_REGULATOR_FIXED_VOLTAGE=y +CONFIG_FB=y +CONFIG_FB_PXA=y +CONFIG_FRAMEBUFFER_CONSOLE=y +CONFIG_LOGO=y +CONFIG_USB=m +CONFIG_USB_OHCI_HCD=m +CONFIG_USB_ACM=m +CONFIG_USB_PRINTER=m +CONFIG_USB_STORAGE=m +CONFIG_USB_SERIAL=m +CONFIG_MMC=y +CONFIG_MMC_PXA=y +CONFIG_NEW_LEDS=y +CONFIG_LEDS_CLASS=y +CONFIG_LEDS_GPIO=y +CONFIG_LEDS_TRIGGERS=y +CONFIG_LEDS_TRIGGER_HEARTBEAT=y +CONFIG_RTC_CLASS=y +CONFIG_RTC_DRV_DS1302=y +CONFIG_RTC_DRV_PXA=m +# CONFIG_IOMMU_SUPPORT is not set +CONFIG_DMA_ENGINE=y +CONFIG_DMA_VIRTUAL_CHANNELS=y +CONFIG_DMA_OF=y +CONFIG_PXA_DMA=y +CONFIG_EXT2_FS=m +CONFIG_EXT3_FS=y +CONFIG_EXT4_FS=y +CONFIG_REISERFS_FS=m +CONFIG_ISO9660_FS=m +CONFIG_MSDOS_FS=y +CONFIG_VFAT_FS=y +CONFIG_NTFS_FS=m +CONFIG_NTFS_RW=y +CONFIG_JFFS2_FS=y +CONFIG_JFFS2_COMPRESSION_OPTIONS=y +CONFIG_NFS_FS=y +CONFIG_NFS_V4=y +CONFIG_ROOT_NFS=y +CONFIG_CIFS=m +CONFIG_CIFS_STATS=y +CONFIG_CODA_FS=m +CONFIG_NLS_DEFAULT="cp855" +CONFIG_NLS_CODEPAGE_437=y +CONFIG_NLS_CODEPAGE_855=y +CONFIG_NLS_ISO8859_1=y +CONFIG_NLS_UTF8=y +CONFIG_PRINTK_TIME=y