Re: SD Card read/write errors and NSOD
-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 (Noise | Screen of Dead). | | This does not happen when GSM is off. | | I found a similiar problem on http://docs.openmoko.org/trac/ticket/2217 | , the difference is that I have the problem with 2.6.24 kernel too! (I | followed the suggestion to down the glamo clock and the slow memory | without success) | | Before updating the ticket with my details I'd like to know if there is | kernel version suited to test this better, and have community feedback | to know it this problem affects ather peoples too. What does the noise look like, is it also the top-down block of static random pixels described on the trac https://docs.openmoko.org/trac/ticket/2217 or jazzy moving pixels, or all over the screen, or in a defined invalidated area not redrawn or what? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm1MIEACgkQOjLpvpq7dModpgCfQTnW+FJ++9ru7D1dnMzvcuxi wRMAoIBXzdcdkGWNkR9FqdqaDUTYvgAR =xNc2 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD Card read/write errors and NSOD
-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 | | https://docs.openmoko.org/trac/ticket/2217 | | or jazzy moving pixels, or all over the screen, or in a defined | invalidated area not redrawn or what? | | | The screen is full of random pixels, but not uniform as in the trac | ticket snapshot. Hm that guy had an encrypted FS which was suspected as the source of the entropy, because it's actually real tough to just happen across good random-looking data coming out of nowhere. So this also makes it sound like SD Card blocks end up in the framebuffer region, in your case they'll full of more normally distributed file contents maybe. | Touching the TS sometimes update a random part of the screen with other | random pixels. | I'll try to reproduce and take a snapshot asap. Is the random part of the screen always a linear set of vertical lines? ~ Ie, never a 64 x 64 or such pixel square in its own world but always a linear block of framebuffer memory? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm1N7MACgkQOjLpvpq7dMp9+gCbBDgaAWgYUPWU5Z01x1vVzoGe DtoAn1CBJrI2mYOPfu227tF2ai5qXjy8 =wl7+ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) / adding caps for bass
-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 you are in | an experimental frame of mind and can deal with the fiddling and risk | involved. | | I understand that it won't be trivial. Maybe not for me. But if openmoko | creates a standard procedure for this improvement too, then I can have | an electronic repair shop do everything in one go - both buzz and bass | fixes. That will cost me less than having the fixes done separately, | even if both fixes together may cost a bit more than buzz only. I hope | to ship the phone only once, the repair guy will need to open it only | once... I did this rework thismorning just to see how possible it is. I wrote up the following document about it http://people.openmoko.org/andy/additional-headset-audio-caps.pdf but this isn't intended to be any official story, just something for people to try at their own risk. Don't go near it unless you're confident you can handle the rework listed in there. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmzufMACgkQOjLpvpq7dMpZpgCglANrjlScuayAoa1USU5wv8of t0sAn2LQ8qmJu4uNhnaEv8Y953qzgu1R =oq/B -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-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 / can clearance, you have to cut the can and make some kind of grommet for the leads to pass through. I dunno what happens to BT antenna effectiveness either. The way I documented you keep the leads short, the components are all in the can and the can is unchanged, but you're limited to 22uF or maybe 47uF. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm0BrEACgkQOjLpvpq7dMpKEgCffFr8lSOttUjCypf7dJJeCkN2 q5AAnig1L9yZhI/ot2gZuIbPkED4wG6D =3L+d -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-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 Mark Brown on | andy-tracking, we should keep the amp turned off more often. | | Can these be safely removed? Are they there just to make sure the | capacitors slowly drain, so you don't get a pop when plugging something in? | | Or do they have other purposes as well? The headphone action is overloaded with a digital connection to the GSM chipset. It's only used in factory though. I guess the 1Ks were added as some protection against large voltages developing on what would be floating nets on headset insertion, etc. | | Another question - is a single big capacitor enough, if it is put into | | the ground line instead of having one cap for each of the stereo | | channels? Or will that wreck stereo sound? One could then use a even | | bigger cap. | | You'd need to do both channels; the one with the unchanged cap will | sound the same as always otherwise. | | You misunderstand. I did not propose to do only one channel. | I planned on shorting both the small caps. Then, instead of one big cap | on each of the stereo lines: LEave the stereo lines connected as-is. | Break the ground line (which is common to both channels) and insert a | single big cap there instead. Slightly less work, and perhaps a bigger | capacitor will fit. (It'd probably have to be bigger too, as the two | channels often enough have the same signal.) Yes I didn't get your point. But I don't think it's the same action as one cap before each transducer and a direct common low-impedence ground reference. The two signals will mix where they join at the single capacitor and the impedence depends on the frequency. | | There is lots of easily accessible room next to the battery, above the | | SIM card. | | | | I'd love to see a good answer to those questions. Currently, it's | | unusable as an MP3 player and that's an important use for me (if | | I could use it as an MP3 player, I'd carry it with me that much more | | often, which would in turn increase my use of it). | | 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 Well, point taken. | I hope some thought goes into this for the gta03. Sound output from a | phone obviously has low power, but it should be as hi-fi as the sound | chip allows. Ideally, a balanced output that don't use (or need) caps. | One can play uncompressed wav files, and use a high-quality headset or | connect to a regular stereo system. Openmoko could have sound | enthusiast customers, as well as linux enthusiasts. We have 47uF series caps on this circuit right now on 3D7K (new name for old GTA03). - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmw74sACgkQOjLpvpq7dMrJ/QCfV0j30BJKibqrQBgSVRwge97b fB0Amwcbt4IK1rcQ0QyGmJzrhGX+nu0t =OfX+ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-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 on the bipolar transistor used | to light the AUX LED. | | This 50mA fault current then flows not through the LED (which has a | reasonable series current limit resistor), but through the GPIO IO cell | and the driver transistor base. | If this is the problem than it really is a bad design flaw... | Maybe i should test the AUX LED on my gta02v5 how much current it uses | when it is on. | | Ouch. I just tested mine, and the AUX LED really uses that much (about | 50mA). Does a SOP exist to fix this? No there's no real hardware fix that's practical. We could have done something extreme like PWM the enable by software in FIQ ISR, but it would result in dim AUX LED even so, since the LED is not seeing the excess current but just normally lit. 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. Overall, it's a small issue about small excess current on one GPIO that spends 99.9% of its life off anyway, as a customer this would bother me so much less than the buzz or bass issues it wouldn't really bother me at all. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmvlWwACgkQOjLpvpq7dMrppwCfcfKKKjYBRZtU3/OkBmteMeA8 2CcAoI0olr8DO0vo8I8n5YYPhNWr7Dxb =flcr -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-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 available in the kernel | otherwise I would mention it; if someone found one I'm also interested | to know. | | Probably this is what you're talking about: | | debian-gta02:/sys# cat /sys/class/leds/gta02-aux:red/trigger | [none] rfkill0 nand-disk rfkill1 mmc0 adapter-online usb-online | ac-online battery-charging-or-full battery-charging battery-full timer | netdev backlight Ah there we go. I guess it's pretty much every reason you would like to light an LED from kernel side, gsm rfkill is missing but I'm not sure anyone wants to burn the battery just knowing that the GSM modem is powered all the time. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmvr/EACgkQOjLpvpq7dMppHQCgj5H1Fg4xDsw6OpRdgM6V9FjM CcIAoIpW7Ip3qI55Gu0BtjEROpDDD/k9 =IQ+X -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-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 | unit. Connect them to the headset plug instead, and break the plug's | normal connection to the circuit board. This approach won't pick up any | more buzz than the headset based solution, or the current bassless | setup. And you can use any headset you want. | | The big question is - is it safe to short those small capacitors? Or | will that have other side effects, such as draining the battery or | disturbing sound on the built-in speaker? 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 Mark Brown on andy-tracking, we should keep the amp turned off more often. | Another question - is a single big capacitor enough, if it is put into | the ground line instead of having one cap for each of the stereo | channels? Or will that wreck stereo sound? One could then use a even | bigger cap. You'd need to do both channels; the one with the unchanged cap will sound the same as always otherwise. | There is lots of easily accessible room next to the battery, above the | SIM card. | | I'd love to see a good answer to those questions. Currently, it's | unusable as an MP3 player and that's an important use for me (if | I could use it as an MP3 player, I'd carry it with me that much more | often, which would in turn increase my use of it). 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 you are in an experimental frame of mind and can deal with the fiddling and risk involved. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmwESIACgkQOjLpvpq7dMrOYwCgg84IEzmPEoGSozNU+2kl7v3R edgAn2war5CTGE2912IvQ0tROeRbtUTB =qFA+ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flashing GSM firmware
-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 obviously there *is* some confusion | going on *somewhere*. I'm not quite sure when you stopped working for Openmoko / will stop working for us, but talking of confusion the openmoko.org address either doesn't or won't help. | rootfs is a standard FSO-console MS5 patched to fix doesn't boot on r/o | mounted fs issue. | Kernel is recent Andy tracking with GSM sysfs node patch created originally by | PaulFerster based on my suggestions. | MOKO11 was a corporate work involving quite a number of people on IRC, mainly | PaulFerster, Werner, Lindi (iirc), and me. Dieter checked for the bugs we | spotted and fixed them in calypso's FW. | The uSD image was entirely created, tested and published by me. | Original idea: roh. | | So all those people deserve a special thank you, and Andy deserves a special | acknowledge for sedulous mobbing as soon as joerg is mentioned somewhere. | | :( Just saying joerg's image would be totally misleading. Glad you agree. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmwPnMACgkQOjLpvpq7dMrTJQCbBje6BK0p95cGooXj2PHlw+x8 Q10Anj3BgrYSh4klNddHuYFZDEBg/qmr =XRTu -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-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!!! | No, no, no. You are right only for GTA02v6. On GTA02v5 (which I have) | this has been fixed only for orange and blue LEDs under POWER button. | Red AUX button is still power hungry - it is eating 50mA. | | Your mentioned 50mA for the AUX LED is ridiculous. It would burn out | with this high current. Normal LEDs only use ~20mA and low current LEDs | ~2mA. 50mA would be for a higher power led which isn't build into the | freerunner. | And when you are on battery the AUX led is off by default and even if it | blinks (like i modified my led behaviour) it isn't really much it uses. Johnny Tenfinger is right despite it sounds strange. On some or all A5s there is no base current limit resistor on the bipolar transistor used to light the AUX LED. This 50mA fault current then flows not through the LED (which has a reasonable series current limit resistor), but through the GPIO IO cell and the driver transistor base. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmu21kACgkQOjLpvpq7dMrRmQCfZqaeELLNiPfCWfJWz2U1cUIq 39EAoI5cfSObn7zEG5m4aaolg2zuj6k9 =kWYq -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] Suspend / Resume speed
-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. While this is not a scientific measurement, 2008.12 surely | is a lot faster. Any other ideas what they do differently? | No idea, sorry. I have never seen 2008.12. It's definitely not a problem | in the base system, since FSO ms5.1 resolves in 1 second (admittedly, | with Qi, with U-Boot it might be 2 seconds). | | My SHR resumed in about 4s. (Running from internal flash, not SDcard.) | First, nothing happens. Then the console shows itself for a little | while. finally, graphichs take over and the screen is redrawn. | | 1s would surely be an improvement. If your kernel has the printk timestamping enabled, maybe the dmesg during suspend / resume has a hint if it's something on the kernel side. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmmlxoACgkQOjLpvpq7dMptXwCdH85IfZksSKJyDQ6u5Akk4T7p 3a0AnRwU+LRs9p2d2syTWBT88wZbvibq =GWNa -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] Suspend / Resume speed
-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? It'll just be different loglevel= or console= on kernel commandline depending on which bootloader and where you're booting from. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmmBSkACgkQOjLpvpq7dMoQAwCaAj4gYunzAQGaAT4mc2R7DmfO SPYAn1o0cBKB55DyKYYrUXIBM5qdwbWc =1n1k -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko media player and direct mp3 to bluetooth headphones
-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 mp3 is like this: gst-launch filesrc | location=some mp3 file ! mp3parse ! a2dpsink device=XX:XX:XX:XX:XX:XX | ... | | I'm in the process of making a new media player (OK well - 2 formats as of | now mp3 and ogg - with maybe aac later if I can get a GPL codec) called | intone. It is essentially aimed at reducing CPU usage by using integer based | codecs (libmpg123 and tremor). I'm currently playing 44100 hz ogg files at | about 17-19% CPU usage. | Anyhow, your finding is very interesting. If you could post some more | details - the version of bluez, your audio.conf, hcid.conf etc and a step by | step method of sending data to the bluetooth headset (including headset | bonding) that would be helpful. Yes it's pretty interesting to read, especially as it pushes the dodgy codec business outside of anything to do with OM, and has power advantages. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmmBYsACgkQOjLpvpq7dMov8ACfZ9YrZghG3XIHNItuZ/aRBUJu fC8AnjYNUTMsSZawuK6jMUP+3oj/aWxJ =ilfj -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Squashfs module for newer kernels
-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 English wikipedia, only to find I cannot use it on | the moko :) I added this as a module to the default configs, but actually we don't directly control the config used for packaging kernels in a given distro. I hope people are basing it off arch/arm/configs/gta02_packaging_defconfig in which case packages built from now on will have the module. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmklS0ACgkQOjLpvpq7dMrH+gCfaxGGYfwzIrR8FfSpy9BAvteX 9WwAn1LBg56VIze16T0hoH/FDHuXQgAG =nddi -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Lack of structured information
-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 wiki | draft of 2.6.28 sysfs is a pretty good idea. For 2.6.24 kernels I started this page and it has been added to by others: http://wiki.openmoko.org/wiki/GTA02_sysfs so there's a good deal of structured information there specific to sysfs. You can find it by just searching sysfs in the Wiki. Stuff changed along with suspend - resume fixed and driver rewrites in the last couple of kernel versions. I posted a mapping for 2.6.28 here http://lists.openmoko.org/nabble.html#nabble-td1569863 Some of these are changing slightly as we go on. So we will update the sysfs wiki page with the new ones soon. But, you shouldn't take that there is no documentation about sysfs, all the important guys are on that page. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmkl5kACgkQOjLpvpq7dMrnzwCgh3NRT1QDgpMu+W0BSzQBVZYC azcAni18kPsQdv4fGEKkSmX/ZvwsvDUm =hnJR -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] Any luck with bluetooth headsets?
-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 some discussion about the voice-recording.state on the | ML. Seems like the DAI mode 1 has implementation problems. Maybe we | need to try voip-headset.state. Just a thought - haven't gotten | around to doing that yet. | | Tried that, but that one with BH-604 is simply quiet in both ends. | | I also saw the DAI discussion, but I don't understand the issue well | enough to know what to do. It feels like we are very close but not | quite there yet. 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 BT). As in literally it's not there in the chip. Maybe there's some way to meddle it through the ADC and DAC but other than that it doesn't work IIUI. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmhEuIACgkQOjLpvpq7dMr0PwCeJfApbPuG7tlUEpguxwb2ixzd PqgAoI/f+Nf1U5oZO1b1Vn0NSTXOf/Pm =Xni9 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] Any luck with bluetooth headsets?
-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 actually sure what I'm really using, but I suppose that would | be done through the CPU anyway? What could be the reason that outgoing | audio works but not incoming? No you can do it with the stuff coming from the analogue paths / GSM. What you can't do, at least, not by routing the digital sides together anyway, is like bluetooth headphones (which are being driven by digital audio bus from Wolfson) to listen to MP3 coming out of CPU on a digital audio bus to Wolfson. If you're just trying to do the phone call part through GSM headset, routing the analogue stuff hooked to the GSM chip to the digital interface for bluetooth, that has worked OK in the past. | IIUI - If I understand it? I'm too old for internet vernacular :-) Yes :-) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmhHDwACgkQOjLpvpq7dMpUWQCgh/6WmhVGsJGs/mlRhhIdS0I8 XJkAn1I3SlXbmAAAqjGz6ixg4261e5YZ =r3sY -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] Any luck with bluetooth headsets?
-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 and BT). As in literally it's not there in | the chip. | | Routing audio between SoC and Bluetooth should be possible through HCI | (that is, BT is connected via USB to SoC). The chips shipped in the | Freerunners have default eeprom setting (they call it ps keys) to route | SCO audio (i think that doesn't affect A2DP) over PCM interface. This | setting can be changed but after that one has to issue a special | command every time he wants to route the next SCO communication over | PCM. That sounds like a great workaround, although unless it exposes some digital audio device class entity it sounds like work to stitch it together into something you can pipe audio into. | Unfortunately, the BT earpiece i have here for testing works only with | laptop for now (with the same bluez), with FR i hear only ambient noice. | | Maybe there's some way to meddle it through the ADC and DAC but other | than that it doesn't work IIUI. | | Doesn't seem it can be possible on Freerunner because both DAIs are | timed fully independently. Keeping it all digital on USB would be a superior solution. You can get these EDR stereo headsets now it would be a nice feature. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmhIZkACgkQOjLpvpq7dMovZQCfTB6g8096cgSYLo8zTKWxPx4B 41MAn24sE0hte8/ZQ6Xs2pU15uNsx8Ik =HNvI -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] Any luck with bluetooth headsets?
-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 in the driver though. | | I'm going to prepare a routing diagram with alsa control names printed | over it real soon (today/tomorrow), as i'm already familiar with the | driver code, so it's just work to be done. Matt and Candy here in Taipei are making a spreadsheet about this too, which goes into the detail of which bits and what options are possible for the controls. We'll add it to the Wiki when it's done. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmiBTsACgkQOjLpvpq7dMor8gCeKtWoVhyvbCtByhlk5GAxdD1d fkUAn0laGgO6fgJx8JdAqo5qgrH+w+q2 =4iNG -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM] Less power consumption
-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 the battery does not last that long: | | 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:01:00 EET 2009 38 % | Sat Feb 21 12:01:15 EET 2009 32 % What kernel is this? I know you usually run something near HEAD? What is the status of WLAN, BT and GPS in each case? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmf6rgACgkQOjLpvpq7dMpsGACdFtplvKARavOJw3//YNsLO9a/ rQIAn0EcLxg2FTyFKhKU26b7DwXeZnBZ =L94a -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM] Less power consumption
-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 be even | better? This events/0 thing is solved for a long while in later kernel versions. On the one hand it's hard enough to solve these issues, but on the other hand the distros need to adapt to later kernels, or nothing changes for the end user no matter what we're fixing. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmgDtoACgkQOjLpvpq7dMq+ogCeJnTCtzAaZpXaR7jagg6KbMXN N4IAn1Q6ZsHaYlBSM0RSLs3+0dzir/TO =pYGz -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM] Less power consumption
-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:01:00 EET 2009 38 % | | Sat Feb 21 12:01:15 EET 2009 32 % | | What kernel is this? I know you usually run something near HEAD? | | Also please note that after each test call the phone opens a gprs | connection and sends a short status report to nagios monitoring system | which can then alert me if the phone is not responding to calls. This | GPRS connection lasts around 1-3 minutes and probably contributes to | the energy consumption. Well, your consumption is roughly double that of Mickey's... 10h is worth 16% of his battery and 30% of yours. I am sure something real is going on there but with the possibility of very different GSM environments, where it has direct access to the battery, I don't know how to come at it except to see how a GTA02 acts for me next week. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmgEZoACgkQOjLpvpq7dMr9cgCeMEV8XxWetU83ylW7MiAQ0UJX wJQAnRSYU56Y5U/NTX65N5+Klp93Q3Kt =PIqs -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qi powers off after few seconds
-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 after | battery removal. Anybody else noticed this? What's your kernel? If it's not recent, try a 2.6.29 one it may resolve it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkme2lwACgkQOjLpvpq7dMqylACfTsRJE4QhVOzgP2agWBXReg5y 7cYAnAj153a6bJoNtGW2wNLWCxw61wBD =GZcI -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: good 2.6.28 kernel for 2008.12
-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. Qpe and I don't think it's the kernel that is unstable, 2008-12 isn't prepared to work with the new sysfs paths it has may be the issue. | Enlightenment crash all the time, Duke3d doesn't work. Can anyone | suggest a 2.6.28 image that's stable enough for daily use? There's a problem with QVGA that we're working on, but that's probably the only thing down to the kernel itself. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmb3S8ACgkQOjLpvpq7dMpfkQCeKMi0t+1qAnZ3heDrg+H61Fmz pdwAn24Mo7uoTN6g/hjsmSmvdYUkr+Xt =UuHZ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Accelerometers in Kernel 2.6.28-rc4
-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 moredrivers kernel the accs are working now. But now I
have the
| following problems.
|
| When I use Qi it says it is not able to set some permissions and then
hangs in
| Angstroem login screen and I can not SSH into it. I also tried this
from the
| mailing list:
|
| Just create a textfile /boot/append-GTA02 and put whatever is needed as
| kernel parameters in there - here is mine:
| rw rootdelay=3 glamo_core.slow_memory=1
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 think if the rootfs does not remount root rw.
| When I use U-boot I have to change the boot environment because it's
bigger
| than 2 MB. I do that the following way:
| setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x3200
kernel;
| bootm 0x3200
|
| Then I would normally save the environment with saveenv but the system
boots
| immediately after the setenv command. So how can I save it?
You need to escape the ; with backslashes. Your setenv is only setting
the text as far as the first ; as it stands, then taking the nand and
bootm as new commands and running them right away.
| Then it boots sucessfully but I can not ssh into the freerunner with
message:
| ssh: connect to host 192.168.0.202 port 22: No route to host
What does
ifconfig -a
route -n
say? dmesg on the PC side?
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkmJmq4ACgkQOjLpvpq7dMr14ACfejv9eU6ErxHb9sTYZA4/vDy+
NDsAoI7zhHSKUlutgqz5xnoKUjwYQhl5
=WLi6
-END PGP SIGNATURE-
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Accelerometers in Kernel 2.6.28-rc4
-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 think if the rootfs does not remount root rw.
|
|
| the same failed to set owner root for /var/volatile/cache/
| the same failed to set mode 0755 for /var/volatile/cache/
Hum meant to be a tmpfs there. You should be able to mount on one a ro
filesystem AFAIK.
| UBOOT
|
| You need to escape the ; with backslashes. Your setenv is only setting
| the text as far as the first ; as it stands, then taking the nand and
| bootm as new commands and running them right away.
| I did the following:
| r...@x:~# chown uucp.uucp /dev/ttyACM0
| r...@x:~# cu -l /dev/ttyACM0
| GTA02v5 # setenv bootcmd setenv bootargs \${bootargs_base}
\${mtdparts}\;
| nand read.e 0x3200 kernel 0x30\; bootm 0x3200
| GTA02v5 # saveenv
| Saving Environment to NAND...
| Erasing Nand...GTA02v5 #
|
| If I now choose boot from the bootloader it boots fine,
| But after a reboot I have to do the same again it, it doesn't save it.
If you come up in NOR U-Boot it doesn't seem to impact NAND environment,
no idea why but nothing can be done about it now.
So if that's the case try whatever dance of death needed to get a
console on NAND U-Boot and do the same there.
| usb0 Link encap:Ethernet Hwaddr DA:DF:7E:17:08:9A
| UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
| RX packets:17 errors:0 dropped:0 overruns:0 frame:0
| TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
| Collisions:0 txqueuelen:1000
| RX bytes:9792 (9.7 KB) TX bytes:4140 (4.1 KB)
Well there's no IP on usb0.
ifconfig usb0 192.168.0.202 netmask 255.255.255.0 up
should help with that.
If this is with a kernel with the Ethernet gadget built as a module, I
wonder if there's a race somewhere between inserting the module and
trying to bring up the interface in initscripts.
| route -n
| Kernel-IP-routingtable
| DestGateway Genmask Flags Metric Ref
Use Iface
|
| say? dmesg on the PC side?
| [23821.176092] usb 1-1: new full speed USB device using uhci_hcd and
address
| 108
| [23821.384140] usb 1-1: configuration #1 chosen from 2 choices
| [23821.392754] usb0: register 'cdc_ether' at usb-:00:1a.0-1, CDC
Ethernet
| Device, 9e:08:34:97:d5:f8
| [23834.084104] usb0: no IPv6 routers present
It's pretty happy otherwise.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkmJtDQACgkQOjLpvpq7dMrr2QCfagr27Pwb490AIw4UZA2NfOeF
5sUAmwYm0OSNaOFi1DtSfyiMxN/aR16b
=f2cW
-END PGP SIGNATURE-
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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 and then qi was able to boot it ok afterwards. so i am not sure | what exactly happens there for the first time... | | the trouble is that i don't know how to change the ro flag for qi (i | can imagine i could place a kernel on my card and add append file with | rw and root=/dev/mtd device and of the nand flash?) Yes it can work, but you need root=/dev/mtdblock... Having rootfs mount ro initially is a safety feature, it'd be sad if we have to take it out because the rootfs can't manage doing a mount /dev/root / -oremount,rw in the initscripts. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmJdUMACgkQOjLpvpq7dMpNzACfdZ8JCjQUISC/T+lY0S0DAhIw XZoAn2rmqjlO7L+/YdkETA+2uU29ABDW =+Ae5 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Accelerometers in Kernel 2.6.28-rc4
-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 get confused | so it doesn't make trouble. | | We also changed lis302dl to use level interrupts so it's suspicious now | we see this behaviour that is so similar. | | -Andy | | Thanks, | Is somebody working on this or should I write a bug report? If yes where? | Can I use any other Kernel with FSO Milestone 5 which doesn't suffer from this | problem ? I want to update my system but I need proper working accels. Send a bug report in Trac about it. There is a quick workaround for this that can be done I believe. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIBM4ACgkQOjLpvpq7dMp/vgCfd2H3VtJb9gvcjbIgj83nDVXc POkAn2WB4y3BNCMyEO802DAzHPxBwwS0 =rAZM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Accelerometers in Kernel 2.6.28-rc4
-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'll update the moredrivers kernels at http://people.openmoko.org/andy when I checked we didn't break the threshold stuff. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIIt8ACgkQOjLpvpq7dMpzogCffYlArN6RPOfEBvWc2u0s6d2y I8YAn2KLk5NKki7CmLVeQe5evB6ordzz =0bQ1 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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 mine: | rw rootdelay=3 glamo_core.slow_memory=1 It's glamo3362.slow_memory=1 to get the conservative memory bus timings for Glamos that need it. BTW ~ I added more tuning options if you kernel has this patch http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=7f859d161097631a3c76ed1dbb1cfcb08ebe9759 so you may be able to increase the speed from this. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIb2oACgkQOjLpvpq7dMr3PgCfRWvegM8FoQtjcmXzhHtvf0we M/MAnjmYLGG5jqIDML7PcegifrmQ+QML =slV0 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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 HAVE no problems with a similar uSD (has FDOM) but only with the FSO.. /boot/uImage-GTA02.bin is a workable kernel with correct CRC? /boot/noboot-GTA02 should not be present... Needs to be ext2 or ext3 in first three partitions. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIb+AACgkQOjLpvpq7dMozFACdHT5J6iRsV0gu4PlHNb11vprp pM8AniH1LI72PJCY+J9B3y4VBIXWsHN/ =oEcj -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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 opportunity to do fsck if it likes. Did it try to start X and left some log anywhere? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIIpAACgkQOjLpvpq7dMpCmACeLbwCJSG2xKQYNCGcSFtrQIg3 7icAn1wq/8sA0GFsIzIN27ZRdo+3XwV3 =PPsb -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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 and for that i need to edit the boot environment | | ... | I had flashed u-boot back but would love to use qi again as it can start | the neo on a short pwr press, has no logo and is faster... | | | Not sure I understood what you wanted correctly, so please don't | hesitate to ask again - but if you want to use Qi to boot from NAND the | procedure is the same as from SD-Card: No this isn't so regrettably, since it would make a lot more sense than how it is. For NAND it uses the kernel in the third NAND partition same as U-Boot and mounts the sixth partition as rootfs same again as U-Boot would. We'd need a jffs2 filesystem parser and to wait for the mount action to complete to get the kernel if we did it the right way, so we do NAND for GTA02 the compatible way. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIuFsACgkQOjLpvpq7dMrFFQCfQX5OlrSZK2FRslJgyt0yXZxt EKYAn2Z+AyICuhaHUuOZJZ5U7keb1yOM =fCsi -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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 comment in the source and gave you advice when you were already right, sorry about that. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIqFQACgkQOjLpvpq7dMpkCgCfTAnQZRHfM++R7eRHAxT+dO85 8ykAniRJNkFRylNoNsryMmH8tkT10Nh2 =JIDm -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freesmartphone.org Milestone 5 'Calling All Stations' Release
-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/Noisy SOD for me. | | glamo3362.slow_memory=1 | | | Your latest compiled kernel | | uImage-moredrivers-GTA02_andy-tracking-b72d8b4c5b7173a1.bin http://people.openmoko.org/andy/uImage-moredrivers-GTA02_andy-tracking-b72d8b4c5b7173a1.bin | | isn't cutting it for me as a re-suspends immeditaely when coming out of | a suspend, so I couldn't try out this parameter. It's just due to my local .config being out of date and still enabling the Android WAKELOCKs -- the git config is actually fine already. I've updated the build in that dir to the current HEAD with the current config and confirmed suspend and resume is fine. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmIvJAACgkQOjLpvpq7dMolUQCfWHIAKtOzbEUwUUP+Cc7fu3M3 B9oAn1R7Py+X597SmhzyYBJGrNW4OhMA =4Kzf -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTE] better kernel?
-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 connecting the charger for 1-2 sec). | | Today, I tried the | uImage-moredrivers-GTA02_andy-tracking-b72d8b4c5b7173a1.bin, the battery | icon is stable, but the PM crashes when I go to the power settings. (as I | see, I cannot even change the brightness) | | So, is there any kernel that works ok with the QTE 4.4.2 ? I guess the PM GUI stuff is choking simply because it doesn't know about the new /sys paths in 2.6.28+ for this. There are several known problems in 2.6.24 branch we won't fix that are fixed in andy-tracking. So the recommended path for any distro to get best performance is to uplevel to distro to work with andy-tracking. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmHbUQACgkQOjLpvpq7dMpwWgCfdMUJMRmuBAOqm3zwMZn2OanY W7YAn2AW2RMNTt2gBTZcWpCBOV4W6+Bs =Jyut -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No Sound on calls
-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: | . | Do you mean second latest commit in openmoko git or some Debian | repository kernel? Which commit exactly? I'd like to test out 2.6.29 | but the sound problem is preventing it currently. | Alsa changed the names of mixer elements in 2.6.29 so they don't match with the state files. I found the source of the problem yesterday and Michael Trimarchi has sent a patch thismorning to re-truncate them again for now, which I'm testing. I'll update the files at that URL again assuming it solves it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmGvlkACgkQOjLpvpq7dMo+1wCdHJBS8WYdYVJHPSVG/UScLKCf 2JQAmwTSj3MGHWA/8Vg+7dqBHTsEUel4 =i4xl -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No Sound on calls
-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, 2009-02-01 at 19:27 +0200, Timo Jyrinki wrote: | | . | | Do you mean second latest commit in openmoko git or some Debian | | repository kernel? Which commit exactly? I'd like to test out 2.6.29 | | but the sound problem is preventing it currently. | | | | Alsa changed the names of mixer elements in 2.6.29 so they don't match | with the state files. I found the source of the problem yesterday and | Michael Trimarchi has sent a patch thismorning to re-truncate them again | for now, which I'm testing. | | I'll update the files at that URL again assuming it solves it. It worked fine here so it should be solved on the updated moredrivers image in there now. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmGyzcACgkQOjLpvpq7dMpuLwCeL3sde6lQL5PgdR9p5yz1BX5i gq8AnjRI/srsTAVr950g9ihHXwPQyxz2 =qYBo -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debug board v3 and neo1973 (gta01)
-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 cracked at | one edge cutting the fingers, then it tore at the neck. Then I got a | new one :-) | | Thank you Andy for your advices. | I look carefully at the cable, but see nothing. However testing it | again with the multimeter show it is defective :(. | | Where can I get a new one ? Should I buy a new debug board just for the | cable ? I think Tony (cc-d even if mailman stripped it) can help you about it, it should be possible to get you a replacement cable. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmFkekACgkQOjLpvpq7dMrFqwCeNwBrCI/rIOz0hI0tqzY2ayxX 3/sAn3FL02BInoJ2Eo7JFMT25giF46Yi =H6Xi -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner is running OpenWrt!
-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 SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmED1cACgkQOjLpvpq7dMoY/QCfbLzTNkDTVrW05ZE9juA/lVgA /PEAn1AmjshcaOYlhNL+z+nF0TxZesaz =mIzv -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debug board v3 and neo1973 (gta01)
-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 connector of | the debug board ? 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 one edge cutting the fingers, then it tore at the neck. Then I got a new one :-) The flat cable solution is pretty evil, but there doesn't seem to be much chance of improving it because it's not exactly an enduser feature and it's expensive to put the FTDI on the main board. But I curse that flat cable more than once a week myself. | What is the led7 on the debug board ? It blinks randomly when the | cable moves. And googling around, I didn't found if it is good that the | neo screen flashes and stay sometimes on until I launch openocd. LED5 lights on TX action of serial console, I guess LED7 is TX action from PC on JTAG. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmCEiIACgkQOjLpvpq7dMpdygCdEi2ZFoGQCcJVQrWVATAMAnKN rgYAnAm5Dn8HCkvd3UMIFUjytxmQDCrJ =3ysK -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debug board v3 and neo1973 (gta01)
-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 here, nothing later did. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmAV3cACgkQOjLpvpq7dMo51gCeJ1eTKzqgHxGQ/1P7Y6diZwTp EwQAn16lLMLKP5Kc9b4MbqQaKc+VRsjz =+Yg4 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.12] fr gets very hot w/ wifi, gps and wallcharger Re: Hot stuff (literally!)
-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 this, 2.6.24 or andy-tracking based one? 30 degrees C doesn't sound too volcanic, it's easily reached in ambient temperature in Taipei on a nice day. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEUEARECAAYFAkmAcKUACgkQOjLpvpq7dMpmugCfa8wsPV8SxviWVKno6iQtXqiQ ouAAl2/JicYMWW50es2/JgWZq/MsFdg= =xLbu -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.12] fr gets very hot w/ wifi, gps and wallcharger Re: Hot stuff (literally!)
-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 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 this, 2.6.24 or andy-tracking based one? | This is a stock 2008.12, with updates, so a 2.6.24 one. Well the charging LED thing is broken in 2.6.24 are fixed in any recent andy-tracking. Basically we're not doing anything with 2.6.24 these last months, all the effort has been on the -tracking branches. | 30 degrees C doesn't sound too volcanic, it's easily reached in ambient | temperature in Taipei on a nice day. | No, it's not volcanic, but it shouldn't run that warm to the touch, should it? | | Inside, it's just over 20C (I guess). Outside, it's a nice 2C at the moment :-) It's hard to guess where the power is going if you can't ssh into it. WLAN or GSM side would be reasonable guesses. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmAdX4ACgkQOjLpvpq7dMojqwCdFeNTVCaeAz8L8MeAu6MSSy5Y EcIAmwfy5pjrwgXp0iGV0Z11RgCUtDGm =Ppm5 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.12] fr gets very hot w/ wifi, gps and wallcharger Re: Hot stuff (literally!)
-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 current. | WLAN or GSM side would be reasonable guesses. | | How can I check what's going on to any reasonable detail that may | track this down for you? I can't see an easy way. WLAN can't be disconnected from power, and the device won't stay up without a battery typically. What I would suggest is update to something using the newer kernel and see if it still happens. One of the changes in the newer kernels is overhaul of the WLAN driver. In git anyway the packaging config for the kernel has WLAN stuff as modules, and when you rmmod the module it should take the device down to its lowest power state. So that should give a way to try to point the finger anyway. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmAfG0ACgkQOjLpvpq7dMreYwCfRU4M761bq2SVlpN+DenEyWti POgAoIsLsl3c5SqhCyhk5SofLS06xa4v =pRVU -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Hot stuff (literally!)
-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 the policy, then? | does wlan crank up txpower and scans constantly? Shouldn't do, but it's closed firmware, so who knows. On 2.6.24 there is some bad bug in the WLAN stack that it starts spewing debug messages for 11 hours every 22 hours or so. That's a known way it will eat more power randomly. It hasn't been observed on 2.6.28+. So if it helps people choose, it's a good idea to use a distro that is supporting current kernels. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmAgv0ACgkQOjLpvpq7dMrfEACgifz78bWULMe23jJR5YRr2CmY RYQAnjhBxKYvK48Xo+4z+VNL47/M8KT8 =pNsN -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.12] fr gets very hot w/ wifi, gps and wallcharger Re: Hot stuff (literally!)
-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 a newer kernel, does it? | | I'm not against installing Qi and a 'stable' or 'tracking' kernel, | since I don't use it for 'daily use' yet... | | So, are there any steps to take to reproduce this, and/or check if it | still happens with newer kernels? FSO's unstable repo supports it I believe. http://downloads.freesmartphone.org/fso-unstable/images/om-gta02/ - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEUEARECAAYFAkmAk2cACgkQOjLpvpq7dMovBACfYsaVsHIiGKvW+CyDm9cQ4u7q JREAmOM9A5n2q6wgxVUAETqhN3ADzRk= =XOQS -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] Kernel 2.6.28 not working on my Freerunner
-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. I'm going with my [AUX]-button to | the boot option and pressed the power-button. The screen says that the | kernel was loaded successfully and stopped at starting kernel. I | waited for more then a hour, after then I removed the battery for a hard | shutdown. | | The kernel is 2.6.28. Kernel 2.6.24 is booting nice. But I want to know | what's going wrong (kernel panic)? What kind of information do you want | to help me fix this? If there is literally a kernel panic, the AUX light will be flashing at about 4Hz. Where did you get the kernel from? Is there a git hash on the filename? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl/focACgkQOjLpvpq7dMqh+QCgiotnMUPI/wAu3BWp/1Hp54H9 45gAnAsot9n5gE0mkIONUSEhT41nCXog =23ih -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] Kernel 2.6.28 not working on 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: | gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r2-om-gta02 | on shr-testing the new kernel won't work anyway. The included version of | frameworkd is missing the necessary changes... | | For the new kernel you have to use shr-unstable right now. This will | changes with the next testing image... which will be due, when we have | sorted out one or two problems of the current unstable image. | | | phew It's not my Freerunner :-) ... just the software. I will | switch back to unstable until the new image is released. | | Keep up the good work! Glad to hear it, that particular kernel revision has been used for a while by quite a few people now with good results... I guess it started fine and then choked somewhere in the rootfs. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl/knUACgkQOjLpvpq7dMqRtwCeJL4XaRSvuO10+fxQK7HI8S6k TQUAoIijV63Aq3tcaX2/1yxJhrUEWjUb =QB7W -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Accelerometers in Kernel 2.6.28-rc4
-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 0048 - Value X1 | 0006 0002 0001 0024 - Value Y1 | 0006 0002 0002 0396 - Value Z1 | 0006 - Seperator time 2 (0.2ms higher than time1) | 0006 0002 0048 - Value X2 (the same X1 ) 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 get confused so it doesn't make trouble. We also changed lis302dl to use level interrupts so it's suspicious now we see this behaviour that is so similar. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl8XEMACgkQOjLpvpq7dMoBAwCgk58mQwThsSpQKsgdM1A8y1ok KsIAn34sAwxQsBr1fd/qSuuM4yIaqDyf =/VOZ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] 2.6.28 kernel problems
-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 which is nothing else than the name This has changed in the last week. It was taking me a great deal of time to switch between GTA02 and GTA03 kernel builds, so I changed the build script to use the O= kernel makefile parameter to keep the object files and configs for the builds in different subdirs. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=aeb4db1b913993a3e06522f13bab79decbd3cdef This reduces the time needed to switch typically to just 10 - 20 seconds or so. It requires the subdir name to be given in the first parameter as described in the changed build script. The optional dummy parameter to signal that you want a module tarball is then the second parameter now. It sounds like the combination of the Wiki and the comments and error help in the build script led to you some kind of hybrid solution, but the idea is you would have a GTA02 subdir with suitable config and build that with ./build GTA02, while having a GTA03 subdir with different config and build that with ./build GTA03. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklmOSUACgkQOjLpvpq7dMq5YACZASNu4qpntsx30j0cdxgvBoTw rYoAoILbeIC66Dyqv4u1Gzxa/kO9IOsU =e0hQ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] 2.6.28 kernel problems
-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 is there or not, so I usually use ./build GTA02 x for example. To save time, most builds I am not giving that second parameter at all. | But before i first run the build script i have to create the GTA02 | directory by hand and copy the .config into it. Else the build script | doesn't find any .config and starts the console configuration of the kernel. Right, part of the gain from this change is that the configs along with the .o files all live in their little worlds now, so nothing gets overwritten in ./GTA02 if you build ./GTA03. I realize that's not exactly being a problem for most people yet, but it was getting pretty bad here having to copy over the config and wait 10+ minutes every time I had to switch to look at something. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklmYjUACgkQOjLpvpq7dMq2vQCeOL4Qg4L2S6I/nDBnPZe371RQ dL0AnjiNLD02U7OTAAZqxU9laXQBkQC0 =IUJK -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: meeting in Braunschweig
-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 removed immediately. That's really good news. Are andy-tracking kernel packages autobuilt and made public anywhere yet? What would good advice look like for people on existing rootfs to try those packages? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklkqS4ACgkQOjLpvpq7dMqCaQCeOe3CY03oQeRq6ndVlKCAUKLx 5P8AnRyjAVYxEf/xf6UUL59dYuSIv8iI =6uQc -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Help with nand u-boot environment
-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, | and wanted to erase them all, so I used the defaultenv command in | u-boot to reset them to the beginning. The beginning I think it's not | a working environment. | Now the environment is messed and I can't boot from NAND, only from NOR, | even if I want to use internal flash and not SD. | | re-flashing the bootloader does not change the environment. I think what your missing then is dynpart or dynparts to fill in more of the environment for you, then saveenv. | Unknown command 'Boot' - try 'help' | | is there a way to avoid this? No immediate idea, sorry. This kind of thing is why there is no private environment in Qi. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkleBAsACgkQOjLpvpq7dMp4YACggNKFFQGgFYDeDNcsaTZ2cDJR kioAnRFQ9Yh5lAQMtcIvy878Ro3RdoyV =GHxZ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.12] Help with Om.2008.12 on microsd
-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 driver message. | | Happens to me also, but after that message I also have the following | messages (not sure if they change from boot to boot): | | Unknown HZ value! (87) Assume 100. | mount: special device /dev/mmcblkp01 does not exist | ALSA: restoring mixer settings... | Configuring network interfaces... /usr/sbin/alsactl: load_state:1327: No | soundcards found... | ADDRCONF(NETDEV_UP): usb0: link is not ready | done. | | I can shutdown by holding the power button. | I have FDOM in the same card and it works fine. I was just meddling with this in NAND, I believe that ro on the kernel commandline is fatal for startup of 2008.12. When I removed it from Qi, 2008.08 started up OK. So check your U-Boot env if you're using that for ro, or try adding rw to /boot/append-GTA02 if you are on SD Card and Qi. It's pretty common to boot with rootfs ro initially... - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklaL68ACgkQOjLpvpq7dMpdZwCfY23A6BvOiEu/OQx2bRnJh3A5 cJkAn2Mu/MbFjCdP9MIcdIqWAMpeHCYD =Nm0M -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Stage of GTA03 development?
-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 | some new keys in the neighbourhood as we walk around. That's quite terrifying new take on distributed attack :-O - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklLaBIACgkQOjLpvpq7dMrGIgCeMwKdw/x4W4Kv0paMLy6xjgxY lV8An2Rj64bw6ZZDF0go4G6wFz5Q4lSm =YzOI -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: read-only?!?
-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; input, bus etc.. so it's normal that | the system couldn't start. but why it is a read only file system? i | maked from my other system to the memorycard a mkfs.ext3 . ext3 isn't | read only i think? If this is on a host with uSD - full size SD adapter, these adapters have a little slider that can be used to disable writes to the SD Card, they are easy to knock. Also if your filesystem is corrupted it can decide to fail gracefully by becoming read-only. But I have managed to knock that little slider so many times I used some pliers to pinch the plastic so it can no longer move. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklLdCEACgkQOjLpvpq7dMoqgACePVUFeGo+eAI+MbO27/yC5Y9u 2akAniSjEbiot6ZDkoEWNmzAFEcO/d+B =MadW -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: read-only?!?
-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: cannot create directory 'device/bus': | Read-only file system | | this is created for every folder; input, | bus etc.. so it's normal that | the system couldn't start. but why | it is a read only file system? i | maked from my other system to | the memorycard a mkfs.ext3 . ext3 isn't | read only i think? | | If this is on a host with uSD - full size SD adapter, these | adapters have a little slider that can be used to disable writes to | the SD Card, they are easy to knock. | | Also if your filesystem is corrupted it can decide to fail | gracefully by becoming read-only. | | But I have managed to knock that little slider so many times I used | some pliers to pinch the plastic so it can no longer move. | | -Andy | it's a normal micro-sd in my moko, i didn't found a slider.. | | with my last system, it works (om 2008.9, your/andys kernel), but with | om 2008.12 it didn't.. i couldn't belive it that 2008.12 make the fs 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 be it then. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklLfvwACgkQOjLpvpq7dMo+ewCeIQTPYKebdI1zULUs4n4U0jMv ercAnit0OO7TA/9dzIizh91YpxDm8WXu =iB6t -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: New 2008.12 Release
-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 be the ro business, Qi has ro in the kernel commandline but this update apparently does not remount rw. | - Doesn't see my sdcard Hmm is the /dev/mmcblk0p1 etc there through? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklLgL8ACgkQOjLpvpq7dMrjFwCeKK5MBC+SG2TRJYepKna1but/ 7dAAnRHeReaF6Ll8yXRSHABXMxKYIj5y =vpxF -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: read-only?!?
-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 be it then. | | - -Andy | | I'm stuck with this also... | | Has a bug been logged? | Will a new kernel be released or are we stuck tweaking u-boot parms? This is not a kernel issue, it's something to fix in the rootfs, otherwise you have to solve it by changing U-Boot env. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklLrfsACgkQOjLpvpq7dMo87QCeN+CuRAd86Kha3yj4JlWj1dd1 8aoAnRJGa6Yzjod2xzSEbfgDEdwRGbxz =XoOE -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian on freerunner
-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=true QI_VERBOSE_BOOT=true ./install.sh all' ? | | on mmcblk0p2 there is / (root) and /boot | in /boot there is append-GTA02 and uImage-GTA02.bin | this files should be in /boot/boot. Is this /boot on that partition mounted on /boot on another partition then? Qi makes the assumption that the partition the kernel is coming from is the rootfs. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklMEKgACgkQOjLpvpq7dMr+7QCfeEMftyYHIQ4GDNmFUDT1W+40 olMAn0T7esfKEVByfEqBNKbn18NFsy6s =vIYX -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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. | | again after 5-10 suspend/resume cycles, i got the wsod again. does | this mean i did something wrong or that you are mistaken or that i was | unlucky enough to get bad hardware? Well, first confirm with cat /proc/version that you're running what you think you're running. Second, WSOD from resume is a bit ambiguous since it can be a more generic resume failure on 2.6.24. If you disable resume and just let it do framebuffer blanking for a while, do you ever see the WSOD just from that? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKI2AACgkQOjLpvpq7dMp+ZwCfcc08rVov6HwcjRzlUVV1eFtG iVgAmwfV4YDHAWuoNB3tXw4fOjriSbth =VPSs -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Black SOD for a change
-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 is from | Dec 8. Sounds right... | I suggest you compile the kernel as well as relevant modules | yourself. Or ask Andy to update his private directory. :) I am sitting on another update to power management stuff from Ben Dooks locally the last week until I can confirm it didn't do to GTA02 resume what the last update did. Since I am in the hellworld of trying to get GTA03 resume working it might not happen immediately. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKNn0ACgkQOjLpvpq7dMpe4wCfXr7kD/zX/Li7YtrN7JlD15F6 d64An0zGAhPIh2WwTgk4g3SufPPbJSHB =lOSU -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Black SOD for a change
-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/debugging-hell.html | Andy, i still think it'd be good if you updated the kernel in you | directory for GTA02 to the one that can actually resume (as the rev is | known, it shouldn't be that hard). People started to try andy-tracking | and not everybody can easily compile it himself. Qi update (that | includes that fancy UI ;) ) would also be good. Right... I'll try sort it later today. | BTW, do i understand it right, that the latest pm stuff from Ben | should fix BT-not-working-after-resume problem? Is it a known issue | or should i provide dmesg for the case? No it's something else to do with Balaji regulator changes, that's what the warnings are in dmesg. The solution might not be simple because the regulator stuff is now going upstream. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKPvoACgkQOjLpvpq7dMri+ACfZJFasA+c2Y/luxDi1/xIS5WH Xo4An1dJN6ZslMqxSfr++LIEFrtJWfmi =rZjq -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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 wsod. i | only get wsod after a resume. I guess it is another Glamo / suspend related misery. On andy-tracking I changed the Glamo resume to hard reset the Glamo and reload it every time. This works around a variety of WSOD caused by accidental actuation of Glamo's reset signal during suspend via a dodgy resistor divider. Later today I'll update the testing binaries in http://people.openmoko.org/andy and I think that will impact this problem for you. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKaYUACgkQOjLpvpq7dMolRwCdGnVieQx0k7qpF4xzwxVAmGNc BOkAn0rkZDGfl63vPUY3IYValwgigPv+ =Cu9d -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Black SOD for a change
-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. Subsequent | suspends/resumes don't help. Rebooting helps. After you rebooted, is it doing that bad shimmering thing each resume? I did six resumes in a row fine on my GTA02 A6 here before uploading that build. What kind of GTA02 is it? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKuEAACgkQOjLpvpq7dMqbSwCgjat1bOZBO5o+PMYtwv7yUWtw jfoAn2r/Nb+m6o/TbU3PVhdtVSB2kZyP =D7c4 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Black SOD for a change
-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 suspending and resuming once, there | | is noise on the screen, the bad TV antenna sort. Subsequent | | suspends/resumes don't help. Rebooting helps. | | After you rebooted, is it doing that bad shimmering thing each resume? | I did six resumes in a row fine on my GTA02 A6 here before uploading | that build. | | What kind of GTA02 is it? | | -Andy | 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 0x350 or 0x360 - A5 or A6. The 2.6.28 branch is running access to Glamo faster, I wonder if all the Glamos out there can take it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKzWoACgkQOjLpvpq7dMqBswCeOroW2ZzwMetFJIPZGddmFG4d EtoAnRv0aDj7yYEW4fiqcYPR63AFbgoL =pXEP -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Black SOD for a change
-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 0x350 or 0x360 - A5 or A6. | 0360. Hum. Well, I recognize the symptom well enough to do with Glamo internal DRAM not set up right I believe, but I don't have it on my A6 since many weeks when the last Glamo resume struggle was taking place and I didn't hear it from other andy-tracking testers yet either. One of the changes is we run the Glamo a bit faster, maybe it will turn out not all Glamo devices can handle it; but it just guessing right now. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklK3ngACgkQOjLpvpq7dMru5wCghjwoPAF6/rm4sAZ4Gv4UfIRh 8OYAn2HuCmT7dlP0DGRE4gESFrB4Mqu1 =/rzm -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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 from Oct 17... it has Harald's patches but not Nicolas' fixes... ancient kernel alert. Kernel from that vintage is expected to WSOD all over the place. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklK33gACgkQOjLpvpq7dMrO3gCgkpKnBjK5MxXdrKp0T/Q8veX5 i1EAoICZuvH1lgm3pSGj8nZZm/El6um6 =N8xl -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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 a...@openmoko.com wrote: | -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 from Oct 17... it has Harald's patches but not Nicolas' | fixes... ancient kernel alert. Kernel from that vintage is expected to | WSOD all over the place. | | can i change one of the opkg conf files to get a newer kernel to test with? | | after more testing i found that i can only get the wsod to clear up if | i bring the unit back from blanking quickly on the second blank. if i | wait longer than a couple minutes or so, i get the wsod again. is any | of this information useful or should i try everything again with a | newer kernel? I think it's just suffering for you at this point. I updated the http://people.openmoko.org/andy with current andy-tracking, you can give that a try. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklK6HAACgkQOjLpvpq7dMrcDACgicsUP5XJmpad3LYIOb7bDiPj gBUAn1aHOmojlmG4QDF/9wVz2QFmUHHg =bNGt -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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/resume cycles i got the wsod | again. should these images have the fix? if not, can someone point | me to a kernel/rootfs that doesn't wsod? I can't tell from the filename if they should have it or not. But, I can tell from the filename of this package that it should have it. http://downloads.openmoko.org/repository/testing/om-gta02/kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk John, maybe you can clarify the situation with the other path (and maybe change it to have a git hash). - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklJWZ0ACgkQOjLpvpq7dMp0VQCfVxId2dAzx9XxgQfd7GnapaHW h0cAn1YOwxA34xbNLDgWNnwmpBBD9mdW =vqJO -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Using qi and booting from SD-cart
-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 renamed it) Sounds good. | Then I powerdown my FR (battery out), put the battery back in and press | power hold it down and press AUX. You shouldn't need to press AUX. | 2 lines are shown s3c2410_udc: debugfs dir creation failed -19 | power_supply bat: driver faild to report 'status' properly It has booted a kernel, either the one from SD Card or fallen back to NAND one. These are kernel messages. | then the screen go's black and I have to press power and AUX again - | same lines appear again afther some time FR boots with flash image | | I folowed the wiki on Qi and Enabling console messages and Put a | rootdelay= in append-GTAXX like so: This append-GTAXX would be append-GTA02 in this case, just making sure. | But no starting up from SD. Sounds like you are actually starting up from somewhere just not getting all the way. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklJZqIACgkQOjLpvpq7dMpEjQCeOiKa3Qu5sXhNGvGYmBuJYKab QRgAnRIwpR3hryjE5Nj9HIJ1TY2nGTeh =1mPX -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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 Nicolas' patches went in to our stable kernel 12 days ago, but when the various distros update to that, or if they want to use some different kernel tree is up to them. | so, my question is: what is the easiest way to get the wsod fix. | which distro, which uimage, etc. my choice would be to use andy | tracking since that seems to be the future but i understand that most | of the distros will have some broken bits due to some changes. | | this is really the last annoyance for me in using the phone on a regular basis. The kernel packages in testing repository have the workaround: http://downloads.openmoko.org/repository/testing/om-gta02/ The ones in the unstable repo lack it (?) Anyway the ones in the unstable repo should shortly become andy-tracking based, but not, evidently, yet. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklJJ3oACgkQOjLpvpq7dMqSFgCdFzRvlrOGT1Rl2aTjFisD+DPP f94An1Dr5+UTPY4r0sPmILBVkRqXEo+q =TQhf -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-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 | the phone. Nicolas Dufresne resolved it with a couple of patches that are in our current stable and andy-tracking kernels now. So the solution is independent of the distro used. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklI3PYACgkQOjLpvpq7dMq3vACdGs+2DsC4F5nAFg4wwaiLAtPV VwsAn05XxOiVxvf7KQ2Du+d3Up1F4YVa =ZbPM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Using qi and booting from SD-cart (Andy Green)
-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 first three partitions. | | Then I powerdown my FR (battery out), put the battery back in | and press | | power hold it down and press AUX. | | You shouldn't need to press AUX | Just using power button the first line is shown very briefly and than | the black screen again. using power button 2nd time gives me the first | line and a blinking cursor without further action. Hum. | Yes it is append-GTA02! If something is wrong about the SD card partitions, it will fall back to using the NAND kernel partition (and the NAND rootfs then). In that case the /boot/append-GTA02 file won't apply since you're not using the kernel from there either. | What can I do further, where can I find new information? There's some information in the README file in git (click README here): http://git.openmoko.org/?p=qi.git;a=tree I would add loglevel=8 into /boot/append-GTA02 and see if you then get the booting log on the LCM. If you do, you know you are booting from SD and maybe there is some more info available. If not, you're likely booting from NAND. | I've been reading about git and saw a patch but I don't understand how | to use it. Where can I find info on this? If you want to build qi you need to install the toolchain, clone the repo git clone git://git.openmoko.org/git/qi.git qi then checkout origin/master git checkout origin/master and run ./build - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklJfKcACgkQOjLpvpq7dMr0ZgCbBPFOMUu9YjKPcQmQOsreXss8 +yEAoJOEricuk3gQ82D1+wmFKGV+dkvd =XDJA -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Black SOD for a change
-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 I wouldn't assume this is a kernel issue, but if you think it might be, you should try andy-tracking kernel from git or here: http://people.openmoko.org/andy and see if it changes the behaviour. The suspend and resume action is very different in these 2.6.28 kernels. There's also this opowerd thing that wants to manage resume actions including backlight. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklH0yQACgkQOjLpvpq7dMqgVwCdH0eel9le/VhaAksC6e+voBx+ lL8AoILkpurOZbcb9ImRUDKXJC1g0vwR =gxsD -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qi bootloader not working afther flash?
-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 hold down AUX when you power up, you always come into NOR U-Boot... that's still the same when you blow Qi into the NAND U-Boot partition. If you don't press AUX and power the thing up, it should try to boot by Qi. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklG7sYACgkQOjLpvpq7dMqGEwCgiTeFkk5mBlXFh2RCFri/xcqr i8MAn3JOyayK4luL5LKwwHar8nZrA2aA =7hzK -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] M4.1 issues (GPS, Suspend)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | Andy Green a...@openmoko.com 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 :/ | | This is a kernel issue I think, it should be gone in andy-tracking based | kernels with Balaji's new regulator based PMU driver in. | | It seems to me it's not. I used stable for some time and seen the | same issue. Now i switched to andy-tracking and it's just the same | (though suspends now seems to be faster). The FSO issues several | commands to the GSM modem prior to suspending, if they fail, it Yes if userspace is getting the button presses and eating them, it will give same end result. There was a bug flying around where we lose an interrupt from the PMU and after that we don't get notified about button presses: that should be gone anyway. | But you are right, it's time to try the new kernel, as FSO works ok | with it (minor modifications necessary, reported on fso trac). Great. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklDjVIACgkQOjLpvpq7dMpJSwCghmdBzV5MlALdJ77fzUB2TrJH edoAn2mpGR9fySWZF46WcZEKXjcAW/sV =P8L7 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] M4.1 issues (GPS, Suspend)
-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 in andy-tracking based kernels with Balaji's new regulator based PMU driver in. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklCguwACgkQOjLpvpq7dMo0FwCcDDds9tMfQCGvY/flb8ks4OTL me4An2qEkLRMKeF0dSi8kl5zj6HbfjOV =2VK8 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Converting a brick into a phone
-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? | | If you have to whine, do so at serious problems like the White Screen of | Death (which is now apparently solved, at least worksforme). | | There is a kernel image somewhere that doesn't go WSOD under | any circumstances? Or just some patches? | | At https://docs.openmoko.org/trac/ticket/1841 is a patch a pre-compiled | kernel for FSO M4.1 | | The daily testing images already integrate this patch (AFAIK). Both stable and andy-tracking have the no deep sleep workaround from Nicolas Dufresne and so far no customer has told they saw a WSOD from blanking or suspend since using it. Something different (hopefully easier to figure out) is busted if there is a different WSOD now on game[s] that switch screen orientation. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklA+SsACgkQOjLpvpq7dMpQYACeISV3xmboRixnCUDqr2EX7Q/7 zfoAoIAntTCpVGX06xyRzYBuQ00IBwY5 =BRP+ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM kernel newbie] Error building kernel
-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: | - - | $ ./build dummy | scripts/kconfig/conf -s arch/arm/Kconfig | | scripts/kconfig/conf -s arch/arm/Kconfig | CHK include/linux/version.h | /bin/sh: Syntax error: ( unexpected This is coming out of not having a branch initialized in git I think you'll find. Try git branch in that dir and you'll see some error in parenthesis. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk894QACgkQOjLpvpq7dMrRNQCgiF7+GSvktTuf3oYfVQe1JMOj PioAnj6jOvBPjm0WZ1KQdvUqh71/4uto =du99 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot, mounting phone
-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 can happen, how do I mount the phone, so I can edit | the phone back to default? What do you mean by mount the phone? Which filesystem are you thinking about mounting and editing? If it is one on the SD card, then the best thing to do is pop the SD Card out and meddle with it on a PC via a card reader. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk89vEACgkQOjLpvpq7dMpL3ACfZ7+JhGyx1JkQHGhuKT/iL7TE 1mMAnRWo8pu75cTx2oFjYqEUiVsjmLmE =JasM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/30 ~ 12/06)
-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, but it is evidently pretty small since two users tested it overnight (9h) at a cost of 13% battery. On andy-tracking shortly we plan to take down the regulator supplying the LCM during suspend and solve it that way, if the LCM ASIC doesn't have any more surprises. Then it should even outperform the previous way with ASIC in Deep Sleep for current savings. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk8JiAACgkQOjLpvpq7dMryxACgg62dTSnIgciVZm7jzh7FjpWs fnwAnRgysJnhIKBrW6neTPl3Sy+V/DFk =QuVy -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: microsSD doesn't mount any more!
-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 doesn't hurt anything unless you try to get U-Boot to touch anything above 4GB. | | [ 30.365000] Buffer I/O error on device mmcblk0, logical block 8 Are there some glamo-mci errors floating around before that? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk5MHYACgkQOjLpvpq7dMrj9QCfbXf7x2O6jtB0X+SfRTv/0e8k M2gAnjxeXYIDq53UrZC+mcAhm1zI02fR =jDld -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First impressions on new Android rootfs
-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 it 30 minutes or so to complete the upload. | | Sean | | | Sean, | | which uImage should we take? uImage-android or uImage-tracking? | | Good point. I've deleted uImage-tracking and made uImage-android the | matching kernel based on andy-tracking. I really hope we can capture the diff between this and andy-tracking into andy-tracking directly. It's fair enough if it contains in-progress patches I guess but we need to keep zero diff as often as possible. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3pWEACgkQOjLpvpq7dMrevgCfbCFiPonwVRqXCKcLHG/p0qDE +jQAniIoNdy6n9sja4R5GoTPPaO7yLIA =euuM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-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 (for some values of working) for a long while... what bad behaviour does not working look like for you? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3qRIACgkQOjLpvpq7dMqofwCgiF7V+PzyU8gggDNphszuwUyT 02QAoI7n1sGzzWGrCL8smhyPg9G4KU9A =9gnV -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-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 (not that important) Sean McNeil is targeting getting the Android UI for that working at any rate. | - weak signal Weak transmission or RX or both? | - connexion lasts only for a few minutes Hum. | - after connexion is lost, reconnecting nearly always involves rebooting Well, if this is due to SDIO side errors, this situation can have been improved in andy-tracking. If it's due to firmware trouble, probably this will never be fixed due to Atheros closed firmware policies. | I think I already sent the kernel messages that appear in that case | somewhere. I must confess that, as I wanted to use my Neo as a sort of | internet tablet, it now just gathers dust somewhere, waiting for a WiFi | fix. Changing the SDIO stack is enough of a jolt it's probably worth blowing the dust off and having another go according to your optimism / schedule :-) At any rate if you do this please post on kernel list about your experiences. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3wUQACgkQOjLpvpq7dMq3vACfe0uMjBCMueWANbTmtOuPTpvR VPcAn10hXLCc0XNUhX7wF5FacR4OPNRW =V0aw -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-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 there recently a release of an completely open atheros driver? | http://www.heise-online.co.uk/news/MadWifi-HAL-now-open-source--/112113 | or did that not apply to the chip used in the fr? | | There are working drivers for ath5k and ath9k, but the Neo has an | ath6k ... Yes the main difference is that the AR6001 in GTA02 is what's called a fullmac device, it means that it has an 80211 stack in the firmware of the device that can run autonomously. That's in contrast to the other devices which use a softmac 80211 stack in Linux. The advantage is that it can run autonomously somewhat even with Linux down, the disadvantage is we are entirely at the mercy of the not-really-updateable closed firmware for a very wide range of operations. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3164ACgkQOjLpvpq7dMpeMQCaAqluqq4S+c4xiveBgVVMTfvt 5AUAn2cBOrC3CGtoxYsEFU9kPZsJpUPK =VO5V -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-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 understand what's
| in it, or what the current state of the kernel is.
|
| Would someone mind elaborating a little on a few points:
|
| 1. Is this generally available? If so, where?
http://people.openmoko.org/andy has new binary versions every day or two
at the moment. These are moredriver kernels that have everything
critical built in the kernel, but there's also a matching module tarball.
If you're using U-Boot to boot it, U-Boot has a 2MByte kernel limit by
default and you need to meddle it:
setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nand
read.e 0x3200 kernel 0x30\; bootm 0x3200
saveenv
Qi (the new bootloader replacing U-Boot) doesn't have these problems.
| 2. I'm currently running Debian with the stock kernel that gets put in
| place by the install.sh script. Can I use this kernel with Debian?
| There are caveats on the Debian pages about using other kernel, so has
| anyone used this with Debian successfully?
Dunno what the caveats involve, I used Debian in runlevel 3 anyway with
random kernels.
| 3. What do I get with it? What is at risk?
|
| Thanks... I apologize if this info is out there somewhere, but I have
| spent a significant amount of time digging through past threads, and I'm
| just not getting a complete picture.
You can try it out on an SD Card for very low risk.
The main features are
~ - Suspend / Resume changes (should be way more stable)
~ - pcf50633 driver rewrite (fixes some troubles)
~ - WLAN driver now uses mainline SDIO stack (should fix some probs)
~ - Android-ready
~ - Kernel features and fixes between 2.6.24 and 2.6.28
There will be some breakage of features for a while since there are many
changes to /sys paths used by various things, but the rootfs people
should catch up soon.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkk2tW4ACgkQOjLpvpq7dMqgtACcCbAFepKRhdb50dmblBkBe1pS
AkQAn3HzTNMF2cSS9YaeGDHcJnrzC5Co
=cgkB
-END PGP SIGNATURE-
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: dualboot. u-boot now, Qi later
-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 thought of making a few smaller partitions for different kernels and a | few larger of different rootfs + one large for my personal data. | | But that will mean more than 4 partitions. Will logical partions work | just as well with Qi? Are there any special order which is better? | | Or will I have wipe all systems and start over when Qi arrives? No Qi is adapatable to existing common partition schemes on uSD. What it does is look in first three uSD partitions in turn for ext2 / 3 filesystem, if it finds one and /boot/uImage-GTA02.bin in there it will pull it in and try to boot it. If none of those worked out, on GTA02 anyway it will try to boot from NAND kernel similar to U-Boot (except Qi studies the image and pulls the correct length of NAND for any size kernel). If it sees a FAT partition it'll just skip it for consideration for booting and try the next one. On GTA03 it'll be a similar deal except it looks for /boot/uImage-GTA03.bin, it means you can isert the same uSD and filesystems on multiple kinds of device and it will pull the correct kernel for that device. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3D6wACgkQOjLpvpq7dMrWOQCdHaheLMJUVaZ9asFRAOw6q2bV FzoAnijsmj314/sWMjggPgTsLUg4G2U4 =iPdK -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-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, let it be | more public. Great, automated stress / regression testing of suspend will be a very welcome innovation (hopefully even the results will be welcome sometimes too :-) ) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk1BZYACgkQOjLpvpq7dMrDPwCeMx14nlQgRNBgr23QEsPBT0xW n8YAn3j6Ao0OEkmyTd8/Mj9D5VgYELBt =wwl3 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-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? buzz / echo / hiss... no software change can fix buzz. It's baked into the hardware and you will have to do fairly extreme meddling with your soldering iron to impact it. Echo reacts to some tweaking in alsa and maybe Calypso firmware option selection, I guess this turn up in rootfs images as best it can. Hiss and Etc I didn't hear about, but I don't think kernel or hardware world can cover for any of it on existing device. Only button to push in userspace world is optimization of echo I think we find, unless hiss is somethng like bad channel selection in alsa world. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk1ncAACgkQOjLpvpq7dMoWVgCgiF4Bsh30L8k3oEZF1Me5peit gQ4An35b4aFzPmvddxScu6pFHmSIlsRQ =GXBl -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot freeze, hang at boot time, why ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Starting kernel ... | /freeze | | Someone can tell me what's happening ? Or give me any clues to repair | that, and a place to report the bug. Best thing is figure out if it's a kernel issue or just userspace... fiddle with your U-Boot env to add console=tty0 loglevel=8 on the kernel commandline, then you should see the whole boot process fly by up to userspace starting. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky35QACgkQOjLpvpq7dMoSBACgjA3y2mpXn8HFHmQExqonu6V1 x7kAn2lAyFIdu5xBi9H3PI33t0T5lr9q =JZeN -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: Hi John - | * some obsolete kernel modules still left in system If we didn't do it already, the packaged kernels need to move to having /lib/modules path that is specific to the kernel device and build, similar to what the ./build script does: /lib/modules/2.6.28-GTA02_andy-tracking_d0aa5acc0be7c573-mokodev/ The branch and hash stops any conflict about module versions, and the device tag GTA02 allows multiple kernels to be installed on the same rootfs, so you can share the SD Card between GTA01 and GTA02 say, both times with SD Card boot to the right kernel. | * must remove 'ro' in kernel boot parameter if you use sd boot. At the moment Qi has ro boot everywhere by default, is this restriction just a temporary workaround for something? | he will work on opkg internals next. Olv moved to look into kernel | and fso. Erin will try bluetooth. Julian is working on the GTK | redraw issue, please help him out. Jeremy will fix some qtopia bugs | and keep working on suspend/resume issues. Just a thought, it can be worth Olv and Jeremy bouncing what they're planning on doing off the kernel list. For example some advice for Jeremy about suspend / resume issues would be don't waste your time doing any suspend / resume work on 2.6.24 kernel, only on andy-tracking. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky4dwACgkQOjLpvpq7dMrSTACeNaM2tQ5kn+rvzlTJC0nD5N5L s8wAnAn/GDMCXyBN8ODnY2sq5XhheRn/ =/Ytn -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-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 / resume work on | 2.6.24 kernel, only on andy-tracking. | | I'm very sorry to jump in this thread. But this advice of yours is | so much surprising! It implicitly suggests that Jeremy might be unaware of | the fact that every sane person knows for like 2 months. Do i Every sane person :-) No a lot of people are still using 2.6.24, all the distros are shipping it, it is in a branch called stable, it's not nuts if somebody tries to work on it. But there are multiple known issues with suspend / resume solved on 2.6.28 stuff and for sure unless they are solved first debugging suspend resume will be exercise in chasing one's tail. If he already knows it then fine, but people have been targeting stable in the last weeks for stuff that needs to be done on 2.6.28. | understand it right? How can it be possible at all? Everybody's so | excited about this Optimization team and you say they might | waste some time just because they don't lurk on -kernel mailing list? | | No offence meant, but that is sooo strange... I fear I've missed your point... John Lee wrote that two folks in Taiwan are going to be working specifically on kernel stuff... ''Olv moved to look into kernel and fso. ... Jeremy will fix some qtopia bugs and keep working on suspend/resume issues.'' I write to suggest they might get advantage if they coordinate kernel work on the kernel list -- at least we might not duplicate work on the same thing and there is a pretty fair amount of knowledge about Openmoko suspend / resume stuff on that list. What's sooo strange about that? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky+doACgkQOjLpvpq7dMo4GQCfSRrSFPE8WSACxUIgaXrBBzn6 C8wAn3nEoVN9VPjEMd9zQ2mukdo2D666 =1qaJ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-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 The fact is I don't know what Olv and Jeremy are planning on doing in the kernel because it hasn't appeared on the kernel list or anywhere else for me. But that's all... I have no problem with their experience level and will be interested to see what they're coming up with, and if I can help. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkzCCgACgkQOjLpvpq7dMpopQCeNgUq6HhK1UOpUG44b9ltDZkm OesAnihKj1eUuuJCCfozUU2kqDFJDxk5 =kUyy -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OT]Software patents end? ??:) light at the end of tunnel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | FLAC *is* compressed, but it's lossless compression, meaning that there | is no change to the sound when you encode it to FLAC, Whereas when you | encode to MP3 or ogg, you're losing audio information. | | I'd like to point out also that the CD source is already lossy in that | it is a digital representation of analog signals. Recording companies, | however, compensate for this and work to make the sound output from a CD | player as ideal as possible, About FLAC it's actually really interesting. They do a lossy compression action like most other codecs, but they then decode it and compute an additional error channel, the difference between what the lossy decoder gives and the original it still has access to at encode time. The error channel is compressed in the gzip type sense and added into the FLAC file along with the lossy encode. The end user FLAC decoder does the lossy decompression and then adds on the error channel to give a lossless result in the end. (Sorry Arne... but it's kind of on-topic you know with the Android image getting recooked for this). - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkv0s8ACgkQOjLpvpq7dMqLigCeLIEmWJieYNQk6nAGyJawaZSj W50Ani6oPQ0GRWNDkMrHxNjADBvipEjC =7g1J -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OT]Software patents end? ??:) light at the end of tunnel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | but it's kind of on-topic you know with the Android image | getting recooked for this). | | now i am confused. | care to elaborate? http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006894.html - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkv1K8ACgkQOjLpvpq7dMrmPQCfdxdU3PzJUA6ZTa2UqmTuuaGi daQAn025CJT5rJWxTO1nUQWiQRTllZgL =ovml -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: microSD issue again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi All | Who have same problem ? | Transcend 2Gb microSD | glamo-mci glamo-mci.0: Error after cmd: 0x8020 | mmcblk0: error -110 sending read/write command | end_request: I/O error, dev mmcblk0, sector 3919855 It's kind of suspicious that this is at byte +2006965760 into the 2GByte SD Card... it's right at (or beyond) the end... - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkwLKAACgkQOjLpvpq7dMqlIQCfQrSOam6/E25wmHFD65s+MrUa fF8AniN7rsgwgiGa1F7IIWc2hMENajUO =kfiU -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel log?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | I got a segmentation fault message when executing luvcview on the | FreeRunner. What should I do to check the kernel log to see if the | driver crashed? It seems that the dmesg command is not helpful. Userspace stuff can segfault fine without kernel help, is there anything at all mentioned in dmesg? Try run the app under gdb to debug where the segfault happens. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkktZaMACgkQOjLpvpq7dMpc2ACgkuTCaoWWIxeenNCIy5c5oJGJ XzwAn0e54Gq2AZNq0q8bg5Rp+9zs0OhA =1GPX -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
