The adb kernel driver actually could support another protocol. The only limitation is that there is a maximum 4096 byte packet size. Of course you would need to write your own program on the PC that understands the data you are sending from the device. And you could not use adb at all if you hijack the adb driver for another purpose.
You could use the adb sources as a starting point for whatever it is you are trying to do. But it sounds like it would be a non-trivial effort and I don't think anyone on this mailing list will be able to help you with it. Mike On Wed, Feb 25, 2009 at 8:32 PM, Ramy <ramal...@gmail.com> wrote: > > You mean to say that the controller driver provided for msm 7200 will > only work with adb protocol. can it be changed or customized to meet > any specific protocol. > > > On Feb 26, 12:23 am, Mike Lockwood <lockw...@android.com> wrote: >> On Tue, Feb 24, 2009 at 11:59 PM, Ramy <ramal...@gmail.com> wrote: >> >> > Hi all, >> >> > I am very new to the android env. please bear with me if my question >> > is too fundamental. >> >> > I am using a peripheral driver with no host support for USB. >> > I am trying to use the adb driver to transfer a file. The adb driver >> > is compiled fine and two device are created in the kernel. android_adb >> > and android_adb_enable. >> > I understand that the android_adb_enable device must always be enabled >> > to use the android_adb device. I try to copy a file to device /dev/ >> > android_adb using cp command. >> >> > cp ***.txt /dev/android_adb >> >> > but when i try to read the same using the cat command i get >> >> > rx c1cf4fa0 queue >> > rx c1cf4f60 queue >> > rx c1cf4f20 queue >> > rx c1cf4ee0 queue >> >> > and waits.... >> >> > why am i not able to see the output using the cat command ? what is it >> > wiating for ?? >> >> Hi Ramy, >> >> You can't just write arbitrary data to /dev/android_adb and expect it >> show up on the host side. adb (on the host) and adbd (on the device) >> communicate with each other via a structured protocol. The >> /dev/android_adb driver file is intended to be used only by the adbd >> daemon. You can't write to it yourself unless you send data using the >> adb protocol. >> >> -- >> Mike Lockwood >> Google android team > > > -- Mike Lockwood Google android team --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
