Re: [maemo-developers] Discussion of a possible project - offline calendar project
Just an idea/plan: FIRST STAGE (alpha version) 1) Create a pytgtk app that asks the user for its google-calendar account details and stores them in the device. 2) When internet connection is available (or when user requests it), it should download ical files. Perhaps it would be better using some kind of sync mechanism to check updates 3) The app could add the ical files to EDS, or just show them as a list 4) There should be a nice calendar home applet to show this data. SECOND STAGE (beta edition) 1) Add sync capabilities with phone calendar using opensync or perhaps funambol. This way is ok for having google-phone-770 calendars synced. THIRD STAGE (release candidate) 1) Create methods to create new events in the calendar and a way to sync this changes with google and phone calendar. Ideas? Anyone already coding this? Thanks in advance, 2007/1/16, Mathias Uebelacker [EMAIL PROTECTED]: By the way, a interface to mobile phones should be included - but thats will be a hard work an should be the second step Mathias 2007/1/16, Mathias Uebelacker [EMAIL PROTECTED]: Hello, thanks to for the answers. I will wait until wednesday for further answers to my question. So at this time there where some projects with little or no growth or the possibility to create a new one in Python?. So maybe we should thought about possible features in the next step. But lets wait til wednesday an see whats coming next. br Mathias 2007/1/15, Teemu Nikkilä [EMAIL PROTECTED]: Hello! On Monday, 15. January 2007 12:15, Martin Grimme wrote: Hi, This sounds really interesting. I know that there are already applications like dates or GPE-calendar for the N770 but both don't fit my needs. Since my idea was to write some sort of PIM suite specially for the 770 in the near future, maybe we should join efforts. I have written software for the 770 in C (Ogg Vorbis Player) and Python (Obscura Photo Manager) and have to say that Python wins for big applications, IMHO. Development is much faster and the code usually more clear and stable than with C. So I'd vote for Python. Funny, I started to play around with a calendar project a while ago. I use KDE Contact on the desktop and choose to store my calendar appointments as emails on an IMAP server. These mail messages contain standard iCalendar files. To get started, I wrote a very simple Python app which is able to retrieve and list the appointments from the server. Then I unfortunately ran out of time for the project as I was supposed to figure out how to render the next occurrence of a recurring appointment. There seems to be a python module for that too though. Also I'd like to be able to see the calendar of my (series 60) phone and preferably be able to synchronize with it. So I'd really love to see a calendar application that can use (offline) IMAP as a backend and also interact with a phone's calendar. I'm also willing to contribute if there was a project in Python to implement this. -Teemu ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- J. Manrique López de la Fuente http://www.jsmanrique.net msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
Hi! On 1/16/07, Peter Robinson [EMAIL PROTECTED] wrote: Camera is vga. So that means 640 x 480. That is correct! However don't expect a good framerate when using VGA resolution since the camera is meant for videocalls. Use CIF (352x288) or QCIF (176,144) if you want an acceptable (~15) fps. -- Regards, Zeeshan Ali Design Engineer, SW Open Source Software Operations Nokia Multimedia ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: Discussion of a possible project - offline calendar project
On Tue, 2007-01-16 at 09:05 +0100, Jose Manrique Lopez de la Fuente wrote: Just an idea/plan: FIRST STAGE (alpha version) 1) Create a pytgtk app that asks the user for its google-calendar account details and stores them in the device. 2) When internet connection is available (or when user requests it), it should download ical files. Perhaps it would be better using some kind of sync mechanism to check updates 3) The app could add the ical files to EDS, or just show them as a list 4) There should be a nice calendar home applet to show this data. SECOND STAGE (beta edition) 1) Add sync capabilities with phone calendar using opensync or perhaps funambol. This way is ok for having google-phone-770 calendars synced. THIRD STAGE (release candidate) 1) Create methods to create new events in the calendar and a way to sync this changes with google and phone calendar. Leaving creation of events until RC is risky, as you'll probably end up rewriting the entire application to handle that. Note that Dates + OpenSync can do bidirectional syncing from Google Calendar to EDS on the desktop, so doing the same on the 770 would involve building opensync. The synchronisation methods in eds-dbus have not been tested, but if they are broken they should be trivial to fix. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: Discussion of a possible project - offline calendar project
Yes, if opensync support is easy to do, it could be used from alpha versions. Is there python support for opensync?? 2007/1/16, Ross Burton [EMAIL PROTECTED]: On Tue, 2007-01-16 at 09:05 +0100, Jose Manrique Lopez de la Fuente wrote: Just an idea/plan: FIRST STAGE (alpha version) 1) Create a pytgtk app that asks the user for its google-calendar account details and stores them in the device. 2) When internet connection is available (or when user requests it), it should download ical files. Perhaps it would be better using some kind of sync mechanism to check updates 3) The app could add the ical files to EDS, or just show them as a list 4) There should be a nice calendar home applet to show this data. SECOND STAGE (beta edition) 1) Add sync capabilities with phone calendar using opensync or perhaps funambol. This way is ok for having google-phone-770 calendars synced. THIRD STAGE (release candidate) 1) Create methods to create new events in the calendar and a way to sync this changes with google and phone calendar. Leaving creation of events until RC is risky, as you'll probably end up rewriting the entire application to handle that. Note that Dates + OpenSync can do bidirectional syncing from Google Calendar to EDS on the desktop, so doing the same on the 770 would involve building opensync. The synchronisation methods in eds-dbus have not been tested, but if they are broken they should be trivial to fix. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- J. Manrique López de la Fuente http://www.jsmanrique.net msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Improving Cairo performance on the N800
Hello!
Now, the recently announced Nokia N800 is different from the 770 in
various ways that are interesting for Cairo performance. I've got my
eye on the ARMv6 SIMD instructions and the PowerVR MBX accelerator.
Yeah! me too. The combined power of these two can make it possible
to optimize a lot of nice free software out there for the N800 device.
However! while former is fully documented and the documentation is
available for general public, it doesn't have a lot to offer. ARMv6
SIMD only operate on 32-bit words and hence i find it unlikely that it
can be used to optimize double fp emulation in contrast to the intel
wirelesss MMX, which provides a big bunch of 128-bit (CORRECTME: or
was it 64- bit?) SIMD instructions. OTOH, these few SIMD instructions
can still be used to optimize a lot of code but would it be a good
idea for cairo if you need to convert the operand values to ints and
the result(s) back to float?
I have already been thinking on utilizing ARMv6 before the N800 was
release to public. My proposed plan of attack for the community (and
also the Nokia employees) is simply the following:
1. Patch GCC to provide ARMv6 intrinsics. (1 MM at most)
2. Patch liboil [1] to utilize these intrinsics when compiled for
ARMv6 target (1-3 MM)
3. Make all the software utilize liboil wherever appropriate or ARMv6
intrinsics directly if needed.
The 3rd step would ensure that you are optimizing your software for
all the platforms for which liboil provides optimizations. OTOH! one
can skip step#1 and write liboil implementations in assembly.
I already did a little progress on this and the result is two
header files which provides inline functions abstracting the assembly
instructions. I am attaching the headers. One of my friend was
supposed to convert them to gcc intrinsics and patch gcc but i never
got around to finish them. However I am attaching the headers so
anyone can use it as a starter if he/she likes.
Using PowerVR MBX accelerator is a completely different story.
Although it has a lot to offer but I failed to find any documentation
on it. There were tons of documentation on how to use the OpenGL ES
implemented on top of MBX. If you come across any documentation on
that, please let me know.
[1] http://liboil.freedesktop.org/
--
Regards,
Zeeshan Ali
Design Engineer, SW
Open Source Software Operations
Nokia Multimedia
#ifndef __ARMV6_ARITHMETIC__
#define __ARMV6_ARITHMETIC__
/** 8-bit SIMD operations */
/* Signed 8-bit SIMD add */
static __inline unsigned long sadd8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(
sadd8 %0, %1, %2\n
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Signed 8-bit SIMD subtraction */
static __inline unsigned long ssub8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(
ssub8 %0, %1, %2\n
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Unsigned 8-bit SIMD addition */
static __inline unsigned long uadd8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(
uadd8 %0, %1, %2\n
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Unsigned 8-bit SIMD subtraction */
static __inline unsigned long usub8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(usub8 %0, %1, %2
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Signed saturating 8-bit SIMD addition */
static __inline unsigned long qadd8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(qadd8 %0, %1, %2
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Signed saturating 8-bit SIMD subtraction */
static __inline unsigned long qsub8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(qsub8 %0, %1, %2
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Unsigned saturating 8-bit SIMD addition */
static __inline unsigned long uqadd8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(uqadd8 %0, %1, %2
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Unsigned saturating 8-bit SIMD subtraction */
static __inline unsigned long uqsub8(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(uqsub8 %0, %1, %2
: =r (d)
: r (m), r (n)
: cc);
return d;
}
/** 16-bit SIMD operations */
/* Signed 16-bit SIMD add */
static __inline unsigned long sadd16(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(sadd16 %0, %1, %2
: =r (d)
: r (n), r (m)
: cc);
return d;
}
/* Signed 16-bit SIMD subtraction */
static __inline unsigned long ssub16(unsigned long n, unsigned long m)
{
unsigned long d;
__asm__ __volatile__(ssub16 %0, %1, %2
: =r (d)
: r (n), r (m)
: cc);
Re: [maemo-developers] Re: Discussion of a possible project - offline calendar project
To myself, yes, it seems there is a python plugin for it... 2007/1/16, Jose Manrique Lopez de la Fuente [EMAIL PROTECTED]: Yes, if opensync support is easy to do, it could be used from alpha versions. Is there python support for opensync?? 2007/1/16, Ross Burton [EMAIL PROTECTED]: On Tue, 2007-01-16 at 09:05 +0100, Jose Manrique Lopez de la Fuente wrote: Just an idea/plan: FIRST STAGE (alpha version) 1) Create a pytgtk app that asks the user for its google-calendar account details and stores them in the device. 2) When internet connection is available (or when user requests it), it should download ical files. Perhaps it would be better using some kind of sync mechanism to check updates 3) The app could add the ical files to EDS, or just show them as a list 4) There should be a nice calendar home applet to show this data. SECOND STAGE (beta edition) 1) Add sync capabilities with phone calendar using opensync or perhaps funambol. This way is ok for having google-phone-770 calendars synced. THIRD STAGE (release candidate) 1) Create methods to create new events in the calendar and a way to sync this changes with google and phone calendar. Leaving creation of events until RC is risky, as you'll probably end up rewriting the entire application to handle that. Note that Dates + OpenSync can do bidirectional syncing from Google Calendar to EDS on the desktop, so doing the same on the 770 would involve building opensync. The synchronisation methods in eds-dbus have not been tested, but if they are broken they should be trivial to fix. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- J. Manrique López de la Fuente http://www.jsmanrique.net msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] -- J. Manrique López de la Fuente http://www.jsmanrique.net msn: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Improving Cairo performance on the N800
Hi, On Mon, Jan 15, 2007 at 09:48:35PM -0800, ext Daniel Amelang wrote: - Write a new Cairo backend that targets OpenVG, since the PowerVR MBX has fully-accelerated OpenVG rendering. I haven't found anything about OpenVG + Maemo 3.0, so maybe the software infrastructure isn't there yet to do this. - Something involving the OpenGL capabilities of the MBX. It doesn't support shaders, so it would be pretty limited. It does support multitexturing, so maybe a poor man's glitz is feasible. We don't currently use the MBX block at all: there's no driver or anything to hook into. Cheers, Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Anybody has any news about a PIM application in the hildon framework (and so for 770/800?)
I was looking for hildon docs about calendars because I started hacking a little on winzig in Python and run into this http://www.maemo.org/platform/docs/pymaemo/pyhildon_weekdaypicker.html The fact that astonished me is that... Description Weekday picker supports non-mutually exclusive selection of days of the week. Selected days of the week are shown with a pushed-in effect. Weekday picker is used where users are required to pick days on which a certain event should take place, for example, which days a Calendar event should be repeated on. It is used in __Calendar in the Repeat dialog, in Tasks in the Repeat dialog__ and in the Email set-up wizard Calendar Tasks repeat dialog??? Am I missing something or what?!?!? Rgds, Michele ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Discussion of a possible project - offline calendar project
Hi; On 1/15/07, Andrew Flegg [EMAIL PROTECTED] wrote: On 1/15/07, Martin Grimme [EMAIL PROTECTED] wrote: [development of another PIM suite] This sounds really interesting. I know that there are already applications like dates or GPE-calendar for the N770 but both don't fit my needs. Since my idea was to write some sort of PIM suite specially for the 770 in the near future, maybe we should join efforts. I don't think GPE is the perfect PIM suite (it is the most mature we've got, though) and Dates is still very immature. However, is what you want so diametrically opposed to the aims of these two projects that you couldn't work with them to improve the existing projects, rather than creating another? I guess though similar on the surface in what they do, they are actually very different in how they go about things. For example Dates, unlike GPE-cal(afaik), uses a client-server split and attempts to align itself more with, and reuse, desktop technologies in having an optimised EDS backend (which actually gives *alot* for 'free but not of all that functionality used as yet ). We also wanted to experiement a bit with the UI as to at least try and come up with something workable but original that didn't follow the kind of standard PDA calendar app blueprint. If it's a case of getting in at the ground floor, the relative youth of Dates might be more interesting to you; and there are some nice UI ideas in there which will only improve with decent synchronisation. I don't know the people at Opened Hand responsible for Dates, but I can't believe they wouldn't be interested in the help? Especially from two talented, enthusiastic programmers. Of course help is always welcomed, Bugzilla; http://bugzilla.o-hand.com/buglist.cgi?product=dates is a good place to start. Just as a note, Dates is still being developed (we recently released 0.2 for example and have bora packages - maemo.o-hand.com ). We have basic syncing (This is infact where we have been currently focusing, admittadly limited ,attention) just not quite at release quality as yet. -- Matthew ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
On mån, 2007-01-15 at 11:50 -0800, ext Ty Hoffman wrote: Y'all, I haven't seen any specs on the n800 camera (resolution, etc.). Can anybody point me in the right direction? Thanks. Oh, and for what it's worth, I'm now getting annoyed with the speed of the n800 developer discount program...I want to buy an 800, but of course would like to know if I'm one of the chosen ones for the discount. Don't want to buy one and then get the 'you're a winner!' email. I don't like to complain, because I know it's probably tough to manage a discount program and be fair, but a little more alacrity would be good. Meanwhile I'll just sit here on my hands for a few days more before I make the drive to CompUSA. Any ETA out there?? Yeah, I understand how annoying it is that it has been a whole week (gasp!) since the product launch without any decisions on what developers will be picked for the developer discount program. Oh and woes if it would take another week or two. Maybe not *all* virtues are lost, but patience certainly seem to be dead and buried. On a more serious note: the reason this is taking time is simple: we've spent enormous amounts of energy on getting the N800 out in time in the first place. We simply haven't had any time to focus on the developer discount program, since it did not have a firm deadline; CES did... Regards: David Weinehall ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Weinehall schreef: On mån, 2007-01-15 at 11:50 -0800, ext Ty Hoffman wrote: Y'all, I haven't seen any specs on the n800 camera (resolution, etc.). Can anybody point me in the right direction? Thanks. Oh, and for what it's worth, I'm now getting annoyed with the speed of the n800 developer discount program...I want to buy an 800, but of course would like to know if I'm one of the chosen ones for the discount. Don't want to buy one and then get the 'you're a winner!' email. I don't like to complain, because I know it's probably tough to manage a discount program and be fair, but a little more alacrity would be good. Meanwhile I'll just sit here on my hands for a few days more before I make the drive to CompUSA. Any ETA out there?? Yeah, I understand how annoying it is that it has been a whole week (gasp!) since the product launch without any decisions on what developers will be picked for the developer discount program. Oh and woes if it would take another week or two. Maybe not *all* virtues are lost, but patience certainly seem to be dead and buried. On a more serious note: the reason this is taking time is simple: we've spent enormous amounts of energy on getting the N800 out in time in the first place. We simply haven't had any time to focus on the developer discount program, since it did not have a firm deadline; CES did... I take nokia is going to refund the €300/$300 price difference for people that bought an n800 already but are going to be in the dev program? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFrMitMkyGM64RGpERAl+UAKCUqTA7z5/FznOJQVGEyrOXlNPaRQCgjFC8 M9O5bo8qVWcSDv2pM2V7i/8= =LKbj -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Improving Cairo performance on the N800
El mar, 16-01-2007 a las 12:20 +0200, ext Daniel Stone escribió: We don't currently use the MBX block at all: there's no driver or anything to hook into. There was a linux driver for PowerVR from Imagination Technologies for 2.4 kernels, but I think is not open source :( Salu2 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
On tis, 2007-01-16 at 13:44 +0100, ext Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Weinehall schreef: On mån, 2007-01-15 at 11:50 -0800, ext Ty Hoffman wrote: Y'all, I haven't seen any specs on the n800 camera (resolution, etc.). Can anybody point me in the right direction? Thanks. Oh, and for what it's worth, I'm now getting annoyed with the speed of the n800 developer discount program...I want to buy an 800, but of course would like to know if I'm one of the chosen ones for the discount. Don't want to buy one and then get the 'you're a winner!' email. I don't like to complain, because I know it's probably tough to manage a discount program and be fair, but a little more alacrity would be good. Meanwhile I'll just sit here on my hands for a few days more before I make the drive to CompUSA. Any ETA out there?? Yeah, I understand how annoying it is that it has been a whole week (gasp!) since the product launch without any decisions on what developers will be picked for the developer discount program. Oh and woes if it would take another week or two. Maybe not *all* virtues are lost, but patience certainly seem to be dead and buried. On a more serious note: the reason this is taking time is simple: we've spent enormous amounts of energy on getting the N800 out in time in the first place. We simply haven't had any time to focus on the developer discount program, since it did not have a firm deadline; CES did... I take nokia is going to refund the €300/$300 price difference for people that bought an n800 already but are going to be in the dev program? I have no idea... Regards: David ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Anybody has any news about a PIM application
== Date: Tue, 16 Jan 2007 13:52:18 +0100 From: =?ISO-8859-1?Q?Fred_Lef=E9v=E8re-Laoide?= [EMAIL PROTECTED] To: maemo-developers@maemo.org Subject: Re: [maemo-developers] Anybody has any news about a PIM application in the hildon framework (and so for 770/800?) == Hi Michele, For what I know Winzig has been already ported to Maemo. check out : http://www.muth.org/Robert/Winzig/ Thank you, infact I currently use it and keep it syncro with my desktop using Unison. The main question was more about if anyone has got any rumour about some native PIM apps from Nokia, due to this new entries. I was just wondering if my time was well spent in Hacking Winzig to adapt it more to my needings and Hildonizating it a little more or just to wait for Nokia to make its own PIM. The fact is that my N9210 PIM was perfectly suited for me, so if something similar is going to be released for N800, well... I prefer to spend my spare time in something else :)! Rgds, Michele ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] examining n800 kernel
Hi, I've been looking at the n800 kernel source in bora repository to figure out what n800 is like comparing to the n770. Here is a summary of some things I found. As I don't have the device I may be wrong with something that could be easily verified. kernel is 2.6.18-omap1 - everybody probably knows that :-) MMC/SD 4 bit data bus seems to be used only for SD cards, omap2 maximum speed is now set to 48Mhz (was 24Mhz for omap1 reduced to 12Mhz for N770). There are no high speed MMCmobile/plus (or high speed SD) patches applied so I guess SD cards run at 24Mhz, MMC at 16Mhz. There are also no patches for wider bus width (4 bit) for MMCmobile. SDHC cards are not supported too. As there are patches floating on the net for all these things (done mostly by Philip Langdale http://intr.overt.org/blog/) future looks promising :-) Oh, BTW multiblock writes _are_ enabled in this kernel. Video similar setup like N770 but hopefully improved (finally no memory bicycle but proper bus?). The external videochips seems to be from epson too, not 472 but 475 (or 4 in early prototypes?) called Blizzard and Hailstorm. Difference seems to be bigger memory buffer (1280K) that allows 24 bits in 800x480 instead of 16 on N770. See also http://www.erd.epson.com/index.php?option=com_docmantask=cat_viewgid=68Itemid=40 So the framebuffer is still external but handled by something different. OMAP1 uses something called SOSSI, OMAP2 calls it RFBI (remote frame buffer ...) Interesting is that omap framebuffer driver now contains code for synchronization on vblank and preventing tearing effect. It is both in omapfb/blizzard/rfbi code for n800 and also for omapfb/hwa472/sossi code for n770! Lets hope some variant of this kernel will go into some future n770 firmware. If not we can try to backport it for mplayer. from the code it looks like the pin from 472 chip signalling horizontal or vertical blank perion is indeed connected to something and checked (?) inside sossi driver. The is still no support for display rotation feature of the epson chip. Both IVA and MBX are a bit of a mystery to me. Probably another ones to the bag with jazzelle technology so it won't feel alone there unused :-) http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123navigationId=12719contentId=27458 USB Seems to be 2.0, capable of high speed mode (480MBits), chip is TUSB6010 by TI. No usb host mode is compiled in the kernel. Usb host mode support was also removed from initfs (usb booting) so this may look bad. BT Was already discussed, see the bt headsed thread - Bluecore4 CSR chip capable of BT2.0, driver is called hci_h4p in drivers/bluetooth/hci_h4p (not present in mainline kernel?). WI-FI seems to be same chip as in (newer) N770 devices (?), similar firmware blobs (3825.arm, 3826.arm) probably newer versions. Hopefully the speed will be better that those 500KB/s on N770 thanks to rest of the system. Audio Alsa compiled in, OMAP24xx EAC driver, mixer support, PCM should be handled by DSP. Feel free to correct or expand if something is wrong/missing. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] examining n800 kernel
Hi Frantisek, BT Was already discussed, see the bt headsed thread - Bluecore4 CSR chip capable of BT2.0, driver is called hci_h4p in drivers/bluetooth/hci_h4p (not present in mainline kernel?). the mainline inclusion is work in progress, but the driver (especially its firmware handling) needs some major cleanup. Regards Marcel ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Encouraging developers to use Maemo Extras
Hi, While everyone who makes packages for Debian like to see them in Debian Unstable or Ubuntu Universe (modulo proprietary software developers), while there is little activity in Maemo Extras. That's not surprising, as there is no or little advertisment of Extras in the development documentation. Extras should be clearly labeled as official unofficial :) repository. As little as several lines of text in the strategic places: packaging instructions, list of available software, maybe the wiki front page may improve situation a lot. I call it improvement because quite often quickly hacked version of Maemo packages are even released without sources and .diff.gz just because authors don't bother to do so. Establishing some quality standards for the application packages (bugtracking, version tracking etc) would attract more developers to the Maemo (exactly as Debian policies/structure/quality attracted many people). -- JID: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
Zeeshan Ali wrote: Hi! On 1/16/07, Peter Robinson [EMAIL PROTECTED] wrote: Camera is vga. So that means 640 x 480. That is correct! However don't expect a good framerate when using VGA resolution since the camera is meant for videocalls. Use CIF (352x288) or QCIF (176,144) if you want an acceptable (~15) fps. Thanks for the info! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Python for Maemo -- new version released
We from INdT (Nokia Institute of Technology -- Brazil) have the pleasure to announce the new version of Python for Maemo, for Maemo SDK 2.1 (Scirocco) and SDK 3.0 (Bora). Highlights of this version: * Support for N800 device/software (SDK 3.0) * Language updated to Python 2.5 * Updated bindings * Added bindings to new Hildon widgets * Improved OSSO bindings * Project home has moved to Garage.maemo.org. The new project page is http://pymaemo.garage.maemo.org. There you can find directions about repositories, installation on SDK/device etc. The release notes for this version can be found at http://pymaemo.garage.maemo.org/pymaemo25_releasenotes.html. We encourage everybody to try the software and report bugs/improvement requests. -- Elvis ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
On 1/16/07, Zeeshan Ali [EMAIL PROTECTED] wrote: Hi! On 1/16/07, Peter Robinson [EMAIL PROTECTED] wrote: Camera is vga. So that means 640 x 480. That is correct! However don't expect a good framerate when using VGA resolution since the camera is meant for videocalls. Use CIF (352x288) or QCIF (176,144) if you want an acceptable (~15) fps. Has anyone done any testing to see what the max [EMAIL PROTECTED] is? Is the bottleneck with the internal memory bandwidth or CPU speed. Also, is it accessible as a v4l2 device so that other apps can be easily written to use it? /Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
David Weinehall wrote: On mån, 2007-01-15 at 11:50 -0800, ext Ty Hoffman wrote: Y'all, I haven't seen any specs on the n800 camera (resolution, etc.). Can anybody point me in the right direction? Thanks. Oh, and for what it's worth, I'm now getting annoyed with the speed of the n800 developer discount program...I want to buy an 800, but of course would like to know if I'm one of the chosen ones for the discount. Don't want to buy one and then get the 'you're a winner!' email. I don't like to complain, because I know it's probably tough to manage a discount program and be fair, but a little more alacrity would be good. Meanwhile I'll just sit here on my hands for a few days more before I make the drive to CompUSA. Any ETA out there?? Yeah, I understand how annoying it is that it has been a whole week (gasp!) since the product launch without any decisions on what developers will be picked for the developer discount program. Oh and woes if it would take another week or two. Maybe not *all* virtues are lost, but patience certainly seem to be dead and buried. On a more serious note: the reason this is taking time is simple: we've spent enormous amounts of energy on getting the N800 out in time in the first place. We simply haven't had any time to focus on the developer discount program, since it did not have a firm deadline; CES did... Regards: David Weinehall Well, David, I tried to be as nice as possible with my comment about the wait, which is why I said I understand it's not easy to manage a program like this, and get it going. So I'm thinking that the (gasp!) crap is uncalled for. Again, I know it's a tough thing to find the time. I also am sure that it would not have been difficult to decide on and publish a date saying 'notifications will be sent out by date', so that everything is not a riddle wrapped in a mystery inside an enigma. --Ty ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
I take nokia is going to refund the €300/$300 price difference for people that bought an n800 already but are going to be in the dev program? Wow, that's a wonderfully well developed sense of entitlement you've got there. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
On 16 Jan 2007, at 18:27, Ty Hoffman wrote: Well, David, I tried to be as nice as possible with my comment about the wait, which is why I said I understand it's not easy to manage a program like this, and get it going. So I'm thinking that the (gasp!) crap is uncalled for. Again, I know it's a tough thing to find the time. I also am sure that it would not have been difficult to decide on and publish a date saying 'notifications will be sent out by date', so that everything is not a riddle wrapped in a mystery inside an enigma. Surely you either need one _now_ for business reasons (in which case you can buy one), or you just want one, in which case whining about how Nokia won't tell you right now whether or when they're going to give you one on the cheap is likely to be counterproductive at best. Christmas was last month. Nokia do need to start taking 'open' seriously if they want this platform to be a true success - just look how many questions on this list are about the closed aspects of the code and how many people there are itching to work on those issues. We need to persuade them to open the source, not complain about how they don't give out enough free hardware. M ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
On 1/16/07, Matt Clark [EMAIL PROTECTED] wrote: I take nokia is going to refund the €300/$300 price difference for people that bought an n800 already but are going to be in the dev program? Wow, that's a wonderfully well developed sense of entitlement you've got there. Getting beyond the easily misinterpreted intentions of mailing list participants, he does have a very good idea. If Nokia just sends 500 worthy developers mail-in rebates for store-bought n800's then there is no issue of waiting anymore. It is probably the easiest thing to handle logistically on Nokia's side also. On another note, one beneficial thing that this delay has generated is a lot of developer activity on the 770 as devs fight to get noticed via project updates :] So as a simple user I say, Nokia, delay all you want ;] /Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
Michael Wiktowy wrote: On 1/16/07, Matt Clark [EMAIL PROTECTED] wrote: I take nokia is going to refund the €300/$300 price difference for people that bought an n800 already but are going to be in the dev program? Wow, that's a wonderfully well developed sense of entitlement you've got there. Getting beyond the easily misinterpreted intentions of mailing list participants, he does have a very good idea. If Nokia just sends 500 worthy developers mail-in rebates for store-bought n800's then there is no issue of waiting anymore. It is probably the easiest thing to handle logistically on Nokia's side also. On another note, one beneficial thing that this delay has generated is a lot of developer activity on the 770 as devs fight to get noticed via project updates :] So as a simple user I say, Nokia, delay all you want ;] /Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers Yes, I also noticed the flurry of dev projects after the announcement. Interesting. Maybe the whole discount program is just a psychological experiment on motivation and reward, and there are no discounted units. Perhaps it's a first test for the 'bounty' program discussed earlier...(please don't misinterpret my intentions! I'm just kidding!) --Ty ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] For want of a ... (Was: n800 camera specs)
Getting beyond the easily misinterpreted intentions of mailing list participants, he does have a very good idea. If Nokia just sends 500 worthy developers mail-in rebates for store-bought n800's then there is no issue of waiting anymore. It is probably the easiest thing to handle logistically on Nokia's side also. That is so sensible it will never happen ;-) I would be delighted to be proved wrong though, and also I'd like to ask a very open question: How many people on this list are being held back in development by lack of access to hardware? Or any other resource? What's the thing that would most accelerate your development activity? Steve Ballmer might be a bit of a plonker at times, but 'Developers! Developers! Developers!' as a war cry has done Microsoft nothing but good. What do we, as developers, really want? I know my initial list would be: 1 more open source code 2 or, if I can't have that, dev access to non-redistributable code on easy terms (like, less than retail device cost) 3 did I mention the code? 4 discounted hardware M ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] osso-browser-interface.h
So, i'm still struggling to get a browser window to embed, but i came across this maemo garage project: https://garage.maemo.org/projects/browser/ If you download the maemo-browser-interface tarball, it seems to define osso-browser-interface.h. This version misses out the define for the new embed window. Can anyone confirm that OSSO_BROWSER_PLUG_NEW_WINDOW_REQ has been removed from the new 2007 software (from the maemo 3.0 scratchbox install? - i'm a bit hesitant to install it as i'm still programming for the 770 and have seen problems running them both). If so i think i'll abandon it as a programming option. That garage project does have some interesting functions under the browser engine abstraction layer, anyone had a play with these? Or does anyone know how the current email client embeds the browser engine in the new mail view? Any help would be appreciated. Andrew ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] For want of a ... (Was: n800 camera specs)
I know my initial list would be: 1 more open source code 2 or, if I can't have that, dev access to non-redistributable code on easy terms (like, less than retail device cost) 3 did I mention the code? 4 discounted hardware For me: 1: More freed code 2: Discounted (hardware and the software that only runs natively in given hardware), and/or more documentation about the aforementioned. I couldn't care less about dev licensing for non-redistributable code. -- Just stop and take your secret journey, you will be a new box. --Leeta http://www.gnu.org/philosophy/shouldbefree.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] For want of a ... (Was: n800 camera specs)
I couldn't care less about dev licensing for non-redistributable code. That's interesting. Is that because it's not relevant to you? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: Using the N770/N800 as a remote control.
If only the N800 had IR support then it could be used to go after the high end remote control market. Maybe we'll get it in the next model. There were at least five devices like this at CES this year. http://www.rticorp.com/products/T4.html They are remote controls in the $1,000 to $1,500 range for high end AV installations. N800 has everything necessary except for the IR support. I could easily see these vendors OEMing the N800 instead of building their own. On 1/9/07, Jon Smirl [EMAIL PROTECTED] wrote: Did a SIR transmitter make in into the N800? I have a Phillips RC9800i remote control and I would like to replace it with my N770 or a N800. http://www.hometheatermag.com/accessories/0406philips/ I've been looking around for a IR transmitter/receiver in the form of a USB dongle and can't find one. You need a receiver in addition to the transmitter so that you can train the remote codes. It only costs a couple of dollars to build a remote compatible IR transmit/receiver USB dongle. Adding this capability would be very useful given the way I use my N770. -- Jon Smirl [EMAIL PROTECTED] -- Jon Smirl [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] n800 camera specs
On Tue, Jan 16, 2007 at 12:18:52PM -0500, ext Michael Wiktowy wrote: Has anyone done any testing to see what the max [EMAIL PROTECTED] is? Is the bottleneck with the internal memory bandwidth or CPU speed. Depends: if you're attempting to display the result on-screen as well, then it greatly drops. Bus bandwidth is generally the limiting factor (memory, DMAing from camera, copying to framebuffer and subsequently to the LCD controller). Also, is it accessible as a v4l2 device so that other apps can be easily written to use it? Yeah, it is. Cheers, Daniel signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] examining n800 kernel
On Tue, Jan 16, 2007 at 02:57:16PM +0100, ext Frantisek Dufka wrote: similar setup like N770 but hopefully improved (finally no memory bicycle but proper bus?). The external videochips seems to be from epson too, not 472 but 475 (or 4 in early prototypes?) called Blizzard and Hailstorm. Difference seems to be bigger memory buffer (1280K) that allows 24 bits in 800x480 instead of 16 on N770. See also http://www.erd.epson.com/index.php?option=com_docmantask=cat_viewgid=68Itemid=40 So the framebuffer is still external but handled by something different. Correct. The bus between the display controller and the LCD controller (RFBI) isn't exactly blazing fast, though. We only use the 475. OMAP1 uses something called SOSSI, OMAP2 calls it RFBI (remote frame buffer ...) Interesting is that omap framebuffer driver now contains code for synchronization on vblank and preventing tearing effect. It is both in omapfb/blizzard/rfbi code for n800 and also for omapfb/hwa472/sossi code for n770! Yes: we use this to do vsync for video from the X server. Lets hope some variant of this kernel will go into some future n770 firmware. If not we can try to backport it for mplayer. from the code it looks like the pin from 472 chip signalling horizontal or vertical blank perion is indeed connected to something and checked (?) inside sossi driver. The is still no support for display rotation feature of the epson chip. For the moment, rotation isn't possible in the UI (lots of hardcoded 800x480s abound), so it's not been a high priority on my list, but it is certainly on it, and I'll hopefully be adding the support at some stage. Cheers, Daniel signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] For want of a ... (Was: n800 camera specs)
I couldn't care less about dev licensing for non-redistributable code. That's interesting. Is that because it's not relevant to you? Yes, for the same reason I'm hacking on the 770 instead of some ultra-proprietary pocketpc-based device. -- Just stop and take your secret journey, you will be a new box. --Leeta http://www.gnu.org/philosophy/shouldbefree.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] For want of a ...
Twas brillig at 19:40:12 16.01.2007 UTC+00 when Matt Clark did gyre and gimble: MC Wouldn't you like to see that source, even though you couldn't MC redistribute it? Not necessarily. Just a API/protocol documentation should be enough. -- JID: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Help needed on setting up the development plarform for NOKIA N770/800
Hi Following are my questions: 1.I am newbie to Linuix. I have SUSE LINUX running in the VMWare Server on Windows PC. I would like to know if there are detail steps as to how I can setup the Maemo development platform on SUSE LINUX. 2.From the links in www.maemo.org, I understand that the Mamemo works on Debian. Do I have to change my linux distro to debian only? 3.Pl. provide me what tools I have to install in order. Help is appreciated ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
