> I have a question about the kernel setting (from the Release 7) > > Why this path is hardcoded in the setting and not givent to the > kernel command line : > > (...) > CONFIG_INITRAMFS_SOURCE="/ media/Littleboy/work/koolu-1.0/out/target/product/freerunner/root" > (...)
> Hmm... I sound like a broken record today... > What is the problem you are trying to solve? nothing, but because i am a linux kernel programmer i don't like hard code so that's just the reason of my question. during the Android analysis, i am looking lot of things everywhere in the system ... > That particular setting is a build-time option that happens to > be stored in the final configuration file. It doesn't affect >the run-time behaviour of the kernel. > The effort required to "fix" that does not provide any benefit > whatsoever as far as I can see, so if you are having a problem > because of it I'd love to hear about it. > Marcelo By the way i am currently working in order to fix the usim access problem ; i need to fix it for my work and i will push back my work if i found a solution. best regards Thierry Gayet 2009/6/15 <[email protected]> > Send android-freerunner mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of android-freerunner digest..." > > > Today's Topics: > > 1. Re: SD card size is 0 and no USB mass storage (Yves Dorfsman) > 2. adb connectivy issue on centos 5.3 using koolu 7 > ([email protected]) > 3. Re: changing init.rc (Marcelo) > 4. Re: Date & Time automatic update (Marcelo) > 5. Re: android-freerunner Digest, Vol 6, Issue 19 (Marcelo) > 6. Re: adb connectivy issue on centos 5.3 using koolu 7 (Marcelo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Jun 2009 07:56:25 -0600 > From: Yves Dorfsman <[email protected]> > Subject: Re: [android-freerunner] SD card size is 0 and no USB mass > storage > To: Android on Freerunner Development > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Brian Code wrote: > > The reason that the HTC Dream creates a /dev/sdx device when plugged in > > is because it supports a combination USB driver in the kernel used on > > the device. Right now, the kernel used on the Freerunner uses the USB > > ether gadget driver which allows a network connection. On the HTC Dream, > > it's a hybrid gadget, ADB/mass storage (which means only ADB is > > accessible, not ADB over usb ethernet on the Freerunner). > > > > If someone wants to port/write that driver into the kernel, you would be > > more than welcome to do so. It's on the (long) list of things to do. > > > > Hi Brian, > > Thanks for your input. Don't hold your breath on this, I tend to get exited > about thousands of things, but get down to do anything only about a few a > year ; I also need to send my FreeRunner in to get the buzz fix right now, > so won't be able to start for a while. > > Anyway, which driver are you talking about here ? > Is this the driver in the Linux kernel that runs underneath Android ? > Or the driver inside Android ? > > > Thanks. > > -- > Yves. > http://www.sollers.ca/ > > > > ------------------------------ > > Message: 2 > Date: Mon, 15 Jun 2009 20:29:04 +0300 (EEST) > From: [email protected] > Subject: [android-freerunner] adb connectivy issue on centos 5.3 using > koolu 7 > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain;charset=iso-8859-1 > > here is what I do: > > [r...@lightsabre android]# ADBHOST=192.168.0.200 adb kill-server > [r...@lightsabre android]# ADBHOST=192.168.0.200 adb devices > * daemon not running. starting it now * > * daemon started successfully * > List of devices attached > > > > there is no usb0 interface anymore after installing > android-freerunner-koolu1.0-beta-7.tar.gz > > For Om 2008.12 there was usb0 and I connected fine with ssh. > > now with android when using dmesg i get the following: > > usb 2-1: new full speed USB device using uhci_hcd and address 4 > usb 2-1: configuration #1 chosen from 2 choices > eth2: register 'cdc_ether' at usb-0000:00:1a.1-1, CDC Ethernet Device, > 00:1f:11:01:92:8a > > > if i do the following: > $ ip addr add 192.168.0.200/24 dev eth2 > $ ip link set eth2 up > > then i can ping 192.168.0.200 and also ping 192.168.0.202 > ssh 192.168.0.202 does not work > > If i understood correctly adb works only with usb interfaces? > anyone has an idea how I make adb sees the eth2? or why i dont get usb0 > anymore? > > thanks > > > > ------------------------------ > > Message: 3 > Date: Mon, 15 Jun 2009 12:45:03 -0600 > From: Marcelo <[email protected]> > Subject: Re: [android-freerunner] changing init.rc > To: Android on Freerunner Development > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Fri, Jun 12, 2009 at 07:45, <[email protected]> wrote: > > > I want to mount my rootfs a+rw.... > > What for? > > In your description you provided a way to do just that, so I'm assuming > that this is not really what you want to do, but instead the way that > you have devised to solve a different problem that you didn't specify. > > If you wish you specify the actual problem that you wish to solve, > maybe someone can help you find a diffrerent solution. > > Marcelo > > > ------------------------------ > > Message: 4 > Date: Mon, 15 Jun 2009 12:50:11 -0600 > From: Marcelo <[email protected]> > Subject: Re: [android-freerunner] Date & Time automatic update > To: Android on Freerunner Development > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Sun, Jun 14, 2009 at 12:16, Yves Dorfsman<[email protected]> wrote: > > > Does anybody know how the automatic setting works ? Does it use > > the GPS ? I know the CDMA network send time information on the > > network, but I believe that this isn't true on the GSM network > > ? What about 3G, I heard 3G is similar to CDMA, do they send > > time information on the 3G network ? Would that be how the > > dream sets it's time ? > > My Nokia phone is GSM and it can pull the current time from the > network just fine. When I turn it on it asks me for the current > date and time, I just close that dialog and after a few seconds > it updates the date/time to the current values on its own, so I > assume GSM provides a mechanism to do this (likely it's an > option that the network operator has to enable). I've seen this > work on several different networks and different countries. > > Marcelo > > > ------------------------------ > > Message: 5 > Date: Mon, 15 Jun 2009 12:55:38 -0600 > From: Marcelo <[email protected]> > Subject: Re: [android-freerunner] android-freerunner Digest, Vol 6, > Issue 19 > To: Android on Freerunner Development > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Jun 15, 2009 at 06:26, Thierry GAYET<[email protected]> > wrote: > > > I have a question about the kernel setting (from the Release 7) > > > > Why this path is hardcoded in the setting and not givent to the > > kernel command line : > > > > (...) > > > CONFIG_INITRAMFS_SOURCE="/media/Littleboy/work/koolu-1.0/out/target/product/freerunner/root" > > (...) > > Hmm... I sound like a broken record today... > > What is the problem you are trying to solve? > > That particular setting is a build-time option that happens to > be stored in the final configuration file. It doesn't affect > the run-time behaviour of the kernel. > > The effort required to "fix" that does not provide any benefit > whatsoever as far as I can see, so if you are having a problem > because of it I'd love to hear about it. > > Marcelo > > > ------------------------------ > > Message: 6 > Date: Mon, 15 Jun 2009 12:59:44 -0600 > From: Marcelo <[email protected]> > Subject: Re: [android-freerunner] adb connectivy issue on centos 5.3 > using koolu 7 > To: Android on Freerunner Development > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Jun 15, 2009 at 11:29, <[email protected]> wrote: > > > eth2: register 'cdc_ether' at usb-0000:00:1a.1-1, CDC Ethernet Device, > > 00:1f:11:01:92:8a > > > > > > if i do the following: > > $ ip addr add 192.168.0.200/24 dev eth2 > > $ ip link set eth2 up > > > > then i can ping 192.168.0.200 and also ping 192.168.0.202 > > ssh 192.168.0.202 does not work > > There's no ssh daemon running on Android. > > After you do this, you can go back to the first steps that you > mentioned and ADB should be able to connect. On the Freerunner, ADB > connects over IP over Ethernet over USB. > > Marcelo > > > ------------------------------ > > _______________________________________________ > android-freerunner mailing list > [email protected] > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org > > > End of android-freerunner Digest, Vol 6, Issue 22 > ************************************************* > -- Cordialement Thierry GAYET +33.663.849.589
_______________________________________________ android-freerunner mailing list [email protected] http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
