Hi
There are a few things you can verify:
Part I (kernel)
(1)make sure thus kernel configuration in MMC driver
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_UNSAFE_RESUME=y
# CONFIG_MMC_EMBEDDED_SDIO is not set
CONFIG_MMC_PARANOID_SD_INIT=y
#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_MMC_BLOCK_PARANOID_RESUME is not set
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=y
(2)Disable this option in kernel menuconfig
General Setup -> Create deprecated sysfs layout for older userspace
tools
Before I did this,vold showed a lot of trouble.
And ,my media_path is not right
media_path /devices/platform/s3c-sdhci.0/mmc_host:mmc0<--my path
before turn off that option
media_path /devices/platform/s3c-sdhci.0/mmc_host/mmc0 <--this is the
right one
Vold may be unhappy to accept my old path,and it didn't work.
D/vold ( 42): Accepted connection from framework
D/vold ( 42): dispatch_cmd(send_ums_status):
D/vold ( 42): dispatch_cmd(mount_volume:/sdcard):
E/vold ( 42): Cannot start volume '/sdcard' (volume is not bound)
D/MountListener( 59): handleEvent volume_nomedia:/sdcard
D/MountListener( 59): handleEvent ums_disabled
D/MountListener( 59): handleEvent ums_disconnected
(3) rebuild your linux kernel
PART II(android system)
(1) creat a vold.conf in build/target/board/idea6410 (this path will
be different for you, specific to your board )
## vold configuration file for idea6410
volume_sdcard {
## This is the direct uevent device path to the SD slot on the
device
media_path /devices/platform/s3c-sdhci.0/mmc_host/mmc0
media_type mmc
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun0
}
(2)add those below to AndroidBoard.mk
include $(CLEAR_VARS)
LOCAL_MODULE_CLASS := ETC
LOCAL_MODULE := vold.conf
LOCAL_SRC_FILES := $(LOCAL_MODULE)
include $(BUILD_PREBUILT)
(3)rebuild the system and check init.rc
service vold /system/bin/vold
socket vold stream 0660 root mount
D/vold ( 42): Accepted connection from framework
D/vold ( 42): dispatch_cmd(send_ums_status):
D/vold ( 42): dispatch_cmd(mount_volume:/sdcard):
I/vold ( 42): Evaluating dev '/devices/platform/s3c-sdhci.0/
mmc_host/mmc0/mmc0:e624/block/mmcblk0' for mountable filesystems for '/
sdcard'
D/MountListener( 61): handleEvent volume_unmounted:/sdcard
D/MountListener( 61): handleEvent ums_disabled
D/MountListener( 61): handleEvent ums_disconnected
D/MountListener( 61): handleEvent volume_checking:/sdcard
Lets see if these steps work for you.
Also, can you post the log messages coming from vold.
Cheers,
Rahul Soparkar
On Sep 21, 3:23 pm, Raju Sana <venkat.raju...@gmail.com> wrote:
> Rabhul,
>
> I have verified the path which has been given in vold.fstab is same as you
> mentioned and also the same entry is present in /sys .
>
> Thanks & Regards,
> Venkat.
>
> On Tue, Sep 21, 2010 at 12:16 PM, rahul soparkar
> <soparkar.ra...@gmail.com>wrote:
>
>
>
> > Hi Venkat,
>
> > The analysis which you have done about vold is correct, vold is not able to
> > detect the sdcard may be as the device path specified in the vold.conf is
> > not correct.
>
> > The path can be something like :
> > /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
> > this path corresponds to the sysfs devices entry path for the sdcard. check
> > the entry in your sysfs for the kernel used, it might be different.
>
> > Cheers,
> > Rahul Soparkar
>
> > On Tue, Sep 21, 2010 at 11:57 AM, Raju Sana <venkat.raju...@gmail.com>wrote:
>
> >> Hi
>
> >> I have ported the similar V4L2 stuff to android2.2 on beagle board , it
> >> builds for me but when I click on Camera application it says please insert
> >> the SD card . Are there any vold issues in android2.2 ?
> >> I guess the media scanner or vold some how unable to detect/mount the SD
> >> card such that the camera application was not aware of SD card.
>
> >> please find me some pointers on this.
>
> >> Thanks & Regards,
> >> Venkat.
>
> >> On Thu, Sep 2, 2010 at 12:17 PM, Rahul Soparkar <soparkar.ra...@gmail.com
> >> > wrote:
>
> >>> Hi
>
> >>> First you need to verify does your kernel support V4L2 through your
> >>> kernel configuration,
> >>> Then you have to write an HAL implementation according to the Camera
> >>> interface specified by android2.2, your HAL implementation should take
> >>> care about the V4L2 stuff, and would act as an communication bridge
> >>> between your V4L2 based camera driver in linux and the android
> >>> framework.
>
> >>> Below given link will of some help, they even have a patch for the HAL
> >>> implementation for V4L2 based camera but i think its for a older
> >>> version of android u need to modify accoring to android 2.2 and your
> >>> camera sensor :
>
> >>> "http://groups.google.com/group/android-porting/browse_thread/thread/
> >>> f6b9c22ee45a68c4<http://groups.google.com/group/android-porting/browse_thread/thread/%...>
> >>> "
>
> >>> Cheers,
> >>> Rahul Soparkar
>
> >>> On Aug 30, 1:11 pm, sandeep kaushik <sandeep...@gmail.com> wrote:
> >>> > Hi,
>
> >>> > I have a query about using v4l2 based driver for camera on android 2.2
> >>> > platform.
> >>> > Is there any application available for testing camera? Also, what
> >>> > patch that needs to be added on android for supporting v4l2 feature?
>
> >>> > Regards
> >>> > Sandeep
>
> >>> --
> >>> unsubscribe:
> >>> android-porting+unsubscr...@googlegroups.com<android-porting%2Bunsubscribe@
> >>> googlegroups.com>
> >>> website:http://groups.google.com/group/android-porting
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
