Shilimkar, Santosh wrote: > > >-----Original Message----- > > >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of > > >Shilimkar, Santosh > > >Sent: Wednesday, December 09, 2009 12:29 PM > > >To: tony@xxxxxxxxxxx > > >Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx; linux@xxxxxxxxxxxxxxxx; > > >Shilimkar, Santosh > > >Subject: [PATCH 6/6] OMAP4: Sync up omap4430 defconfig > > > > > >Enable minimum features to boot omap4430 on es1.0 samples > > > > > >Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > >--- > > > arch/arm/configs/omap_4430sdp_defconfig | 146 ++++++++++++++++++------------- > > > 1 files changed, 84 insertions(+), 62 deletions(-) > > > > > >diff --git a/arch/arm/configs/omap_4430sdp_defconfig b/arch/arm/configs/omap_4430sdp_defconfig > > >index a464ca3..49df3ad 100644 > > >--- a/arch/arm/configs/omap_4430sdp_defconfig > > >+++ b/arch/arm/configs/omap_4430sdp_defconfig > > >@@ -1,26 +1,29 @@ > > > # > > > # Automatically generated make config: don't edit > > >-# Linux kernel version: 2.6.30-rc7 > > >-# Tue Jun 9 12:36:23 2009 > > >+# Linux kernel version: 2.6.32 > > >+# Sun Dec 6 23:37:45 2009 > > <snip> > > >-# CONFIG_SYSFS_DEPRECATED=y is not set > > >-# CONFIG_SYSFS_DEPRECATED_V2=y is not set > > >+CONFIG_SYSFS_DEPRECATED_V2=y > > > > This is a deprecated feature and don't introduce it back again. > > There haven been patches in recent past to get rid of this. > Thanks Vikram. The thing is some of the busy box people are using get confused > and stuck without this. > > Do you have pointers to those patches ? > Poky, and other open-embedded based distros expect this to be disabled to work correctly The solution is to upgrade busybox, not enable a deprecated CONFIG option. Patches to update the different OMAP defconfig were posted to l-o a few months ago. Here's one.such patch. <http://patchwork.kernel.org/patch/40949/> - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
