I ran into the same issue a while back. I started to make a patch to
drivers/usb/gadget/f_acm.c to fix it, but got sidetracked. The
ordering workaround does not help when you have more than one ACM in
your config. Fortunately for me, I am using the ACMs for raw serial,
and not as modems, and I d
Hi Jagan,
This is my case, acm If# is not mapped to interface desc given from device.
So I put "acm" to first order then the acm interface can be located at first
one (If# = 0) on desktop side.
Desktop side
cat /sys/kernel/debug/usb/devices
S: Product=Android HSUSB Device
S: SerialNumber=123456
Thanks Squall.
Could you tell me what is the significance of specifying particular USB
function in first order like
static char *usb_functions[] = {
#ifdef CONFIG_USB_ANDROID_RMNET
"rmnet",
#endif
#ifdef CONFIG_USB_ANDROID_RNDIS
"rndis",
#endif
"usb_mass_storage",
"adb",
//#
Hi Jagan,
No, you need to assign correct values into bMasterInterface0 and
bSlaveInterface0 instead of values generated dynamically.
There is an easy way can avoid this problem and lets you continuing
your work. You can try to re-range items in array, "usb_functions"
like sample make acm to be fir
means can i remove the comments on bMasterInterface0 & bSlaveInterface0.
is that the solution.
On Wed, Apr 13, 2011 at 2:17 PM, Squall.Hung wrote:
> Thanks All,
>
> I found the root cause and solved it on device side.
> In my cause bMasterInterface and bSlaveInterface of usb_cdc_union_desc
> are
Thanks All,
I found the root cause and solved it on device side.
In my cause bMasterInterface and bSlaveInterface of usb_cdc_union_desc
are not correctly mapped to host side (usb interface generation).
Temporary I changed the sequence of usb function initialization (make
acm be as first one initia
Hi,
Update the messages on my host, ACM can not be recognized.
cat /sys/kernel/debug/usb/devices
C:* #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=500mA
A: FirstIf#= 6 IfCount= 2 Cls=02(comm.) Sub=02 Prot=00
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-
storage
E: Ad=83(I) Atr=02(Bulk)
Hi Steve,
Sorry, let my explain my trouble. My ADB works well before I modprobe
usbserial, see below messages.
cat /sys/kernel/debug/usb/devices
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdI
On Apr 6, 2011, at 8:59 PM, Squall.Hung wrote:
> Hi,
>
> I don't really know what you mean about the instructions for updating
> the udev configuration?
> May you tell me more details what instructions you mentioned for
> update udev?
I think he's referring to this:
http://annoyingtechnicaldet
Hi,
I don't really know what you mean about the instructions for updating
the udev configuration?
May you tell me more details what instructions you mentioned for
update udev?
thanks,
chihchia
On 4月5日, 上午8時00分, A Curtis wrote:
> > I have same question, too.
> > CDC-ACM works well with usbserial
>
> I have same question, too.
> CDC-ACM works well with usbserial, but USB ADB feature gets trouble
> after modprobe usbserial .
>
Did you follow the instructions for updating the udev configuration?
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/g
Hi All,
I have same question, too.
CDC-ACM works well with usbserial, but USB ADB feature gets trouble
after modprobe usbserial .
Do anyone have idea? Please help me.
Thanks,
Chihchia
On Mar 23, 6:21 pm, jagan <402ja...@gmail.com> wrote:
> Hi,
>
> I am working on Android Gingerbread kernel upgr
12 matches
Mail list logo
