I might have a problem with changing reference-ril.c. It's not in my
Supersonic source tree.
Those sound like radio-related changes. Do I need those if I'm only
going to use CDC ACM through the USB port? And the phone will be the
gadget or device. The other end is the host USB side. Actually, the
You will only need to compile your kernel using CONFIG_USB_ACM=y .
Then you must modify your reference-ril.c, init.rc and
system/etc/init.gprs-pppd .
- reference-ril.c respecting your modem capabilities
- init.rc service ril-daemon /system/bin/rild -l
/system/lib/libreference-ril.so -- -d /dev
You're right, Mike. I didn't think of that. I'm using the kernel
source for the Evo from the HTC developer site. They must have added
CONFIG_USB_ANDROID_SERIAL. I didn't check it against the AOSP source.
Sounds like, unless they've introduced some dependency, that I could
get by with only CONFIG_U
I don't see any sign of CONFIG_USB_ANDROID_SERIAL in my kernel
sources. Which kernel branch are you working from?
I know some people are using the gadget ACM serial support in our
2.6.36 tree in the common repository on kernel.org, so that should be
working. But it sounds like you might be using
I'm trying to configure an Android kernel to support connecting the
phone as a USB gadget using the CDC ACM protocol. I'm making progress
in understanding how to configure the kernel for this, but it seems
something new pops up every day. One thing I don't understand about
the Android Gadget config
On Mon, Dec 13, 2010 at 11:07 AM, tstanly wrote:
> hi all,
>
>
> I followed the site bellow to download the kernel code,
> http://android.git.kernel.org/?p=kernel/common.git;a=summary
>
> from the instruction,
> ===
> To clone the entire platform, install repo, and run:
> mkdir mydroi
Oh, I should add - this is for giving applications raw unix-type
access.
A lot of things on android reserve that for something running in the
system server process under the system group, and have it export
android services to applications, putting the permission checks on the
exported interfaces.
Assuming your device driver is interacted with via a device file, I
think the cleanest of currently in-use mechanisms is to create a unix
group for your capability and set the device file to be owned by root
but with that as the group and as appropriate read or read/write
permissions to the group.
Follow-up. Looks like I was approaching this entirely wrong. Instead,
I turned on CONFIG_USB_ANDROID_ACM and used the Android Gadget
composite driver. At first, couldn't get it to compile, but then I
found other posts, e.g.,
http://atechyblog.blogspot.com/2010/08/enabling-serial-port-on-nexus-one.
