> Can you send at command on ttyUSB0 ?
Sorry, I do not know what you mean.
> If yes then you need to try to put the reference ril on it and see
what happens... (start it with "-d ttyUSB0")
What do you mean put the reference ril on it?
Are you talking about ril-daemon in init.rc?
service ril-daemon /system/bin/rild
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio sdcard_rw
On Mar 17, 5:41 pm, Maffiou <[email protected]> wrote:
> Can you send at command on ttyUSB0 ?
>
> If yes then you need to try to put the reference ril on it and see
> what happens... (start it with "-d ttyUSB0")
>
> Having just one com port may be a bit of a challenge if you want to do
> data...
>
> M.
>
> On Mar 16, 7:38 am, BiX <[email protected]> wrote:
>
>
>
>
>
>
>
> > Sorry I do not understand how to get it working with Ubuntu desktop.
> > I only know FTDI driver is needed because an 'lsusb' returns 'Future
> > Technology Devices International, Ltd FT232 USB-Serial (UART) IC'.
>
> > Beagleboard booting:
>
> > Initializing USB Mass Storage
> > driver...
> > usbcore: registered new interface driver usb-
> > storage
> > USB Mass Storage support
> > registered.
> > usbcore: registered new interface driver
> > usbserial
> > USB Serial support registered for
> > generic
> > usbcore: registered new interface driver
> > usbserial_generic
> > usbserial: USB Serial Driver
> > core
> > USB Serial support registered for
> > debug
> > usbcore: registered new interface driver
> > debug
> > USB Serial support registered for FTDI USB Serial
> > Device
> > usbcore: registered new interface driver
> > ftdi_sio
> > ftdi_sio: v1.5.0:USB FTDI Serial Converters
> > Driver
> > USB Serial support registered for
> > funsoft
> > usbcore: registered new interface driver
> > funsoft
> > USB Serial support registered for GSM modem (1-
> > port)
> > usbcore: registered new interface driver
> > option
> > option: v0.7.2:USB Driver for GSM modems
>
> > When I plug in the gsm board:
>
> > usb 1-2.1: new full speed USB device using ehci-omap and address
> > 3
> > ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter
> > detected
> > usb 1-2.1: Detected
> > FT232RL
> > usb 1-2.1: Number of endpoints
> > 2
> > usb 1-2.1: Endpoint 1 MaxPacketSize
> > 64
> > usb 1-2.1: Endpoint 2 MaxPacketSize
> > 64
> > usb 1-2.1: Setting MaxPacketSize
> > 64
> > usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0
>
> > On Mar 16, 10:46 am, Hamilton Vera <[email protected]> wrote:
>
> > > Hi there, maybe the best approach is to make it work with your linux
> > > desktop, if you did that please let me know how.
>
> > > Probably this device will be handled by a serial driver acm or usb, if
> > > you have one device created it is a good start.
>
> > > If the low level driver part is ok we will deal with RIL. Please let
> > > me know about this.
>
> > > On Fri, Mar 11, 2011 at 5:55 AM, BiX <[email protected]> wrote:
> > > > I am using a gsm modules as shown
> > > > >http://www.google.com/url?sa=D&q=http://www.sparkfun.com/products/9427
> > > > Currently, I've built FTDI serial driver and BeagleBoard recognize it
> > > > but Android does not receive any signal.
> > > > Can someone enlighten me on the modules or steps I am missing ?
> > > > Thanks.
>
> > > > --
> > > > unsubscribe: [email protected]
> > > > website:http://groups.google.com/group/android-porting
>
> > > --
> > > Hamilton Vera
> > > int Administrator (char Network[],char
> > > ComputationalSystems[])http://hvera.wordpress.com @hamiltonvera
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
