Re: [OpenWrt-Devel] [PATCH 5/5] [orion] kernel and its mtd size
On 20.09.2011 01:02, Patrick Florek wrote: I just compiled a new Firmware for the Marvell Orion Generic Platform (wrt350n v2). I build it with the standard config and failed on creation of the firmware image. Error is that the kernel size is bigger than his space in the filesystem. Should i increase the size for it. How o i set the offset? 1.5M or 2M? Greetings Patrick Did you compile with kernel symbols? I did some days ago with r28247 and my WRT350Nv2 uImage was 1.050.976 Bytes in size (1MB is only 1.048.576). So add another 64KB to the kernel mtd partition (local modification for you), or disable kernel symbols (saves lots of bytes). Where to change this is shown in the 3rd attachment of ticket #5339 [1], and you have to update the image script for Orion too. [1] https://dev.openwrt.org/ticket/5339 Maddes ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] base-files: load_kernelmodules()
I would rather let it accept an argument so the day we change the path we don't have to change the function and just replace occurences of the script instead. Are you agree with patch6, which implements this? As far I can see, only one script (/etc/init.d/boot) uses this function. Will this change in the future? bye, Bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] OpenWrt GPL compliance
I'd like to provide a binary build of OpenWrt packages, however I want to comply with the terms of the GPL. I figured the most obvious thing to do would be to copy the way OpenWrt does things. I'm not convinced that OpenWrt complies with the GPL with regard to section 3, as I have no idea how to generate the packages in the snapshot from the files in the 'sources' area, and I haven't seen this documented anywhere. Can someone shed some light on this? thanks, Biff. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] base-files: load_kernelmodules()
On Tuesday 20 September 2011 13:32:52 Bastian Bittorf wrote:
I would rather let it accept an argument so the day we change the
path we
don't have to change the function and just replace occurences of
the script
instead.
Are you agree with patch6, which implements this?
I think patch 6 proposes too much configurability, so let's just do it that way
instead:
function load_modules() {
local dir=${1:-/etc/modules.d}
...
}
As far I can see, only one script (/etc/init.d/boot)
uses this function. Will this change in the future?
Probably not, it's just to be enough.
--
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
Hello, On Tue, Sep 20, 2011 at 5:26 PM, bifferos biffe...@yahoo.co.uk wrote: as I have no idea how to generate the packages in the snapshot from the files in the 'sources' area, and I haven't seen this documented anywhere. I could not clearly understand what you mean, but here is my understanding of the build process. There is a package source that can be downloaded from a publicly accessible URL (upstream), There are openwrt patches for that particular package, in package/foo/patches directory There are config files (among possibly others) for that particular package, in package/foo/files directory When giving out a openwrt-SDK, there may be binaries, again it follows the same logic given logic above Unless upstream ships binary blobs, freedom to demand show me the code is AFAIK satisfied. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
--- On Tue, 20/9/11, harish badrinath harishbadrin...@gmail.com wrote: Unless upstream ships binary blobs, freedom to demand show me the code is AFAIK satisfied. I don't think you understood. I know how to build *a* version of OpenWrt. I don't know how to build *the* version that created a snapshot. The GPL says: For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable Let me use as an example Backfire 10.03. See: root/tags/backfire_10.03/feeds.conf.default It specifies the packages tip only as: svn://svn.openwrt.org/openwrt/packages (no revision is given). So how do I know what version of packages was pulled in at the time of building? I can assume the package source itself ends up in the 'dl' directory, so I can back that up so I have the pristine package source, but what about the patch set that was applied at that time, and where is the build config for that release? Put in simple terms, where is the build script for a given snapshot? cheers, Biff. PS: As an aside I notice the package sets for snapshots are not complete. Can anyone tell me how I can get the build system to build everything but skipping any packages that don't compile? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
On 20.09.2011 13:56, bifferos wrote: I'd like to provide a binary build of OpenWrt packages, however I want to comply with the terms of the GPL. I figured the most obvious thing to do would be to copy the way OpenWrt does things. I'm not convinced that OpenWrt complies with the GPL with regard to section 3, as I have no idea how to generate the packages in the snapshot from the files in the 'sources' area, and I haven't seen this documented anywhere. Can someone shed some light on this? Did you see the first sentences of e.g. http://downloads.openwrt.org/backfire/10.03.1-rc5/README ? ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] base-files: load_kernelmodules()
I think patch 6 proposes too much configurability, so let's just do
it that way
instead:
function load_modules() {
local dir=${1:-/etc/modules.d}
...
}
This is the same like proposed, ist'nt it? Where is the difference?
bye, Bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
I don't think you understood. I know how to build *a* version of OpenWrt. I don't know how to build *the* version that created a snapshot. If you simply want to be GPL-compliant, you can build your image and _then_ make an archiv of the hole builddir. so you have all downloaded sources for this moment and you can build exactly the same image in 5 years. as far as i know, all the scripts don't need an network connection, if the sources are already downloaded... Is this the answer you wanted? bye, Bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
I don't think you understood. I know how to build *a* version of OpenWrt. I don't know how to build *the* version that created a snapshot. If you simply want to be GPL-compliant, you can build your image and _then_ make an archiv of the hole builddir. so you have all downloaded sources for this moment and you can build exactly the same image in 5 years. (ship the archive to the customer) as far as i know, all the scripts don't need an network connection, if the sources are already downloaded... Is this the answer you wanted? bye, Bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
--- On Tue, 20/9/11, edgar.sol...@web.de edgar.sol...@web.de wrote: Did you see the first sentences of e.g. http://downloads.openwrt.org/backfire/10.03.1-rc5/README That source revision wasn't my concern. So let's see if I've got this right: 1) Check out correct revision as per instructions in release README 2) Copy config from chosen binaries directory to .config 3) Copy sources to dl/ directory 4) type make package/symlinks 5) type make Is that it? I don't understand how the systems works out to pull in the correct feed version. I can understand how it works for tagged feeds, e.g. svn://svn.openwrt.org/openwrt/branches/packages_10.03.1 but I don't get how it can work for svn://svn.openwrt.org/openwrt/packages, and this is what I'm struggling with. Doesn't that just pull the tip, and therefore potentially break what was supposed to be a stable release? Biff. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
On 2011-09-20 5:08 PM, bifferos wrote: --- On Tue, 20/9/11, Bastian Bittorfbitt...@bluebottle.com wrote: If you simply want to be GPL-compliant, you can build your image and _then_ make an archiv of the hole builddir. so you have This is better than nothing, but I suspect won't fit on a single DVD :(. It is also unpleasant for the recipient, for instance they may get a 64-bit build tree to use on a 32-bit machine, or be given a 32-bit build tree and then have to configure multilib etc... Don't ship the build_dir/staging_dir. Ship the normal tree plus dl/ and feeds/ That way it does not reference anything external anymore when you try to build it and it's still portable. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is that it? I don't understand how the systems works out to pull in the correct feed version. I can understand how it works for tagged feeds, e.g. svn://svn.openwrt.org/openwrt/branches/packages_10.03.1 but I don't get how it can work for svn://svn.openwrt.org/openwrt/packages, and this is what I'm struggling with. Doesn't that just pull the tip, and therefore potentially break what was supposed to be a stable release? Simply change the feeds url to http://example.org/blah/blah@12345 and it will checkout revision 12345 instead of HEAD. ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk540TQACgkQdputYINPTPMjswCfS6SeuBQfP50IOBN7Xu89Z+hA VeMAmwRnfrw+43SLb3Tuxv3rhHbUCJvw =RRWf -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ath9k_htc: fix firmware name
ath9k_htc driver requires new firmware name as stated in http://linuxwireless.org/en/users/Drivers/ath9k_htc Signed-off-by: Andrej Vlašić andrej.vlasic0 at gmail dot com ath9k_htc_fw_name.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt GPL compliance
--- On Tue, 20/9/11, edgar.sol...@web.de edgar.sol...@web.de wrote: From: edgar.sol...@web.de edgar.sol...@web.de Subject: Re: [OpenWrt-Devel] OpenWrt GPL compliance To: OpenWrt Development List openwrt-devel@lists.openwrt.org Date: Tuesday, 20 September, 2011, 14:46 On 20.09.2011 14:33, bifferos wrote: So how do I know what version of packages was pulled in at the time of building? I can assume the package source itself ends up in the 'dl' directory, so I can back that up so I have the pristine package source, but what about the patch set that was applied at that time, and where is the build config for that release? this is topic once in a while here on the list. search the archives. there is one revision for packages and trunk per release, as they come out of the same svn. Not all feeds come from the same svn. Put in simple terms, where is the build script for a given snapshot? ordinary buildroot. just find out the correct revision and download that instead of latest. I don't think that works. The snapshots need to somehow record the feed versions in order to be reproducible. Biff. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 0/2] update ben nanonote to linux-3.0
From: Xiangfu Liu xiangf...@gmail.com Hi Lars those two patches is for update the ben nanonote to linux-3.0 most of the kernel code is from the qi-kernel.git[1]. compare to 2.6.38, the most different maybe is '0024-forward-code-to-linux-3.0.patch' help me review those code, please conside merge to upstream thanks Lars xiangfu [1] http://projects.qi-hardware.com/index.php/p/qi-kernel/ Xiangfu Liu (2): ben nanonote: forward patches to linux-3.0 xburst jz4740: update the soc config-3.0 target/linux/xburst/Makefile |2 +- target/linux/xburst/config-3.0 | 269 + .../patches-3.0/0001-JZ4740-cache-quirks.patch | 339 + .../patches-3.0/0002-Add-n516-board-support.patch | 679 ++ .../patches-3.0/0003-Add-n526-board-support.patch | 368 + .../0004-MIPS-JZ4740-Add-id800wt-board.patch | 206 + .../0005-Add-N516-sound-SoC-board-driver.patch | 352 + .../patches-3.0/0006-Add-n516-lpc-driver.patch | 520 ++ .../0007-Add-N526-sound-SoC-board-driver.patch | 219 + .../0008-i2c-Add-i2c-driver-for-JZ47XX-SoCs.patch | 482 + .../0009-MIPS-JZ4740-Fix-i2c-driver-name.patch | 29 + ...adc-Add-support-for-the-touchscreen-part-.patch | 71 + ...Add-touchscreen-driver-for-the-JZ4740-SoC.patch | 389 + .../patches-3.0/0012-Add-ili8960-lcd-driver.patch | 314 + .../patches-3.0/0013-Add-jz4740-udc-driver.patch | 2381 + ...-notifier-Call-notifier-callbacks-prior-t.patch | 42 + .../patches-3.0/0015-500-modifier-keys.patch.patch | 657 ++ .../0016-850-ks7010-support.patch.patch| 66 + .../patches-3.0/0017-900-add-openwrt-logo.patch| 9744 ...d-only-the-vid-header-instead-of-the-whol.patch | 25 + ...Optimize-NAND_ECC_HW_OOB_FIRST-read.patch.patch | 44 + ...d-support-for-subpage-reads-for-NAND_ECC_.patch | 150 + ...timize-reading-the-eec-data-for-the-JZ474.patch | 58 + ...-t-use-3-wire-spi-mode-for-the-display-fo.patch | 25 + .../0023-qi_lb60-NAND-add-data-partition.patch | 31 + .../0024-forward-code-to-linux-3.0.patch | 1275 +++ .../0025-Update-to-new-platform-code.patch | 25 + .../patches-3.0/0026-sound-update-DMA-code.patch | 88 + .../patches-3.0/0027-Add-DEVMEM-support.patch | 117 + .../patches-3.0/0028-Add-cpufreq-support.patch | 425 + .../patches-3.0/0029-Add-new-jz4740_lcd.h.patch| 208 + target/linux/xburst/qi_lb60/config-3.0 | 38 + 32 files changed, 19637 insertions(+), 1 deletions(-) create mode 100644 target/linux/xburst/config-3.0 create mode 100644 target/linux/xburst/patches-3.0/0001-JZ4740-cache-quirks.patch create mode 100644 target/linux/xburst/patches-3.0/0002-Add-n516-board-support.patch create mode 100644 target/linux/xburst/patches-3.0/0003-Add-n526-board-support.patch create mode 100644 target/linux/xburst/patches-3.0/0004-MIPS-JZ4740-Add-id800wt-board.patch create mode 100644 target/linux/xburst/patches-3.0/0005-Add-N516-sound-SoC-board-driver.patch create mode 100644 target/linux/xburst/patches-3.0/0006-Add-n516-lpc-driver.patch create mode 100644 target/linux/xburst/patches-3.0/0007-Add-N526-sound-SoC-board-driver.patch create mode 100644 target/linux/xburst/patches-3.0/0008-i2c-Add-i2c-driver-for-JZ47XX-SoCs.patch create mode 100644 target/linux/xburst/patches-3.0/0009-MIPS-JZ4740-Fix-i2c-driver-name.patch create mode 100644 target/linux/xburst/patches-3.0/0010-MFD-jz4740-adc-Add-support-for-the-touchscreen-part-.patch create mode 100644 target/linux/xburst/patches-3.0/0011-input-Add-touchscreen-driver-for-the-JZ4740-SoC.patch create mode 100644 target/linux/xburst/patches-3.0/0012-Add-ili8960-lcd-driver.patch create mode 100644 target/linux/xburst/patches-3.0/0013-Add-jz4740-udc-driver.patch create mode 100644 target/linux/xburst/patches-3.0/0014-Framebuffer-notifier-Call-notifier-callbacks-prior-t.patch create mode 100644 target/linux/xburst/patches-3.0/0015-500-modifier-keys.patch.patch create mode 100644 target/linux/xburst/patches-3.0/0016-850-ks7010-support.patch.patch create mode 100644 target/linux/xburst/patches-3.0/0017-900-add-openwrt-logo.patch create mode 100644 target/linux/xburst/patches-3.0/0018-901-ubi-Read-only-the-vid-header-instead-of-the-whol.patch create mode 100644 target/linux/xburst/patches-3.0/0019-902-NAND-Optimize-NAND_ECC_HW_OOB_FIRST-read.patch.patch create mode 100644 target/linux/xburst/patches-3.0/0020-903-NAND-Add-support-for-subpage-reads-for-NAND_ECC_.patch create mode 100644 target/linux/xburst/patches-3.0/0021-904-NAND-Optimize-reading-the-eec-data-for-the-JZ474.patch create mode 100644 target/linux/xburst/patches-3.0/0022-qi_lb60-Don-t-use-3-wire-spi-mode-for-the-display-fo.patch create mode 100644 target/linux/xburst/patches-3.0/0023-qi_lb60-NAND-add-data-partition.patch create mode 100644 target/linux/xburst/patches-3.0/0024-forward-code-to-linux-3.0.patch create mode 100644
[OpenWrt-Devel] [PATCH 2/2] xburst jz4740: update the soc config-3.0
From: Xiangfu Liu xiangf...@gmail.com --- target/linux/xburst/config-3.0 | 298 +--- 1 files changed, 64 insertions(+), 234 deletions(-) diff --git a/target/linux/xburst/config-3.0 b/target/linux/xburst/config-3.0 index dd67e13..4852d64 100644 --- a/target/linux/xburst/config-3.0 +++ b/target/linux/xburst/config-3.0 @@ -1,8 +1,4 @@ - -CONFIG_32BIT=y -# CONFIG_64BIT is not set -# CONFIG_ALCHEMY_GPIO_INDIRECT is not set -# CONFIG_AR7 is not set +# CONFIG_ARCH_DMA_ADDR_T_64BIT is not set # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y @@ -13,60 +9,27 @@ CONFIG_ARCH_REQUIRE_GPIOLIB=y CONFIG_ARCH_SUPPORTS_OPROFILE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ARPD is not set -# CONFIG_AUTO_IRQ_AFFINITY is not set -# CONFIG_BACKLIGHT_CLASS_DEVICE is not set -# CONFIG_BACKLIGHT_GENERIC is not set -# CONFIG_BACKLIGHT_LCD_SUPPORT is not set -# CONFIG_BATTERY_BQ20Z75 is not set -CONFIG_BATTERY_JZ4740=y -# CONFIG_BCM47XX is not set -# CONFIG_BCM63XX is not set -CONFIG_BITREVERSE=y -# CONFIG_BKL is not set +# CONFIG_ATH79 is not set +CONFIG_BCMA_POSSIBLE=y # CONFIG_BLK_DEV_INITRD is not set -# CONFIG_BMP085 is not set # CONFIG_BRIDGE is not set # CONFIG_BSD_PROCESS_ACCT is not set -# CONFIG_CAVIUM_OCTEON_REFERENCE_BOARD is not set -# CONFIG_CAVIUM_OCTEON_SIMULATOR is not set CONFIG_CHARGER_GPIO=y CONFIG_CONSOLE_TRANSLATIONS=y -# CONFIG_CPU_BIG_ENDIAN is not set -# CONFIG_CPU_CAVIUM_OCTEON is not set CONFIG_CPU_HAS_PREFETCH=y CONFIG_CPU_HAS_SYNC=y CONFIG_CPU_LITTLE_ENDIAN=y -# CONFIG_CPU_LOONGSON2E is not set -# CONFIG_CPU_LOONGSON2F is not set -CONFIG_CPU_MIPS32_R1=y -# CONFIG_CPU_MIPS32_R2 is not set CONFIG_CPU_MIPS32=y -# CONFIG_CPU_MIPS64_R1 is not set -# CONFIG_CPU_MIPS64_R2 is not set +CONFIG_CPU_MIPS32_R1=y CONFIG_CPU_MIPSR1=y -# CONFIG_CPU_NEVADA is not set -# CONFIG_CPU_R1 is not set -# CONFIG_CPU_R3000 is not set -# CONFIG_CPU_R4300 is not set -# CONFIG_CPU_R4X00 is not set -# CONFIG_CPU_R5000 is not set -# CONFIG_CPU_R5432 is not set -# CONFIG_CPU_R5500 is not set -# CONFIG_CPU_R6000 is not set -# CONFIG_CPU_R8000 is not set -# CONFIG_CPU_RM7000 is not set -# CONFIG_CPU_RM9000 is not set -# CONFIG_CPU_SB1 is not set CONFIG_CPU_SUPPORTS_32BIT_KERNEL=y +CONFIG_CPU_SUPPORTS_CPUFREQ=y CONFIG_CPU_SUPPORTS_HIGHMEM=y -# CONFIG_CPU_TX39XX is not set -# CONFIG_CPU_TX49XX is not set -# CONFIG_CPU_VR41XX is not set CONFIG_CRC16=y +CONFIG_CRYPTO_ALGAPI=y +CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_LZO=y -CONFIG_DEFAULT_AS=y -CONFIG_DMA_NEED_PCI_MAP_STATE=y CONFIG_DMA_NONCOHERENT=y CONFIG_DUMMY_CONSOLE=y CONFIG_EARLY_PRINTK=y @@ -74,48 +37,29 @@ CONFIG_ELF_CORE=y CONFIG_ENABLE_MUST_CHECK=y CONFIG_EXT4_FS=y CONFIG_FAT_FS=y -# CONFIG_FB_JZ4740 is not set -CONFIG_FB_SYS_COPYAREA=y -CONFIG_FB_SYS_FILLRECT=y -CONFIG_FB_SYS_IMAGEBLIT=y CONFIG_FB=y +# CONFIG_FB_JZ4740 is not set +# CONFIG_FB_WMT_GE_ROPS is not set # CONFIG_FIRMWARE_EDID is not set -CONFIG_FONTS=y -# CONFIG_FONT_10x18 is not set -# CONFIG_FONT_6x11 is not set -# CONFIG_FONT_7x14 is not set -# CONFIG_FONT_8x16 is not set -# CONFIG_FONT_8x8 is not set -# CONFIG_FONT_ACORN_8x8 is not set -# CONFIG_FONT_MINI_4x6 is not set -# CONFIG_FONT_PEARL_8x8 is not set -# CONFIG_FONT_SUN12x22 is not set -CONFIG_FONT_SUN8x16=y CONFIG_FORCE_MAX_ZONEORDER=12 -# CONFIG_FRAMEBUFFER_CONSOLE is not set -# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set -# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set CONFIG_FREEZER=y +CONFIG_FS_MBCACHE=y CONFIG_GENERIC_ATOMIC64=y -CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CMOS_UPDATE=y -CONFIG_GENERIC_FIND_LAST_BIT=y -CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_GPIO=y -CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y -# CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED is not set -# CONFIG_GENERIC_PENDING_IRQ is not set +CONFIG_GENERIC_IRQ_CHIP=y +CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GPIOLIB=y -# CONFIG_GPIO_SX150X is not set # CONFIG_HAMRADIO is not set -# CONFIG_HARDLOCKUP_DETECTOR is not set -# CONFIG_HARDIRQS_SW_RESEND is not set CONFIG_HARDWARE_WATCHPOINTS=y CONFIG_HAS_DMA=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y +CONFIG_HAVE_ARCH_JUMP_LABEL=y CONFIG_HAVE_ARCH_KGDB=y +CONFIG_HAVE_CLK=y CONFIG_HAVE_C_RECORDMCOUNT=y CONFIG_HAVE_DMA_API_DEBUG=y CONFIG_HAVE_DMA_ATTRS=y @@ -124,117 +68,79 @@ CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y -CONFIG_HAVE_GENERIC_HARDIRQS=y CONFIG_HAVE_GENERIC_DMA_COHERENT=y +CONFIG_HAVE_GENERIC_HARDIRQS=y CONFIG_HAVE_IDE=y -CONFIG_HAVE_KPROBES=y -CONFIG_HAVE_KRETPROBES=y +CONFIG_HAVE_IRQ_WORK=y CONFIG_HAVE_OPROFILE=y CONFIG_HAVE_PERF_EVENTS=y CONFIG_HAVE_PWM=y -# CONFIG_HAVE_SPARSE_IRQ is not set -# CONFIG_HIBERNATION is not set # CONFIG_HIGH_RES_TIMERS is not set CONFIG_HW_CONSOLE=y -#
