On Wednesday 04 February 2009 09:04:57 Rod Whitby wrote:
> I have not had official word from Openmoko that they have moved from
> git.openmoko.org to git.openembedded.org
>
> If Openmoko has officially moved, then please just tell me the new git
> server and branch, and I can update MokoMakefile im
Joel,
Joel Newkirk wrote:
> On Wed, 04 Feb 2009 14:28:57 +1100, Philip Rhoades
> wrote:
>> People,
>>
>> I installed:
>>
>> openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.jffs2
>>
> uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin
>> and:
>>
>> Calculator -
On Wed, 04 Feb 2009 14:28:57 +1100, Philip Rhoades
wrote:
> People,
>
> I installed:
>
> openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.jffs2
>
uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin
>
> and:
>
> Calculator - works
> Elementary Te* - works
> File
People,
I installed:
openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.jffs2
uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin
and:
Calculator - works
Elementary Te* - works
File Manager - works
GPS &* - works
Htop - doesn't start
I/O - stopped running unexpect
Angus Ainslie wrote:
> Hi Rod,
>
> On Wed, 2009-02-04 at 12:36 +1030, Rod Whitby wrote:
>>> Must development is now occurring in OE upstream. AFAIK the
>>> org.openmoko.* branches are now all legacy and not developed any more.
>> Graeme,
>>
>> Is this official? Who is the official Openmoko distri
Hi Rod,
On Wed, 2009-02-04 at 12:36 +1030, Rod Whitby wrote:
> > Must development is now occurring in OE upstream. AFAIK the
> > org.openmoko.* branches are now all legacy and not developed any more.
>
> Graeme,
>
> Is this official? Who is the official Openmoko distribution manager
> today? I
> Must development is now occurring in OE upstream. AFAIK the
> org.openmoko.* branches are now all legacy and not developed any more.
Graeme,
Is this official? Who is the official Openmoko distribution manager
today? Is that you?
Where was the official announcement to developers of the move f
On Tue, 3 Feb 2009 19:41:32 -0200, Werner Almesberger
wrote:
> Joel Newkirk wrote:
>> Exactly what I was looking for, thanks! :) Now if only the host would
>> recognize it as the same device every time. (particularly windows -
> linux
>> tends to just work despite treating it as new each time, wh
On Wed, 04 Feb 2009 11:41:40 +1030 Rod Whitby said:
> Thomas has one opinion about MokoMakefile. It is not the only opinion
> held by various Openmoko and third-party developers.
>
> It is true that the delta between the normal OE build process, and the
> Openmoko build process is progressively
Thomas has one opinion about MokoMakefile. It is not the only opinion
held by various Openmoko and third-party developers.
It is true that the delta between the normal OE build process, and the
Openmoko build process is progressively getting smaller.
However, there are many people who find the n
Juan Alberto Aranda Alvarez wrote:
> The toolchain is a good idea to show newcomers the phone and get them
> excited with it. But it isn't maintained either, so you have a lot of
> new comers wanting to port their application and would only get
> disappointed.
Ironically, quite a lot of small and
[Subject changed to reflect the actual conversation]
Juan Alberto Aranda Alvarez wrote:
> Harald Welte wrote:
>
>> So if somebody decides that git.openmoko.org is no longer used but instead
>> upstream OE, then whoever makes that decision: Please update the wiki to
>> reflect that change.
>
> So
Thomas Gstädtner wrote:
> On Wed, Feb 4, 2009 at 12:57 AM, Juan Alberto Aranda Alvarez
> wrote:
>> So basically MokoMakefile is broken?
>
> It not only is broken, it also is unmaintained. I suggest you to use
> plain Openembedded, makes everything much easier.
What makes you think MokoMakefile i
Then, it should be wiped out completely from the wiki. I guess it was
created as a way to "protect" new developers. But it totally confused me.
The toolchain is a good idea to show newcomers the phone and get them
excited with it. But it isn't maintained either, so you have a lot of
new comers wan
On Wed, Feb 4, 2009 at 12:57 AM, Juan Alberto Aranda Alvarez
wrote:
> So basically MokoMakefile is broken?
It not only is broken, it also is unmaintained. I suggest you to use
plain Openembedded, makes everything much easier.
___
devel mailing list
dev
So basically MokoMakefile is broken?
Juan
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
Harald Welte wrote:
> So if somebody decides that git.openmoko.org is no longer used but instead
> upstream OE, then whoever makes that decision: Please update the wiki to
> reflect that change.
So upstream OE is the one to use?
Juan
___
devel mailing
Joel Newkirk wrote:
> Exactly what I was looking for, thanks! :) Now if only the host would
> recognize it as the same device every time. (particularly windows - linux
> tends to just work despite treating it as new each time, while windows
> wants to download drivers)
Could the Windows-side prob
On Tue, 3 Feb 2009 11:05:54 +, Robert Piasek
wrote:
> On Tuesday 03 February 2009 00:11:05 Mike (mwester) wrote:
>> The
>> point, of course, being to make the network manager on the host side of
>> the USB connection happier...
>
> Well this can easily be sorted in userspace. I for one build
On Tue, 2009-02-03 at 15:10 -0500, Christopher Friedt wrote:
> Hi Harald,
>
> I don't mind updating the wiki where I see errors at all - as long as
> I'm not stepping on someone else's feet by doing so.
>
Please go ahead and update the pages they are suffering from bit
rot
> A couple of spots
Hi Harald,
I don't mind updating the wiki where I see errors at all - as long as
I'm not stepping on someone else's feet by doing so.
A couple of spots that I feel need some updating are:
1) http://wiki.openmoko.org/wiki/OpenEmbedded
==> This page needs a bit of an overhaul, IMHO, and as this i
Andy Green wrote:
> Not so. I tested DFU behaviour some time ago about that and it just
> erases up to what it writes, not the whole partition. So it's fine.
Okay, so "user kernel" goes first and "boot GUI" (we need a name
for it) starts at offset 4MB (plus any bad blocks in the first 4 MB ?),
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> GTA02 NOR U-Boot will then be incompatible with what we changed to.
|
| Yup, except for the first partition. By the way, since we may
| subdivide the kernel partition, we'll probably end
Hi,
"
Just in time with FSO’s Milestone 5 we are releasing our first tutorial.
It outlines how to create a simple app, write a simple service and do
some basic interaction with edje."
read more at:
http://www.paroli-project.org/2009/02/03/paroli-says-hello-world/
/mirko
__
To Everyone:
On Sat, Jan 31, 2009 at 01:17:16PM -0500, Christopher Friedt wrote:
> Originally I was following the Developer's Guide on the OpenMoko
> Wiki... it seems to be a bit outdated because it still suggests to
> synchronize with git.openmoko.org.
It's a real PITA to see that the wiki bas
Andy Green wrote:
> GTA02 NOR U-Boot will then be incompatible with what we changed to.
Yup, except for the first partition. By the way, since we may
subdivide the kernel partition, we'll probably end up being
incompatible with what's probably the most common use of DFU
anyway. So I'd just recomme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> This opens a can of worms for Qi in terms of supporting GTA02 in the
|> field already with random dynparts to give access to the magic ext2
|> partition in NAND.
|
| One more reason to r
I wrote:
> - going dynamic -> static again:
>
> - previously deleted files in the NAND rootfs may come back from
> the dead (< 74*p)
Ah, plus everything from "going dynamic -> static for the first time"
as well.
- Werner
___
devel mailing list
d
Andy Green wrote:
> This opens a can of worms for Qi in terms of supporting GTA02 in the
> field already with random dynparts to give access to the magic ext2
> partition in NAND.
One more reason to repartition when switching to Qi ;-)
The factory partition is just another item that isn't right i
On Tuesday 03 February 2009 00:11:05 Mike (mwester) wrote:
> The
> point, of course, being to make the network manager on the host side of
> the USB connection happier...
Well this can easily be sorted in userspace. I for one build g_ether as module
and append host_addr=XX:XX:XX:XX:XX to modules.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Cool. Combining this with the initramfs/kexec stuff that's been
| discussed on the kernel list (cc'd here): the kexec kernel could very
| easily do the magic to read that address as you've described here,
31 matches
Mail list logo
