On Mon, Aug 9, 2010 at 6:05 PM, hedwin <hedwin.kon...@gmail.com> wrote:
> I actually don't mind whether it is 2.6.32 or 2.6.35 that is being used.
> The thing is there is a dependency between the kernel version and
> bionic, right?

Actually the dependency in this case is between the kernel and the
vold daemon.  bionic is the standard C library and has no dependencies
on the USB notifications.

Mike

> So when things go wrong it triggers me thinking I might have used the
> wrong kernel version, that's what happend
> when I treid using 2.6.32 (the one from eclair) for the froyo master branch.
> It would be a big help if the android webpage would state the
> configuration required for specific releases so everyone
> understands what to use.
>
> H.
>
> On Mon, Aug 9, 2010 at 9:45 PM, Mike Lockwood <lockw...@android.com> wrote:
>> Froyo uses kernel 2.6.32, and the master branch (which is froyo +
>> various external contributions) also uses 2.6.32.  Since this is
>> confusing and people seem to want to use 2.6.35, I'll see if we can
>> integrate the userspace changes needed for 2.6.35 into the master
>> branch.
>>
>> Mike
>>
>> On Mon, Aug 9, 2010 at 3:14 PM, hedwin <hedwin.kon...@gmail.com> wrote:
>>> Mike,
>>>
>>> Sorry asking an ever recurring question, but is 2.6.32 the kernel
>>> version intended for froyo version in the android.git.kernel.org
>>> master branch or is this 2.6.35.
>>>
>>> Hedwin
>>>
>>> On Mon, Aug 9, 2010 at 1:47 PM, Mike Lockwood <lockw...@android.com> wrote:
>>>> Hi Pankaj,
>>>>
>>>> For the next android release after Froyo we will be using new
>>>> notifications between kernel and userspace.  The userspace changes
>>>> have not been released yet and are not included in Froyo.  So for
>>>> Froyo you should continue using the 2.6.32 kernel.  The android 2.6.35
>>>> kernel is for post-Froyo development and is not compatible with Froyo.
>>>>
>>>> As you noticed, there is now a new f_mass_storage.c driver in the
>>>> mainline kernel.  In the 2.6.35 android kernel we abandoned our own
>>>> copy and are now using the mainline 2.6.35 kernel.  So it no longer
>>>> contains the switch code that is used by vold in Froyo to get the UMS
>>>> related notifications.  If it is important that you use 2.6.35 with
>>>> Froyo, you could probably switch back to using the f_mass_storage.c
>>>> from our 2.6.32 kernel in 2.6.35 instead of the mainline version.
>>>>
>>>> Mike
>>>>
>>>> On Mon, Aug 9, 2010 at 3:21 AM, Pankaj <dubepankaj1...@gmail.com> wrote:
>>>>> Hi All,
>>>>>
>>>>> I am facing one issue with Android Froyo and 2.6.35 kernel in getting
>>>>> USB notifications. When I connected USB cable with our device, Windows
>>>>> Host PC detetecd composite device ADB+UMS, but on device there is no
>>>>> notification (normally two notification "usb connected" followed by
>>>>> "usb debugging connected" suppose to come.).
>>>>>
>>>>> When traced back issue i found logcat is showing one warning as "W/
>>>>> Vold No UMS switch available". In 2.6.32 kernel's f_mass_storage.c
>>>>> file fsg_dev structure contains one member as switch_dev and this
>>>>> switch device is registered in mass_storage_bind_config function, but
>>>>> I found that on 2.6.35 kernel's f_mass_storage.c file is not
>>>>> registering switch device and beacause of which in Android Froyo's /
>>>>> system/vold/main.cpp while opening switch device for UMS it failed and
>>>>> thus failed to show notification.
>>>>>
>>>>> So I want to know why switch device registration is removed from
>>>>> f_mass_storage.c file as without it Android Froyo is not able to
>>>>> display connection notifications.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Pankaj
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mike Lockwood
>>>> Google android team
>>>>
>>>> --
>>>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
>>>> website: http://groups.google.com/group/android-kernel
>>>
>>> --
>>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
>>> website: http://groups.google.com/group/android-kernel
>>>
>>
>>
>>
>> --
>> Mike Lockwood
>> Google android team
>>
>> --
>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
>> website: http://groups.google.com/group/android-kernel
>
> --
> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-kernel
>



-- 
Mike Lockwood
Google android team

-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel

Reply via email to