-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
-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:
| 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:
|
-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:
| - 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:
| On Wed, Jan 28, 2009 at 3:50 PM, Andy Green a...@openmoko.com wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| Somebody in the thread at some point said:
|
| | - Wifi-icon is on
| | - tangoGPS
-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
-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.
|
|
| what's
-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:
| 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
-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
-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...@openmoko.com 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
-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
-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:
| 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
-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:
| 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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/2/3 Stefan Fröbe frob...@googlemail.com
| mailto:frob...@googlemail.com
|
|
| Just create a textfile /boot/append-GTA02 and put whatever is
| needed as kernel parameters in there - here is
-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..
|
|
-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
-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 van...@penguin.cz
| mailto:van...@penguin.cz wrote:
|
| ...
| i understand that this is when you run system from sd card. i run
| system from NAND
-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 wrong
-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
|
-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 the
-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 bug I
-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:
| 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:
| 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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Michael 'Mickey' Lauer mic...@openmoko.org 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
-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:
| Andy Green a...@openmoko.com 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 21 10
-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 cchan...@yahoo.com 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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green a...@openmoko.com 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Simon Kagstrom simon.kagst...@gmail.com 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
-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
-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:
| 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:
| 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:
| 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:
| Johny Tenfinger wrote:
| On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber jo...@openmoko.org
wrote:
| * Change the led transistor power hungry stuff
| Guys, this has been fixed for *ALL* FR ever sold!!!
|
-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 limit resistor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green a...@openmoko.com 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 triggers
-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 shielded
-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
-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:
| 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 unless
-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:
| 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2009/3/9 Andy Green a...@openmoko.com mailto:a...@openmoko.com
|
| [...]
| What does the noise look like, is it also the top-down block of
static
| random pixels described on the trac
401 - 450 of 450 matches
Mail list logo
