-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/3/9 Andy Green mailto:a...@openmoko.com>>
|
| [...]
| What does the "noise" look like, is it also the top-down block of
static
| "random" pixels described
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I'm experiencing read/write error on my 8GB SD card Kingston C08G
| SDC4/8GB 07 (wiki reports this card shoud work!) with 2.6.28 shr-testing
| kernel and with 2.6.24 from 2008.12, followed some times by NSOD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|1. Charger (maybe with Y-cable) connected. Detected by 47 kOhm seen
on ID
|pin. Set USB mode to host and turn off USB power supply.
|
|2. USB headset connected. Detected by ? Set USB mode to host
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| http://wiki.openmoko.org/wiki/GTA02_bass_fix
Yes it's a different way to come at it.
By putting the caps in that case void 100uF will fit easily, but it
needs long leads, the leads violate the can frame /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Lifting the can and meddling with the caps is nontrivial. Somebody did
|> give this plan a go on the list about 6 months ago and reported some
|> success though. But I don't recommend considering it unle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> There are a couple of 1K resistors to 0V that will then connect directly
|> ~ to the amp outputs all the time before the new DC blocking caps you
|> will add back in. But thanks to some recent patches by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> I think there's a little confusion going on here, AIUI Werner did the
|> rootfs end and Deiter the GSM firmware upgrade and deserve the thanks
|> for that.
|
| You haven't understood it quite right, and ob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> I have suggested a refinement on the second approach: short the small
|> capacitors. Add big caps outside the shielded unit - there are places
|> with room. But don't put wires from the caps into the shield
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, 5 Mar 2009, Paul Fertser wrote:
|
|> Alternatively, try Joerg's uSD automated image:
|>
http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz
|>
|> It works and reliab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green writes:
|>> So, please consider changing the framework to use the red LED to
|>> indicate the
|>> battery charge state.
| ...
|> I did not find a way myself to list the trig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>> It was fixed on A6, I'm afraid we just have to let it lie and not use
|>> the AUX LED much as pointed out unless we're on external power.
|> Now that's an idea. How about using it as a battery charging in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, Mar 05, 2009 at 01:19:07AM +0100, Fox Mulder wrote:
|> Andy Green wrote:
|>> Johnny Tenfinger is right despite it sounds strange. On some or all A5s
|>> there is no base current li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Johny Tenfinger wrote:
|> On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber
wrote:
|>>> * Change the led transistor power hungry stuff
|>> Guys, this has been fixed for *ALL* FR ever sold!!!
|> No, no, no. Yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi all,
|
| Are more people experiencing on latest SHR unstable (built feb 28):
| - screen flickering
| - instable wifi connection
| - no PIN dialog popping up when booting from Qi, it does come up when
| bo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Michael 'Mickey' Lauer wrote:
|
|>> I don't think that they simply disable the backlight. Resuming from SHR
|>> unstable takes about 5-6 seconds (no incoming call), while 2008.12
resumes
|>> under 3 seconds.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Daniel Benoy wrote:
|> Apparently bluez supports sending mp3 data directly to bluetooth stereo
|> headphones, rather than using CPU taxing SBC compression encoding.
|>
|> (FYI: The way to test direct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Are you booting from NAND or NOR flash? I know when I boot from NAND
| flash I see a bunch of text scroll by on resume. I don't see that
| when booted from NOR. I don't know why... Have you tried that?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Your points are good and you have defined a good area to pay atention
| sysfs ,but you have to consider that .28 kernels are not being adopted
| by any official Openmoko release yet, but start working on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Simple question, why did the squashfs kernel module disappear in the
| 2.6.28/29 builds. It was there for .24?
|
| Can it be brought back? I spent a weekend of CPU time building a
| smallish image of the En
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Simon Kagstrom writes:
|> From looking at the diagram, I think that would make sense at least. I
|> haven't figured out how to affect these still from looking in the state
|> file and in the driver though.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I have just flashed my freerunner with the latest SHR unstable images:
|
http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.jffs2
|
http://build.shr-project.org/shr-unstable/images/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green writes:
|> As I understand it, the problem with CPU digital audio on BT is that
|> there is no routing path in the WM8753 hardware between the two digital
|> audio interfaces (CPU and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hmm... What does this mean then? Is this to say that streaming voice
| from the GSM directly to BT isn't possible as described on
|
| http://wiki.openmoko.org/wiki/Neo1973_Audio_Subsystem
|
| ? I'm not ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Sat, 21 Feb 2009 19:47:37 -0800 (PST)
| c_c wrote:
|
|>> I've tried both a Nokia BH-604 and a SonyEricsson HBH-PV700, both
|>> work for outgoing audio but not incoming.
|> There's been some discussion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green writes:
|> | Sat Feb 21 02:01:01 EET 2009 65 %
|> | Sat Feb 21 04:01:06 EET 2009 58 %
|> | Sat Feb 21 06:01:00 EET 2009 52 %
|> | Sat Feb 21 08:01:04 EET 2009 45 %
|> | Sat Feb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I think you will get > 3 hours with the FR and gps - I had it on full
| brightness (no suspend and screen on) for about 3 hours - then events/0
| runaway killed it :( Thats with 2008.12, maybe FSO/SHR will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| "Michael 'Mickey' Lauer" writes:
|> FYI: http://wiki.openmoko.org/wiki/StandbyLifetime
|
| Was that with or without GSM deep sleep? Without deep sleep and
| automatic calls every two hours the battery does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| It often happens to me that when I turn on the phone, Qi turns it off
| again after a few seconds, when the boot process has already started. It
| only boots normally when I turn it on the second time. Might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
|
| I've been using 2008.12 for a while now and it works really good. But
| there's a need to change to a 2.6.28 kernel due to some bugs. I tried
| the newest andy-tracking, but it's really unstable.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| QI
|
|> Make sure you have the "rw" in there, and the /boot/append-GTA02 is in
|> the partition with the rootfs. Try adding a space before the rw in case
|> I mangled it with recent changes.
|>
|> It's a bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> I'm just adding some patches and doing some cleaning on it, I'll update
|> the moredrivers kernels at http://people.openmoko.org/andy when I
|> checked we didn't break the threshold stuff.
|
| Thanks, in th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>> It's a good guess... does mount say that it's still ro?
|
| i have flashed u-boot and it starts OK. reflashed qi and have the
| problem again. interestingly enough i tried to boot fso from nor menu
| once
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| | rw rootdelay=3 glamo_core.slow_memory=1
|
|
| that's for a SHR kernel mentioned somewhere on this list (
| uImage-2.6.28-rc4-ms5-fixes_34240a1c06ae3618.bin ) but not fixing the
| White
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
|
| On Tue, Feb 3, 2009 at 9:48 PM, Petr Vanek mailto:van...@penguin.cz>> wrote:
|
| ...
| i understand that this is when you run system from sd card. i run
| system from NAND and for that i need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
|
| opps.. the message saye "glamo3362.slow_memory" NOT glamo33362 as i wrote!
Wah my mistake... it really is glamo_core, it appears in /sys as
/sys/module/glamo_core/parameters/slow_memory
I read my wron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| I have the QT on the rootfs, so I put the FSO on a uSD (I have
installed the
| QI).
|
| ITS impossible to boot from the uSD, QI just seems to ignore the FSO
and it
| just boots to NAND kernel..
|
| I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/2/3 Stefan Fröbe mailto:frob...@googlemail.com>
|
|
| Just create a textfile "/boot/append-GTA02" and put whatever is
| needed as kernel parameters in there - here is mine:
| rw rootdelay=3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> There is a quick workaround for this that can be done I believe.
|
| Any hint where I can find this workaround, then I'll post it to the wiki?
I'm just adding some patches and doing some cleaning on it, I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| this happens only with qi. could it be related to ro kernel
| parameter?
It's a good guess... does mount say that it's still ro? Normally an
initscript will take care about remount rw after it had opportu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> This is reminding me of a problem we have with level interrupts on
|> pcf50633 new driver, we also get twice the same interrupt there although
|> the density of interrupts is so low and logically it cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| I used so far the uImage-gta02-gc7283981_mwester-stable.bin , it works
ok ,
| except the battery icon animates like is being charged (this happens
when I
| boot the FR, I could "fix" this, by connect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Somebody in the thread at some point said:
| | I meant the second latest one posted on http://people.openmoko.org/andy/
| | which is uImage-moredrivers-GTA02_andy-tracking_f2d78193eae5dccd.bin
| |
| | On Sun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I meant the second latest one posted on http://people.openmoko.org/andy/
| which is uImage-moredrivers-GTA02_andy-tracking_f2d78193eae5dccd.bin
|
| On Sun, 2009-02-01 at 19:27 +0200, Timo Jyrinki wrote:
| ..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Le Thu, 29 Jan 2009 20:31:30 +,
| Andy Green a écrit :
|> I would look at the flat cable carefully, the gold fingers at both
|> ends and the neck where it widens. First my flat cable cracked at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| It's very interesting. Will it act as a wireless access point?
Nope. AR6000 doesn't support master mode.
But it's still interesting, well done to the people who worked on it.
- -Andy
-BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I didn't have tools to make electronics and soldier wires to h-tp150*
| dots, so I wonder if someone had already got success with scotch and
| small copper wire ? wiring these dots to the 20 pins empty conn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| POWER_SUPPLY_CAPACITY=0
| POWER_SUPPLY_ONLINE=1
I guess it got confused about charging or not and came down on the not
side. That shouldn't happen any more on a newer kernel.
| OM2008.12 doesn't support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>> My laptop's wifi does get warm too, if under heavy load.
|> Yes, but it's not loaded! Basically there aren't any networks around
|> that I can wifi into, so wifi is left on useless at the moment.
|
|
| wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> It's hard to guess where the power is going if you can't ssh into it.
| I'll go home and check if I can still SSH into it from Ubuntu.
If you can, look at the /sys for bq27000 idea of temperature and curr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wed, Jan 28, 2009 at 3:50 PM, Andy Green wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Somebody in the thread at some point said:
|>
|> | - Wifi-icon is on
|&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| - Wifi-icon is on
| - tangoGPS shows movement (so, GPS is on)
| - 'battery' icon shows a nice flash
| - red light in AUX is on
|
| Note the absence of any cables to the FR at the moment :-)
What kernel is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| telnet_port
| gdb_port
| interface ft2232
| jtag_speed 0
This misnamed "jtag speed" is actually a delay factor. Try 8 or so.
Only certain magical versions of libftdi will work. 0.8 works fine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>>> Where did you get the kernel from? Is there a git hash on the
filename?
|>> I grabbed the kernel from
|>> http://build.shr-project.org/shr-unstable/images/om-gta02/
|>> The hash is:
|>> gitr34240a1c06ae3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
|
| My first post on the mailinglist :-) because I don't know how to fix
| this :-(
|
| Today I downloaded the latest kernel and shr-lite-testing release, ran
| into u-boot and flashed my Freerunner.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> are you sure this isn't just the synchronization events?
|
| For me the problem looks like this.
|
| |type| |code| |-value-|
| 0006 -> Seperator time 1
| 0006 0002 00
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| So the right command line would be something like "./build GTA02 dummy"
| to find within the "GTA02" directory the modules tar.gz afterwards.
Yes but dummy really is a dummy param, it is just checked if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I took a closer look at the build script and i'm quite sure that i'm
| interpreting it correct.
| Maybe the name "dummy" as first parameter is not very good. In the wiki
| it uses "dummy" as first parameter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| => 2.6.28
| * Framework already supports both kernels (.24 & .28).
| * Next FSO milestone will come with support for both kernels. If .28
proves to
| be stable enough in the coming weeks .24 support may be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi all,
| I've been messing with u-boot and need some help.
| I was trying to set the "rw" parameter into bootargs to boot 2008.12
| from SD. After a couple attempts, I had too many entries in the u-boot,
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Em Sab, Dezembro 27, 2008 04:06, Kosa escreveu:
|> I've been trying to boot 2008.12 from a microsd but it just can't.
|> It starts booting but then it stops with an "Only GTA01 hardware
|> supported by ASoc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Am Fr, den 19.12.08 um 01:53 schrieb Jos vd Snepscheut:
|> I have been installing debian on my SD cart using this script:
|> wget http://pkg-fso.alioth.debian.org/freerunner/install.sh
| with 'QI=tru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> Aah didn't I read that this new rootfs does not remount / -orw... as a
|> workaround you aren't meant to use ro on the kernel commandline...
|> that'll b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Cons :
| - Didn't boot after flash. I made several tries, it was stuck at
debugfs dir
| creation failed. I had to aux+power, choose boot and it worked. Now it
| works. (i'm using QI)
My guess is this might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green schrieb:
|> Somebody in the thread at some point said: | Hello there, | | i
|> don't know, what's wrong, but i had just in the beginning some |
|> failures like | | tar: cann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello there,
|
| i don't know, what's wrong, but i had just in the beginning some
| failures like
|
| tar: cannot create directory 'device/bus': Read-only file system
|
| this is created for every folder; in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Lets add another information layer to open street map, containing
| discovered or already-tried-but-failed wpa-keys. Then each gta03
| synchronize with the current state of your home town and start trying
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, Dec 18, 2008 at 4:40 PM, Andy Green wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Somebody in the thread at some point said:
|>
|> | ker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| kernel - 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1
|
| /proc/version is:
|
| Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri
| Oct 17 17:20:36 UTC 2008
Yow it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> | I tried twice, and had it both times. I had some other issues with om,
|> | so I flashed back to shr. I've got A6 I believe, how to check that?
|>
|> cat /proc/cpuinfo should mention "Revision" as 0x35
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> Somebody in the thread at some point said:
|>
|> | I noticed a fresh kernel in your directory, so I flashed it. It seems
|> | to resume, which is nice, but after su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I noticed a fresh kernel in your directory, so I flashed it. It seems
| to resume, which is nice, but after suspending and resuming once, there
| is noise on the screen, the bad TV antenna sort. Subsequen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| i'm not sure how to turn on framebuffer blanking but i will do some
| research and use that for a bit and report back; however, i have used
| other distros where frameblanking was the norm and never had wso
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Oh, good luck with GTA03 resume then. Resume never was easy :)
Linus loves it too
''Now, suspend/resume debugging is some of the nastiest crud around...''
http://torvalds-family.blogspot.com/2008/12/debu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I'm afraid you need at least c59a8bdc7ca4b5470ebc43dfc31ed1d3d23a7c6f
| to get stable operation with suspend/resume working. The latest image
| at Andy's is from Dec 5, and the revision i use on the phone i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> ok, so i flashed the images above and then did a wget for the kernel
|> opk and then did a opkg install
|>
kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk.
|>
|>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello Andy,
| thanks for reacting. still have some questions if I may?
| Is the renaming needed? or can I use the origional kernel name?
It's going to check for exactly "/boot/uImage-GTA02.bin" in the firs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
|
| I'm using qi-s3c2442-master_2ad3ce6ff57753e3.udfu
| 01-Dec-2008 02:23 26K
|
| and a sd card (came with FR 512) with ext3 and I have put the
| kernel-file into /boot as uImage-GTA02.bin (yes I re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2
|
http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin
|
| booted it up and within 5-10 suspend
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| i have been reading about this fix for a couple weeks now and how it
| is in andy-tracking and testing and how it was supposed to be in
| stable "soon." reading your email, andy, i assume that it is now in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| For the WSOD, I recommand you to use the SHR distribution.
|
| I had the same problem for a few month, killing any usuability of the
| phone, but since SHR have resolved it, it's far more enjoyable to use
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Okay; two Freerunner units, one restores semi-okay, one's screen
| typically goes all black after an otherwise successful restore (not
| before showing the appropriate display for a moment though), doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| After power down (battery taken out) restarting with aux and power
| button I get the same screen with menu as before, is this correct?
| How can I see that Qi now is beeing used (and not uboot?)
If you ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Andy Green writes:
|> | while, it gets unable to go to sleep. I can press the power button ten
|> | times, it still stays on. Only way I found for now is to reboot. Not
|> | pretty :/
|>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| while, it gets unable to go to sleep. I can press the power button ten
| times, it still stays on. Only way I found for now is to reboot. Not
| pretty :/
This is a kernel issue I think, it should be gone i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, Dec 11, 2008 at 11:49:03AM +0100, Helge Hafting wrote:
|> Rui Miguel Silva Seabra wrote:
|>> Am I completely daft or isn't the focus on FSO and Paroli et all
|>> precisely what you're whining about?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| I've been trying to compile openmoko kernel and I can't even start
| because of this dummy error:
|
-
-
| $ ./
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This is not listed in the wiki.
|
| I can successfully boot from the SD card, using Hackable:1 (thanks
| folkes), and ssh into the SD card (thanks Arne, clare, Christopher &
Joel).
|
| Now that all of this c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The problem is:
| This is afaik not a fix but a workaround which costs battery power.
| So I think there should be two kernels:
| One with and one without this patch.
There's a small hit on suspend current,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| When in BootLoader, shows that there is a card of 3MB and when I
| boot with the latest 2008.9 jffs I get following dmesg output:
U-Boot driver doesn't understand enough SHDC to get this right, but it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, 2008-12-04 at 13:54 +0100, arne anka wrote:
|>> improved in andy-tracking. If it's due to firmware trouble, probably
|>> this will never be fixed due to Atheros closed firmware policies.
|> wasn't t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Wifi has been working (for some values of working) for a long while...
|> what bad behaviour does "not working" look like for you?
|
| Well, if you ask for it:
| - can only connect through command-line (no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| On Wed, 2008-12-03 at 16:36 +, Andy Green wrote:
|> ~ - WLAN driver now uses mainline SDIO stack (should fix some probs)
|
| Does that mean WiFi is working now ?
Wifi has been working (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Franky Van Liedekerke wrote:
|> On Thu, 04 Dec 2008 01:12:59 +0700
|> Sean McNeil <[EMAIL PROTECTED]> wrote:
|>
|>
|>> I'm uploading a new image right now that includes Ruis virtual
|>> keyboard. Please give
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I have tried to flash the u-boot from the daily release.
| After booting up in NOR, I have used the file
| gta02v5_and_up-u-boot.bin, I am unable to boot up in NAND?
| When I press power and then aux, the AU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I was considering starting to use the Neo as a daily phone, so I need to
| dualboot.
|
| Are there anything special I need to consider to make the partitioning
| compatible with future Qi bootloader?
|
| I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've seen a lot of references to the "andy-tracking" kernel. A search
| of archives yields some info about this with regard to a shift to the
| 2.6.27 kernel. However, I've not been able to really underst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Apologies in advance for what may be a dumb question - but does this
|> statement represent the conclusion of your team's work on audio issues
|> (buzz/echo/hiss etc.)? Or is there further work ongoing?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Thanks your suggestion giving and thanks Andy. I am trying testing
| suspend/resume recursively with a script, using werner's wkalrm. If
| anything I get or any plan, anyway I will talk on kernl list, l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| What i'm trying to explain is that i see it as plain obvious that
| anybody who wants to work on a kernel stuff should coordinate their
| efforts on the kernel list. That anybody targeting fixing bugs in
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| Andy Green <[EMAIL PROTECTED]> writes:
|> For example some advice for Jeremy about "suspend / resume issues"
|> would be don't waste your time doing any suspend / resu
1 - 100 of 487 matches
Mail list logo
