Hello Al,
> Is this something that a volunteer who's signed the NDA would be able to look
> into? If we're lucky here might be something in the small bit of GSM source
> OM do have access to.
>
The actual task of modifying the audio stream is done inside the DSP.
You will
find in the source
On Wednesday 07 January 2009 20:03:34 Openmoko Public Trac wrote:
> #2206: Can't mount GadgetFS on OM.
>- I've got problems starting GadgetFS on the OpenMoko (the actual phone) and
> I think it could be a problem in the kernel or the GadgetFS source.
>
> GadgetFS and g_ether are compiled as modul
On Wednesday 07 January 2009, Dieter Spaar wrote:
> Hello Pavel,
>
> > As far as i can see for most people %N commands are absolutely
> > necessary to get a loud and clear sound (especially on remote side)
> > without echo during voice conversation.
> >
> > We now know all the possible values b
ot;arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO= "openmoko"
DISTRO_VERSION= "-20090107"
TARGET_FPU= "soft"
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing
Hello Dieter,
Dieter Spaar writes:
>> I hope you're the one who can say exactly when it's best to issue
>> those commands to ensure an acceptable sound quality :)
>>
> I am sorry to say that I cannot answer this, simply because
> I don't know it without spending probably quite some time
> on try
Hello Pavel,
> As far as i can see for most people %N commands are absolutely
> necessary to get a loud and clear sound (especially on remote side)
> without echo during voice conversation.
>
> We now know all the possible values but some people got mixed results
> with these settings because
Hello,
Just a question to the people experiencing bug #1024: Anyone with a GTA01
who can reproduce #1024 ? "Deep Sleep", which seem to be necessary for
#1024 to appear, was introduced with "Moko3", so it would be interesting
to know if a GTA01 with "Moko3" or newer also shows #1024.
Thanks and be
#2206: Can't mount GadgetFS on OM.
-+--
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component:
#2205: Use shorter name in launcher of gpe-scap and map Print Screen for
external
keyboard
-+--
Reporter: pander | Owner: openmoko-devel
Type: enhancement | Status: new
Priority:
On Wed, 2009-01-07 at 13:07 +, Andy Green wrote:
> 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 .
Shakthi Kannan wrote:
> I am trying to connect the debug board v3 with FreeRunner to a Debian
> system (running 2.6.26-1-686), and I am getting the following errors:
The FPC connection can be very deceptive. I don't know how many days
(those minutes add up ...) I've already spent trying to figure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| --- On Wed, Jan 7, 2009 at 7:06 PM, Andy Green wrote:
| | jtag_speed 0
| |
| | Try increasing this, despite "speed" it actually means "delay".
| |
| | Also, only certain magic libftdi versions work,
Hi,
--- On Wed, Jan 7, 2009 at 7:06 PM, Andy Green wrote:
| jtag_speed 0
|
| Try increasing this, despite "speed" it actually means "delay".
|
| Also, only certain magic libftdi versions work, IIRC 0.8 is good.
\--
I tried 4, 8, 20 for jtag_speed, but, I still get the JTAG
communication failure
On Wednesday 07 January 2009 14:46:34 Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wednesday 07 January 2009 14:27:57 Andy Green wrote:
> |> | It's not the firmware. It started after I switched to 2.6.28 and the
> |>
> |> newer
> |>
> |> | frameworkd.
> |>
> |> Fair enough,
On Wednesday 07 January 2009 14:45:06 Werner Almesberger wrote:
> Sander van Grieken wrote:
> > Not an option really. It would only drain the battery more I think?
>
> Hence the --wlan disable.
>
> > It's also a fix for a symptom, not the root cause.
>
> You can't have your cake and eat it ;-) Eith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wednesday 07 January 2009 14:27:57 Andy Green wrote:
|> | It's not the firmware. It started after I switched to 2.6.28 and the
|> newer
|> | frameworkd.
|>
|> Fair enough, maybe Werner's module param can
Sander van Grieken wrote:
> Not an option really. It would only drain the battery more I think?
Hence the --wlan disable.
> It's also a fix for a symptom, not the root cause.
You can't have your cake and eat it ;-) Either you tell the kernel
to leave things in place or you have to provide some u
On Wednesday 07 January 2009 14:27:57 Andy Green wrote:
> | It's not the firmware. It started after I switched to 2.6.28 and the
> newer
> | frameworkd.
>
> Fair enough, maybe Werner's module param can help.
Not an option really. It would only drain the battery more I think?
It's also a fix for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| jtag_speed 0
Try increasing this, despite "speed" it actually means "delay".
Also, only certain magic libftdi versions work, IIRC 0.8 is good.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.
Hi,
I am trying to connect the debug board v3 with FreeRunner to a Debian
system (running 2.6.26-1-686), and I am getting the following errors:
=== ERROR ===
$ sudo openocd -f openocd.cfg
Open On-Chip Debugger 1.0 (2008-08-11-18:16) svn:unknown
$URL: http://svn.berlios.de/svnroot/repos/openocd/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hmm.. not sure if I agree here. IMO resume should reinstate the
situation as
| it was at suspend. NM or any userspace process could then decide what
to do if
| it notices the AP has disappeared.
It's not n
On Wednesday 07 January 2009 14:11:41 Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wednesday 07 January 2009 13:44:36 Andy Green wrote:
> |> Somebody in the thread at some point said:
> |> |> Thanks for the report about it, what does enabled or disabled mean
> |> |> for Wif
Sander van Grieken wrote:
> - wifi seems to be toggled by each suspend/resume cycle. After boot wifi is
> enabled (even though the interface is not marked 'auto' in
> /etc/network/interfaces). After the first suspend cycle it's disabled, the
> next cycle it's enabled again, etc.
The S3C MMC dri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wednesday 07 January 2009 13:44:36 Andy Green wrote:
|> Somebody in the thread at some point said:
|> |> Thanks for the report about it, what does enabled or disabled mean for
|> |> Wifi? Say if it is in
-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
On Wednesday 07 January 2009 13:44:36 Andy Green wrote:
> Somebody in the thread at some point said:
> |> Thanks for the report about it, what does enabled or disabled mean for
> |> Wifi? Say if it is in "disabled" situation, what does that look like?
> |
> | eth0 is up but lost its IP, wireless i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Thanks for the report about it, what does enabled or disabled mean for
|> Wifi? Say if it is in "disabled" situation, what does that look like?
|
| eth0 is up but lost its IP, wireless is not associated.
On Wednesday 07 January 2009 13:10:14 Sander van Grieken wrote:
> On Wednesday 07 January 2009 12:51:33 Andy Green wrote:
> > Somebody in the thread at some point said:
> > | In the end I only had to change bitbake's conf/local.conf and include
> >
> > these
> >
> > | lines to move over to 2.6.28 +
On Wednesday 07 January 2009 12:51:33 Andy Green wrote:
> Somebody in the thread at some point said:
> | In the end I only had to change bitbake's conf/local.conf and include
>
> these
>
> | lines to move over to 2.6.28 + comaptible frameworkd:
> |
> | PREFERRED_PROVIDER_virtual/kernel = "linux-ope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| In the end I only had to change bitbake's conf/local.conf and include
these
| lines to move over to 2.6.28 + comaptible frameworkd:
|
| PREFERRED_PROVIDER_virtual/kernel = "linux-openmoko-devel"
| PREFERRED
On Tuesday 06 January 2009 11:31:42 Gergely Imreh wrote:
> 2009/1/6 Sander van Grieken :
> >> I was checking out how to compile my own kernel (uImage) for my
> >> GTA02, but run into a few problem while following the wiki - which now
> >> seems seriously out of date. In the end I managed to compi
Hi,
yesterday, we (Mickey, Daniel, Jan, Stefan, Ray and me) sat together in
Braunschweig to discuss the next steps regarding the builds / images / feeds /
2.6.28 / etc.
Here is the summary of the outcome:
=> latest / experimental package feed
* This feed contains the latest version (autorev)
32 matches
Mail list logo
