Re: [PATCH] OMAP3: PM: Update omap3_pm_defconfig

[Kevin Hilman <khilman@deeprootsystems.com>]

"Nayak, Rajendra" <rnayak@ti.com> writes:

>>-----Original Message-----
>>From: Gadiyar, Anand 
>>Sent: Wednesday, October 07, 2009 5:31 PM
>>To: Nayak, Rajendra; linux-omap@vger.kernel.org
>>Subject: RE: [PATCH] OMAP3: PM: Update omap3_pm_defconfig
>>
>>> Some of the sysfs deprecated entries, if not enabled cause
>>> root filesystem mounts to fail at boot.
>>> This is seen on both the 3430SDP as well as 3430zoom platforms.
>>> 
>>> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
>>> ---
>>>  arch/arm/configs/omap3_pm_defconfig |    3 ++-
>>>  1 files changed, 2 insertions(+), 1 deletions(-)
>>> 
>>> diff --git a/arch/arm/configs/omap3_pm_defconfig 
>>> b/arch/arm/configs/omap3_pm_defconfig
>>> index 9d54139..b1c42ed 100644
>>> --- a/arch/arm/configs/omap3_pm_defconfig
>>> +++ b/arch/arm/configs/omap3_pm_defconfig
>>> @@ -58,7 +58,8 @@ CONFIG_FAIR_GROUP_SCHED=y
>>>  CONFIG_USER_SCHED=y
>>>  # CONFIG_CGROUP_SCHED is not set
>>>  # CONFIG_CGROUPS is not set
>>> -# CONFIG_SYSFS_DEPRECATED_V2 is not set
>>> +CONFIG_SYSFS_DEPRECATED=y
>>> +CONFIG_SYSFS_DEPRECATED_V2=y
>>
>>I think these were deliberately removed on  many OMAP3
>>defconfigs by a recent patch from Vikram
>>.
>>Having these enabled makes it hard to boot on a newer
>>busybox filesystem.
>>
>>It's easy to fix if you just upgrade busybox to a newer
>>version.

Also, any OE-based distro expects these to be disabled to work
correctly.

Kevin