Mer v0.6 released - Page 3 - maemo.org

Active Topics

Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 4 days, 6 hrs ago
more...

Page 3 of 8

< Prev

Next >

Last »

Thread Tools

	GeneralAntilles	2009-01-20 , 11:57
	Posts: 5,478 \| Thanked: 5,222 times \| Joined on Jan 2006 @ St. Petersburg, FL	#21

Originally Posted by fanoush

(except irc)

Sorry, fanoush, IRC.

__________________
Ryan Abel

Quote & Reply |

	Stskeeps	2009-01-20 , 12:25
	Posts: 1,671 \| Thanked: 11,478 times \| Joined on Jun 2008 @ Warsaw, Poland	#22

Originally Posted by fanoush

cool, do you guys have some mailing list or forum or something (except irc) where you discuss these things and real work gets planned and done? Mer looks cool but I am having problem even with watching you.

Glad to see you're interested!

The current collaborative spaces are:

* http://wiki.maemo.org/Mer_Blueprint (formal planning) - if you have a task you think should be done to accomplish the goal of the sprint, add it, or commit to a task if you'd like to take that. RSS here

If there's discussions needed regarding a task, we'll discuss on mer-development@garage.maemo.org (mailing list in progress of being set up, at http://garage.maemo.org/mailman/list...er-development)

Or, on associated Talk/Task pages like https://wiki.maemo.org/Task:Mer_Repository_Setup. It's the hope that people will add their activities to the activity log (there has been talk of having RSS feed of microblogging included into the wiki).

* https://code.launchpad.net/m-r/ (bazaar branches, we hope to merge this into Garage once some blockers goes through)

* http://jaiku.com/channel/merbuilder (log of builder so you can see what goes into repository

, RSS here

* http://bugs.maemo.org - The Mer product on bugs.maemo.org

* IRC, on #maemo (random discussion and getting to know eachother) - idling there and just participating once in a while when you see an interesting conversation is also perfectly fine, it's not a requirement to be in here to be part of the project

- a scrollback is often useful just to glance through once in a while.

__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.

Quote & Reply |

The Following 6 Users Say Thank You to Stskeeps For This Useful Post:
Bundyo, danramos, fanoush, meizirkki, sachin007, VDVsx

fanoush	2009-01-20 , 12:28
Posts: 2,152 \| Thanked: 1,490 times \| Joined on Jan 2006 @ Czech Republic	#23

Originally Posted by GeneralAntilles

Sorry, fanoush, IRC.

Good for quick talk but then it gets lost. List and forums are there for reason, namely to keep archive in some structured form related to discussed topic :-) I don't believe you don't need this.

__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.

Quote & Reply |

	GeneralAntilles	2009-01-20 , 12:38
	Posts: 5,478 \| Thanked: 5,222 times \| Joined on Jan 2006 @ St. Petersburg, FL	#24

Originally Posted by fanoush

Good for quick talk but then it gets lost. List and forums are there for reason, namely to keep archive in some structured form related to discussed topic :-)

The same argument dneary makes against it, but Mer and many other important Maemo projects wouldn't exist if it weren't for IRC.

__________________
Ryan Abel

Quote & Reply |

fanoush	2009-01-20 , 12:58
Posts: 2,152 \| Thanked: 1,490 times \| Joined on Jan 2006 @ Czech Republic	#25

Originally Posted by GeneralAntilles

The same argument dneary makes against it, but Mer and many other important Maemo projects wouldn't exist if it weren't for IRC.

I don't want to ban IRC and I'm not saying it is useless. It is just not enough if you need some history and also if you need to discuss something with large enough group so most of them are not online at the same time. At least #maemo-mer would help with keeping the archive relatively clean if people prefer IRC.

Quote & Reply |

	Stskeeps	2009-01-20 , 13:10
	Posts: 1,671 \| Thanked: 11,478 times \| Joined on Jun 2008 @ Warsaw, Poland	#26

Originally Posted by fanoush

It is just not enough if you need some history and also if you need to discuss something with large enough group so most of them are not online at the same time. At least #maemo-mer would help with keeping the archive relatively clean if people prefer IRC.

We tried for a while to do microblogging as to fight this problem, maybe it should be considered again. We do also have #mer which is more silent.

Quote & Reply |

	Stskeeps	2009-01-20 , 13:46
	Posts: 1,671 \| Thanked: 11,478 times \| Joined on Jun 2008 @ Warsaw, Poland	#27

Mirage on python-hildon, python-gtk2, python-osso

Quote & Reply |

The Following 2 Users Say Thank You to Stskeeps For This Useful Post:
fredoll, VDVsx

	daperl	2009-01-20 , 19:12
	Posts: 2,427 \| Thanked: 2,986 times \| Joined on Dec 2007	#28

Originally Posted by fanoush

I was trying kexec sometime ago with chinook kernel when OS2008 came but did not get very far. The kernel part was maybe OK (there were some patches needed for preserving boot time kernel tags) but I failed to load kernel from userspace, it just segfaulted.

Just so I'm clear. Did kexec -l segfault? Or did kexec -l not segfault, but the subsequent kexec -e segfaulted? Thanks.

__________________
N9: Go white or go home

Quote & Reply |

fanoush	2009-01-20 , 22:37
Posts: 2,152 \| Thanked: 1,490 times \| Joined on Jan 2006 @ Czech Republic	#29

Originally Posted by daperl

Just so I'm clear. Did kexec -l segfault? Or did kexec -l not segfault, but the subsequent kexec -e segfaulted? Thanks.

I think it was already -l but don't remember for sure. I used two patches for kernel 2.6.22, one adding atags support and second one exporting it in two files in /proc/atags directory. Then I used kexec-tools 1.101 maybe with some additional patches.

Now I have tried it with userspace kexec-nit tool from http://guug.org/nit/kexec/ and found it expects /proc/atags to be a file which is how it is done in recent kernels. I combined previous patches with https://dev.openwrt.org/browser/trun...atch?rev=13613 and now the userspace tool compiled by solca loads the kernel fine and when trying to execute it from fully booted Diablo system (not good idea) it turns screen black and hangs. So I guess it tries to run it but hopefully new kernel just doesn't like current state of hardware. I'll try to run it from initfs so less hardware gets initialized.