Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread Patryk Benderz
Dnia 2010-10-06, śro o godzinie 21:55 +0200, Marc Andre Tanner pisze:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release 
[cut]
Great! Shouldn't it also go to annou...@lists.openmoko.org
-- 
Patryk LeadMan Benderz
Linux Registered User #377521
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread giacomo 'giotti' mariani

 Hi,

 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release 

  http://www.brain-dump.org/projects/qi-bootmenu/

 with the following changes:

  - based on 2.6.34 this should hopefully fix some sd card
related problems

  - static NAND boot option in the menu, the NAND partition
is only mounted upon selection so there is no delay for
sd based boots.

To make NAND booting work out of the box it would be nice
if the distros (I tried SHR and QtMoko) could add their
kernels to the jffs2 images too.

At the moment you have to ssh into the device mount the
NAND partition, download their kernel and put it at the
right place. Something along the lines of: 

 ssh r...@$freerunner # the password is empty
 mkdir /mnt/mtdblock6
 mount -t jffs2 /dev/mtdblock6 /mnt/mtdblock6
 mkdir /mnt/mtdblock6/boot  cd /mnt/mtdblock6/boot
 wget $KERNEL
 mv $KERNEL uImage-GTA02.bin

Bonus points if the distros would place a bootlogo.png
alongside the kernel (current preferred dimension is
100x80)

  - visual feedback upon boot selection. There seems to be
a issue which ocassionally garbles parts of the 
font/text but I think it's better than before.

  - userspace updated to latest versions including EFL 1.0
beta release

  - integration of a cross toolchain into the build scripts.
this should make rebuilding everything a matter of
executing one shell script. Well at least in theory...

 Kernel and Qi ready to flash to your Freerunner can be found at:

  http://www.brain-dump.org/projects/qi-bootmenu/uImage-GTA02-bootmenu-0.2.bin
  http://www.brain-dump.org/projects/qi-bootmenu/qi-s3c2442-bootmenu-0.1.udfu

 If you flash the above Qi version, pressing AUX should boot from
 NAND and thus present the bootmenu independently of the content
 of your sd card. If you don't want to use my patched Qi then
 get it to boot from NAND in some other way, for example by putting
 noboot-GTA02 files into your sd partitions. Let me know how it
 works for you.

 The build scripts, in case anyone wants to rebuild the whole
 thing, can be found at:

  
 http://repo.or.cz/w/qi-bootmenu-system.git/snapshot/7c3a92f22e9498198212e4682b2fe078a676f1b5.tar.gz

 download and extract the tarball then run ./build.sh this will 
 download everything that is needed and then build the kernel +
 initramfs. See the README file for further information.

 What remains to be done is

  - add ubifs support

  - read partition labels? or some other way to display custom
text in the menu

  - gta01 support, this basically means kernel support in = 2.6.34
the kernel maximum size of 2MB including the initramfs
should be doable

  - ...

 Patches welcome.

 Have fun,
 Marc

   
Thanks.
__
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto 
spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: wiki.openmoko.org unreachable?

2010-10-07 Thread Stanislav Sedov
On Thu, 07 Oct 2010 00:41:29 +0200
urodelo urodelomuta...@yahoo.com mentioned:

 
 Yes, at least since 15.00 (6th October) o'clock I couldn't connect to it.
 

Same here.
Anyone knows what happened to it?

-- 
Stanislav Sedov
ST4096-RIPE


pgpYZQAbkYwee.pgp
Description: PGP signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: New Phone Project (MiniMoko) : Which functionalities ?

2010-10-07 Thread Christophe Badoit
Le 06/10/2010 17:18, Rui Miguel Silva Seabra a écrit :
   Em 06-10-2010 13:41, Thomas HOCEDEZ escreveu:
* 480x320 3.5 capacitive touchscreen
 
 A phone is the perfect size to integrate:
 
   * personal communication (phone, IM, social network)
   * always present camera (still or moving pictures)
   * computational needs (ssh somewhere, do stuff)
   * run useful programs (like email, web browser, games, other apps)
 
 For these to run well in a phone you need at least 480x800. The 
 Freerunner's 480x640 is definitly too small for most web browsing.
 
 If I go one step further in size, I'm talking about tablets:
 
  From personal experience with a SmartQ7 (now sadly broken), I attest 
 the following: 480x800 is *not* enough for displaying a more complex 
 document properly (eg, a PDF with readable text and pleasently 
 displayed), you need a bigger screensize.
 
   So when you consider such small resolutions... it's definitely not for me.

I'll have to agree with you.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread David Garabana Barro
On Miércoles, 6 de Octubre de 2010 21:55:44 Marc Andre Tanner escribió:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release
 
  http://www.brain-dump.org/projects/qi-bootmenu/


Only a question

Does the modified Qi includes 242 glamo timings patch?


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread David Garabana Barro
On Miércoles, 6 de Octubre de 2010 21:55:44 Marc Andre Tanner escribió:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release

Thanks a lot for the new release BTW :o)


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: New Phone Project (MiniMoko) : Which functionalities ?

2010-10-07 Thread Thomas HOCEDEZ
On 06/10/2010 16:31, Timo Juhani Lindfors wrote:
 Thomas HOCEDEZthomas.hoce...@free.fr  writes:

 There's nothing much to improve, nothing to remove, just adding GSM/3G
 chip. Nikolaus Schaller pointed the OPTION GTM501, which is a
 brilliant little chip ! And if we use the same one, the porting of
 distros/software will be easier from one machine to another.
  
 I read 
 http://www.option.com/en/products/products/modules/gtm501/specifications/#start
 that promises Fully documented APIs.

 Do you have access to these documents?


 

This is the chip used for the GTA04, but I'm not working on it. I can 
ask the ones involved in the project if you want.
(or find Dr Nikolaus Schaller on this ML)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: New Phone Project (MiniMoko) : Which functionalities ?

2010-10-07 Thread Thomas HOCEDEZ
On 06/10/2010 17:17, Maksim 'max_posedon' Melnikau wrote:
 On 10/6/10, Thomas HOCEDEZthomas.hoce...@free.fr  wrote:

 So, the first question is : What to add for this project being
 interresting ? Those will be minimal functions (forget Wimax, 4G,  coffe
 machines or color printer ...).
  
 As for me I just want Voice Calls/SMS and thats all.

 Even gprs/3G not important, because I can attach separate dongle
 inside smartbook itself.

 Similar about GPS. Quality of FR's GPS was much worse than in separate
 devices, GPS inside MID might be even worse than in FR, implement nice
 GPS signal in MID could be very hard task. I'll prefer use separate
 GPS dongle.



-- So you wan the ability to plug some dongles on it ...?

 Second question : Debian is able to run on such a device, but does
 developpers of other distributions can tell if it would be possible to
 port their on it ?
  
 MID is very similar to n900, we can say that SHR already supports
 it, similar for all others distros which supports BeagleBoard.
 Touchbook now supported by many OS'es. So it is a question which
 distros have FSO support.

 Andoid also could be a option, especially if AI's multi-OS support works 
 nice.

-- And an OS that is commercialy vendor is mandatory for the merketing 
plan.
 Maksim

 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: New Phone Project (MiniMoko) : Which functionalities ?

2010-10-07 Thread Maksim 'max_posedon' Melnikau
On 10/7/10, Thomas HOCEDEZ thomas.hoce...@free.fr wrote:
 Similar about GPS. Quality of FR's GPS was much worse than in separate
 devices, GPS inside MID might be even worse than in FR, implement nice
 GPS signal in MID could be very hard task. I'll prefer use separate
 GPS dongle.

 So you wan the ability to plug some dongles on it ...?

I might be was misunderstood, I see on MiniBook as *part of*
Smartbook, and Smartbook already have a lot of space inside[1] where I
can I attach usb dongles, I don't want attach anything in MiniBook.
MiniBook for me, just should be able make calls. All other staff can
be attached to Smartbook tablet part.

[1] http://www.alwaysinnovating.com/wiki/index.php/Smart_Book_top_part

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: community Digest, Vol 204, Issue 8

2010-10-07 Thread Thomas HOCEDEZ
Hi Gennady, I'm proud of your answer.

My idea for the future is based on the FR story. Building a device, that 
should be sold  used immediatly after opening the box (not 2 years 
after ;-) ). So the nobody person, with just an idea of FOSS (or not) 
will be taunted, and everyone like here too.
That's why FR got those problems :  OS lacks. The hardware is still good 
now, 3 or 4 years after which is ENORMOUS on this market. It has some 
'marketing issues' : no camera, no Faceboob application, but it was the 
first. And we can compare it to a teenager, not knowing how to handle 
his body. So no credibility.

Now we have Android that can be ported  being used a the commercial 
argument. So the software won't be a problem for the customer. Then if 
we have enough power inside the beast to let developpers have fun with 
it, it would be a double win !

And as you said, the Community is there, and as clever as active,   so, 
it won't be a problem to find answers  more ideas of what to do.

This project can represent a 'step 2' of the Freerunner/Free phone 
adventure, there is one big chance to do something this way, and I will 
do whatever I can to make it happen.

AstHrO.



On 06/10/2010 21:59, Gennady Kupava wrote:
 Hey, Paul, disagree with your idea about impossibility of commercial
 success of opensource device.

 Declaimer: all things below is just my opinion, which is formed mostly
 by reading community ml from time to time in past. It would be
 interesting to read where and why i am wrong. :)

 В Срд, 06/10/2010 в 22:31 +0400, Paul Fertser пишет:

 openm...@pulster.de (Christoph Pulster) writes:
  
 an intelligent marketing idea. My idea on the later is, to point the
 finger in the Apple direction and naming the evil by name.

 It already has at least 1 good idea, no other smartphones have - OS and
 hardware separation.


 On a related note, i think there's no commercial future with such a
 device.
  

 Openmoko proved that.
  
 Sorry, but openmoko proved only that it is really possible to make open
 phone.


 Too few interested people, really too few.
  
 Now imagine, linus tovalds wrote linux initially... alone. yeah. it
 wrote it while big DOSes, Solarises, BSDs, MacOSes, mimixes,  already
 existed and were fully functional. Yeah, OS he did lack of all features,
 had no chances to compete with that big giants, it were complete crap.
 Were this 'too much people'?


 Despite Freerunner still being the only one.
  
 Bwware, big portion of critics below:

 Why freerunner commercially failed (is it truth at all btw?), my
 version:

 1. People got scarified with tons of grave software bugs (WSOD,
 partition table corruption, sd card speed, graphical subsystem speed,
 overall FR speed, events/0, debug kernel, that just _i_ know). All this
 were fixable, What would happen if all this were fixed in a week after
 FR release?

 2. People scarified by core openmoko's own _developers_ who declare
 various subsystems are 'outdated' (CPU) or 'wrong' (glamo), and did nice
 PR. And all this were not really true. HW is good enought to do many
 things.

 3. Community managment may be much better. I am usure if openmoko had
 dedicated guy to spend all time managing community. I saw some mails
 from people who offer help, unanswered. Yes, may be some offers were
 funny, may be 50% of that people will do nothing, but other 50% may
 easily build excellent community and greatly help project. I guess this
 is main cause of 'few people'.

 4. Team were too small to handle such huge innovative project as
 freerunner (completely new software stack, adapt linux from almost 0 to
 be usable on such multifunctional device) from almost 0 to commercial
 success in reasonable time. One man did qt/x11. Other man did whole
 kernel and bootloader. One more man did testing. Yeahhh. One more whole
 graphical subsystem.

 5. Tons of hardware bugs on initial release. And knowing that all them
 were fixed... just proves that it were possible to fix that faster, with
 bigger team.

 6. Openmoko's team fixed problems is complete weird way. They did one
 interface, found it has some problems and instead of fixing problems
 they used qt interface, then instead of fixing problems of qt they
 switched to fsoe17, which i bet, still has problems on it's own.
 Instead of careful calculation why their device is slow and how fast it
 should be, then solved boot speed problem with disabling logs. Instead
 of fixing grave issues they draw fancy boot pictures. Instead of fixing
 u-boot Qi were implemented. (just things _i_ noticed)

 7. Raster need special mentioning. Being smart and very professional
 man, he thought only about his own project, refusing to optimize latest
 interface for FR, injecting myths about hw slowness (320x200, 16 bit
 graphics, glamo bus speed, etc) and injecting that myths in _smart way_.
 This scarified poor community even more.

 All this bad PR were magnified greatly by openess 

Re: community Digest, Vol 204, Issue 8

2010-10-07 Thread Thomas HOCEDEZ
On 06/10/2010 19:37, Christoph Pulster wrote:

 Once again my rants, Touchbook from A.I. is a piece of crap.
 Pointing with the stylus on the touchscreen and the device is bending
 back to the table. This problem was solved 20 years ago with Psion
 Series 3.
 Besides case has a ugly plastic touch and feel, very bad end-quality,
 unit is getting hot, is heavy, sliding in/out of docking is pain etc
 etc.


I read a lot of reviews of TouchBook, and there is actually a problem on 
the device design. (the fact that the motherboard is on the screen might 
be one). But A.I. tried something, and they often came back with new 
versions.
And here we are talking about the MiniBook, I didn't review for now.
 All in all, I see no reason to spend any effords in this way.
 What we need is a updated GTA02 (a mobile 100% FOSS device) and a
 intelligent marketing idea. My idea on the later is, to point the finger
 in the Apple direction and naming the evil by name. Considering
 ourselves on the light side of gadgets :-)

I'm a pacifist in the heart, and I don't want to start battle against 
something. My philosophy is to build things, not destroying. If you kill 
something, you've got one thing less : If it's a friend, so bad, one 
friend lost, if it's an ennemy, one less to compare with you that your 
idea is better than his.
We're not on the same level than Big A. We all know it. But if we can 
be the little annoying thing in its eye, why not !

When I see all the answers here, I think It worth to spend time  
energy. Everyone waits for it, and some of the readers are ready to give 
a hand. We inherited the FR community, and the community Work, we can't 
let such a chance letting go.

And As you are here, Christoph, If this phone is build one day, would 
you agree to sell it ? Your point of view is really interresting I think.

Thanks a lot,

AstHrO
 Christoph


 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: wiki.openmoko.org unreachable?

2010-10-07 Thread Joerg Reisenweber
afaik the whole infrastructure is hosted by Hetzner sub yourserver which in 
turn is our wellknown openmoko central services alias roh and gismo.

Looks like a misconfic in one of the boxes not routing correctly to one of the 
vhosts. 

I pinged roh about it


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: wiki.openmoko.org unreachable?

2010-10-07 Thread Kent S. Knudsen
http://www.robtex.com/dns/wiki.openmoko.org.html#records

No errors found.
 

jo...@openmoko.org wrote  

afaik the whole infrastructure is hosted by Hetzner sub yourserver which in 
turn is our wellknown openmoko central services alias roh and gismo.

Looks like a misconfic in one of the boxes not routing correctly to one of the 
vhosts. 

I pinged roh about it
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: wiki.openmoko.org unreachable?

2010-10-07 Thread Joerg Reisenweber
hetzner moved irons. fs needed fsck and other service, after 2 years 'uptime'
Central Services (aka roh, gismo) is taking care of it.
ETA unknown yet.

sorry for the inconvenience
/j


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread Marc Andre Tanner
David Garabana Barro schrieb:
 On Miércoles, 6 de Octubre de 2010 21:55:44 Marc Andre Tanner escribió:
 Hi,

 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release

  http://www.brain-dump.org/projects/qi-bootmenu/
 
 
 Only a question
 
 Does the modified Qi includes 242 glamo timings patch?

No. It's the same as in the initial release (built sometime in February)
I am not really up to date regarding the glamo timings, is it stable?
What are the prefered settings? If you provide a patch I can add it.
Or better yet someone should commit it to the openmoko git repository
then I will pick it up 'automatically'.

I only found:

  http://dos.openmoko.pl/overclock/

but it seems you can change the timings at runtime too.

  ./memwrite $((0x4808)) $((0x1380))

Marc

-- 
  Marc Andre Tanner  http://www.brain-dump.org/  GPG key: CF7D56C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread David Garabana Barro
On Jueves, 7 de Octubre de 2010 16:25:03 Marc Andre Tanner escribió:
 David Garabana Barro schrieb:

  Does the modified Qi includes 242 glamo timings patch?
 
 No. It's the same as in the initial release (built sometime in February)
 I am not really up to date regarding the glamo timings, is it stable?
 What are the prefered settings? If you provide a patch I can add it.
 Or better yet someone should commit it to the openmoko git repository
 then I will pick it up 'automatically'.
 
 I only found:
 
   http://dos.openmoko.pl/overclock/
 
 but it seems you can change the timings at runtime too.
 
   ./memwrite $((0x4808)) $((0x1380))
 

Nop, it's no related with overclock (which is not stable for everyone).

Glamo timings are totally stable, because they are simply put at the values the 
glamo documentation says they should be.

More info:
http://www.mail-archive.com/community@lists.openmoko.org/msg60256.html

Here you have uboot patch:

http://www.bsdmn.com/openmoko/glamo/242/

And patched Qi:

http://www.mail-archive.com/community@lists.openmoko.org/msg60284.html

As it's not overclocking, and speedup is noticeable, it would be great if you 
put it by default on your Qi.

Thank you



signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread Radek Polak
On Thursday 07 October 2010 16:25:03 Marc Andre Tanner wrote:

 No. It's the same as in the initial release (built sometime in February)
 I am not really up to date regarding the glamo timings, is it stable?
 What are the prefered settings? If you provide a patch I can add it.
 Or better yet someone should commit it to the openmoko git repository
 then I will pick it up 'automatically'.

I am using it for 2 weeks now and it's stable. You can cherry pick commit from 
my repo:

http://github.com/radekp/qi.git

http://github.com/radekp/qi/commit/b214400c048857e0f2156028bcd7a16397094a7d

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: community Digest, Vol 204, Issue 8

2010-10-07 Thread swap38
Le 07/10/2010 14:42, Thomas HOCEDEZ a écrit :
 This project can represent a 'step 2' of the Freerunner/Free phone 
 adventure, there is one big chance to do something this way, and I will 
 do whatever I can to make it happen.
 
 AstHrO.

+1 :)

/Swap38

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community