g_file_storage problem using linux kernel 2.6.28 on SMDK2440 platform
sdshliyong at 163.com
Thu Feb 19 02:32:06 CET 2009
Below is the patch, It can resolve the remmod g_file_storage issue, However,
it cannot resolve the first issue.
< if (driver->unbind)
----- Original Message -----
From: "Michael Trimarchi" <trimarchi at gandalf.sssup.it>
To: "YongLi" <sdshliyong at 163.com>
Cc: <openmoko-kernel at lists.openmoko.org>
Sent: Wednesday, February 18, 2009 4:25 PM
Subject: Re: g_file_storage problem using linux kernel 2.6.28 on SMDK2440
> YongLi wrote:
>> Hello All,
>> I am testing the g_file_storage module on SMDK2440 platform using linux
>> there are two problems:
>> 1. If I enable the VERBOSE_DEBUG and DUMP_MSGS in the File_storage.c,
>> Winxp host can get the U disk,
>> however, if I disable the debug option, Winxp host cannot get the U disk!
>> If I use dmesg -n 2 to disable
>> console debug message, Winxp host cannot get the u disk too. It seems
>> that there is a timing issue.
>> 2. rmmod g_file_storeage cause the kernel panic! It seems that the
>> usb_gadget_unregister_driver function in s3c2410_udc.c does not call the
>> unbind function. Can I add the below code in this function:
>> if (driver->unbind)
>> Any suggestions will be appreciated
> Prepare a patch :) and send to the mailing list. So I can take a look at
> the code.
More information about the openmoko-kernel