Currently the home page of http://projects.openmoko.org/ is full of
cheery messages on how one can get involved.
It would only be fair for somebody to please put a pointer to this
discussion there.
___
devel mailing list
devel@lists.openmoko.org
https:/
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello!
| This question is mostly for Andy, but since it might be useful for
| other users I decided to post it on ML too.
|
| So, what exactly is different in system paths in rootfs between old
| kernel and
Hello!
This question is mostly for Andy, but since it might be useful for
other users I decided to post it on ML too.
So, what exactly is different in system paths in rootfs between old
kernel and new 2.6.28?
Where can I read about it and how do I change them?
In other words - how to make my root
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
They code that calls this is in the function "requestEnterSimPin" in
hardware/ril/reference-ril/reference-ril.c:
if ( datalen == sizeof(char*) ) {
asprintf(&cmd, "AT+CPIN=%s", strings[0]);
} else if ( datalen == 2*sizeof(char*) ) {
asprintf(&cmd, "AT+CPIN=%s,%s", strin
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
Hi,
i downloaded images from
http://people.debian.org/~aurel32/qemu/armel/ and all works well now so
don't worry about this anymore for me... but for the future it might
be interesting to know what's actually up...
Petr
On Tue, 16 Dec 2008
18:04:10 +0100 Petr Vanek (PV) wrote:
>Hi,
>
>i am h
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
Hi,
i am having troubles creating debian image with qemubuilder. I have
followed the instructions [1] but no luck - [0.00] Kernel panic
- not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Could you please point me to the right direction?
Thank you
Petr
[1] http://wiki.debi
#2085: Combining SIM telephone numers in single contact and improved import and
export
-+--
Reporter: pander | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |
#2085: Combining SIM telephone numers in single contact and improved import and
export
-+--
Reporter: pander | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: reopened
Priority: high |Milestone:
#1158: Charging stops even while connected
-+--
Reporter: p...@… |Owner: openmoko-devel
Type: defect| Status: closed
Priority: high |Milestone:
#2085: Combining SIM telephone numers in single contact and improved import and
export
-+--
Reporter: pander | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |
Hi Alex,
Problem is that the CPIN request needs to look like this:
AT+CPIN="4223"
not
AT+CPIN=4223
Your RIL sends without the quotes around the PIN code.
Best regards,
Mikkel
-Original Message-
From: devel-boun...@lists.openmoko.org
[mailto:devel-boun...@lists.openmoko.org] On Behal
#2085: Combining SIM telephone numers in single contact and improved import and
export
-+--
Reporter: pander | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |
#2085: Combining SIM telephone numers in single contact and improved import and
export
-+--
Reporter: pander | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |
On 12/16/08 Rod Whitby wrote:
> > It's unfair to say that we won't pay for somebody to maintain this.
> > > Money is not the issue. We've said this numerous times. It's
> opportunity
> > > cost. We've never been able to get projects* running well. It's
> super
> > > painful for me each time I
On Mon, Dec 15, 2008 at 11:36:34AM +0100, Minh Ha Duong wrote:
> Dear Openmoko officers,
>
> This is an open letter to share with you my hopes that 2008 testing will be
> someday released as a minor update to 2008.9. I am not feeling comfortable
> with the present situation as an ending to th
Sean Moss-Pultz wrote:
> On 12/16/08 Rod Whitby wrote:
>> The closure of projects.openmoko.org is (IMHO) a step in the wrong
>> direction, since it further fragments the openmoko developer resources
>> and community.
>>
>> This action says "Openmoko does not value the contributions of the
>> commun
On Tuesday 16 December 2008 17:11:01 Harald Welte wrote:
> So maybe the community could decide if they would want to run and maintain
> projects.openmoko.org? Would that be a working compromise? Since Openmoko
> is always about the community, why not let them decide? I'm sure if there
> are enou
On 12/16/08 Rod Whitby wrote:
> The closure of projects.openmoko.org is (IMHO) a step in the wrong
> direction, since it further fragments the openmoko developer resources
> and community.
>
> This action says "Openmoko does not value the contributions of the
> community developers who use projec
Hi Graeme,
On Mon, Dec 15, 2008 at 05:02:36PM +, Graeme Gregory wrote:
> I spent some time investigating Kernel Mode Switching. I definitely
> think this is the direction glamo driver should go in the future and
> ties in with any possible OpenGL/ES work. But at the moment seems to be
> spre
Hi Marek,
On Tue, Dec 16, 2008 at 12:03:24PM +0800, Marek Lindner wrote:
> as discussed some weeks back Openmoko wants to reduce the time spent on other
> things next to the phone. Part of that process is the shutdown of our
> projects.openmoko.org server. In the past we spent considerable tim
mmh,
I am involved in the community infrastructure at www.ops4j.org. We
have 3 paid servers hosted in Germany and are currently upgrading our
infrastructure (the mai wiki is not online right now, sorry). We are
running the whole Atlassian Suite (Jira, Confluence, Bamboo, Crowd,
Crucible) backed by
Marek Lindner wrote:
> as discussed some weeks back Openmoko wants to reduce the time spent on other
> things next to the phone. Part of that process is the shutdown of our
> projects.openmoko.org server. In the past we spent considerable time and
> effort
> maintaining it. As many people notic
On Tuesday 16 December 2008 16:47:19 David Reyes Samblas Martinez wrote:
> At least, openmoko instead "go find yourself a new home", better
> provide a devel manual,howto,faq or any kind of document where specify
> recommended sites which provides the same or equivalent facilities and
> tools they
On Tuesday 16 December 2008 13:04:44 Yaroslav Halchenko wrote:
> sounds again like a broken promise to me, sorry, and imho is not nice
> -- is really a lot of effort put by OM to maintain that poor website???
>
> May be it is worth finding a person in the community who would not mind
> taking a bu
:( It's not good news,
so what will happen with the mailing lists already in
projects.openmoko.org? I got two of them pretty active (fdom-devel and
openmoko-spain)
I'm agree openmoko core developers focus their effort in the inners of
the phone and let the community deal with the rest but I'm sorr
cool! I will be glad to test when you have something ready.
--
Jayesh
On Mon, Dec 15, 2008 at 9:02 AM, Graeme Gregory wrote:
> Hi, small update just to let you guys know what I am doing.
>
> I spent some time investigating Kernel Mode Switching. I definitely
> think this is the direction glamo
46 matches
Mail list logo
