Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
Hi Kevin, Kevin Verma wrote: I read the recent announcement of stlc45xx which still requires a binary tool for its calibration data. But there are other components like battery, 3D etc. Can someone please guide me where are more 'official' details for opening of binary blobs or N8x0 hardware viz Maemo ? at-least a roodmap to look forward to. Could you be a bit more specific? What binary blobs are you referring to? We have a wiki page, designed to help prioritise and justify requests like this, which Nokia personnel work on answering, or at the very least explaining their decision. http://wiki.maemo.org/Questions_for_Nokia If you have any specific modules you'd like to see opened, that's the right place to ask (and ideally explain why). Cheers, Dave. -- maemo.org docsmaster Email: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
On tor, 2008-09-25 at 10:28 +0530, ext Kevin Verma wrote: Dear Nokia Maemo Community, I read the recent announcement of stlc45xx which still requires a binary tool for its calibration data. But there are other components like battery, 3D etc. I cannot make predictions about other components, but for the battery software a well-educated guess is Never, and the reasons are manifold: possible liability issues, patents, and the fact that it's software developed by another branch of Nokia rather than internally within Maemo. Regards: David Weinehall ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
On Thu, 2008-09-25 at 13:56 +0300, ext David Weinehall wrote: On tor, 2008-09-25 at 10:28 +0530, ext Kevin Verma wrote: I cannot make predictions about other components, but for the battery software a well-educated guess is Never, and the reasons are manifold: possible liability issues, patents, and the fact that it's software developed by another branch of Nokia rather than internally within Maemo. In that sense it would be probably simpler to get rid entirely of it than to open it. But still no predictions, sorry. -- Cheers, Igor --- Igor Stoppa Maemo Software - Nokia Devices RD - Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Bug Jar #22
On Sun, 2008-09-14 at 23:23 -0400, Stephen Gadsby wrote: Ten biggest open enhancements by number of votes: ( https://bugs.maemo.org/buglist.cgi?bug_id=176,2639,667,1695,303,368,1046,1129,1017,417 ) 1. (11%) [176] Support for OGG Vorbis / Theora missing 2. (6%) [2639] Home View needs to have an option to lock widgets into place 3. (5%) [667] A2DP and AVRCP Bluetooth profile wanted 4. (4%) [1695] Provide open link in background 5. (3%) [303] Clock should allow configurable 12h/24h display 6. (3%) [368] USB mode selection on control panel 7. (3%) [1046] RFE: Power Management Profiles (AC/Battery, Timed, Environment and screen saver) 8. (3%) [1129] Media player doesn't save the timeposition on close 9. (3%) [1017] need 802.1X/PEAPv0/MS-CHAPv2 and/or 802.1X/EAP-TTLS/MS-CHAPv2 10. (2%) [417] WEP with 802.1x EAP PEAP not supported May be there's more than just me interested by this old enhancement request (no listed here, with 6 votes): https://bugs.maemo.org/show_bug.cgi?id=1043 Add priority to defined wifi connections Opened by Laurent GUERBY (reporter) 2007-02-09 22:20:03 GMT+3 [reply] I have access to multiple wifi networks (two router at home, one FON and another one). I defined them but I see no way to put a priority so that my Nokia N800 prefers one over the other. If it's not there it would be a useful feature. Comment #1 from Laurent GUERBY (reporter) 2008-09-25 15:55:16 GMT+3 [reply] After a year and a half I would love to see this enhancement implemented. I've recently bought an ACER Aspire One netbook (under Linux by Linpus) and the connectivity setting dialog has a list with up and down to define priority amongst wifi connection. May be it's already there? Laurent ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo SDK VMware Appliance 0.8
Hi, Maemo SDK VMWare Appliance version 0.8 has been released. This version has a smaller size (1.03GB compressed) than Maemo SDK VMWare Appliance version 0.7. Besides, this release is loaded with a lot of goodies (features of 0.7): Maemo 4.1 (Diablo) with Nokia Binaries Installer, PyMaemo packages, Maemomm libraries, USB working properly, qemu-arm-eabi used as default cpu transparency method, Eclipse with ESbox 1.4.0 plugin, and Firefox has now a lot of bookmarks for reference material. There are code samples for all the libraries and development packages cited above. http://maemovmware.garage.maemo.org/ -- Raul Fernandes Herbster Embedded and Pervasive Computing Laboratory - embedded.ufcg.edu.br Federal University of Campina Grande - UFCG - www.ufcg.edu.br Campina Grande - PB - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Background Image
Hello to all! Is it, by any chance, possible to add a background image in Maemo? White windows with buttons really annoy me, and i'd like to have an image behind my widgets.. If yes, then how? (I've searched a lot of stuff, but couldn't find anything, regarding this issue) I'm using the Gregale 2.2 Maemo version, and developing the Maemo UI with Glade. Any hint will be great. Thanx a lot, in advance! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
Hello Dave, Could you be a bit more specific? What binary blobs are you referring to? We have a wiki page, designed to help prioritise and justify requests like this, which Nokia personnel work on answering, or at the very least explaining their decision. http://wiki.maemo.org/Questions_for_Nokia This is a good set of questions from curious maemo community though not much official answers I guess. I feel a roadmap rather than bold statement and talks in this context would assure community more to stick to Nokia hardware than to stick it out of Window. If you have any specific modules you'd like to see opened, that's the right place to ask (and ideally explain why). Battery driver for now is what I'd like to see opened, if I have to really explain to Nokia like I have to plead I'd say maybe I'll like to bump up kernel version or perhaps like to try something else than ITOS all-togather , maybe a community spin of Maemo (unsupported by Nokia) That sounds good ? ~kevin ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
In that sense it would be probably simpler to get rid entirely of it than to open it. But still no predictions, sorry. Getting rid of it is maybe a choice but what would be efforts from Nokia to bring in an alternative driver then ? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
I cannot make predictions about other components, but for the battery software a well-educated guess is Never, and the reasons are manifold: possible liability issues, patents, and the fact that it's software developed by another branch of Nokia rather than internally within Maemo. That gets more questions; What is Nokia strategy to avoid getting in IP which is based on restrictive patents ? Does Nokia have plans to provide any cover to its community for collaboration of its patented technology ? Is Nokia shipping hardware that needs binary bits for some kind of lock-in to it users ? ~kevin ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to use gstreamer in diablo?
Gerolf Ziegenhain schrieb: Dear mailinglist, How could I use gstreamer in the nokia tablet with diablo? Somehow the gst-... commands are not provided and it also seems, that even though I can load the python modules, its not possible to setup an audio test source: Traceback (most recent call last): File stdin, line 1, in module gst.ElementNotFoundError: audiotestsrc gst.element_factory_make(audiotestsrc, audio) audiotestsrc is not installed by default. Should be in gstreamer0.10-plugins-base-extra or so. Stefan As I think I installed all stuff provided in the usual repositories, my question would be: Is there a quick intro on how to use gstreamer with python on the tablet? Best regards: Gerolf ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
ALSA sound driver for Nokia 770 and DSP programming
Hi,
As has been discovered long ago [1] but eventually forgotten, Nokia 770 has
AIC23 audio hardware [2] which can be used not only from DSP side, but
from ARM as well. Moreover, OS2006 kernel sources even contain an ARM driver
for it, but this driver is disabled (that's understandable as the driver is
not in a very good shape and has quite a number of bugs).
Recently I have been trying to make it running and seems like we have a very
good chance to have it working nicely. It is also interesting, that the
linux-omap guys seem to be developing a new driver [3] for AIC23 which may
eventually become a better alternative.
Kernel patch is attached. It enables AIC32 driver, adds a hack to
power on/off code so that audio codec is permanently powered on (power
on/off code is not reliable and needs to be reworked). Also it fixes a
problem with audio stuttering on video playback in mplayer (the driver
had broken position reporting which is critical for proper audio/video
synchronization).
Here is some usage instruction (beware that standard disclaimer applies:
you can use this patch at your own risk, this code is quite untested. If it
somehow manages to fry your device, you have been warned and I'm not
responsible for any breakages):
1. Disable esd daemon and DSP stuff in order to move it out of the way
(temporarily rename '/usr/bin/esd' and '/usr/sbin/dsp_dld' to something else)
2. Apply the attached patch to OS2006 kernel, compile and flash it to the
device
3. Compile and install alsa userspace library, I used alsa-lib-1.0.11.tar.bz2
4. Put attached 'asound.conf' into '/etc' directory on the device, it enables
dmix plugin for audio mixing and resampling
5. Compile and try some applications which use ALSA, I tested 'aplay'
and 'mplayer'
The driver is semi-usable now, but a lot still needs to be done:
* proper power management to avoid excessive battery drain
* audio volume control
* switch between speaker/headphone
* audio quality is a bit crappy now, this needs to be fixed
* maybe some more fixes for bugs that are yet to be discovered...
DMA code is quite suspicious (especially the way it does channels linking) and
might be responsible for audio quality issues. Also sofware mixing/resampling
code in dmix plugin can benefit from ARM optimizations.
Now regarding why we may want it. Once if we get a good, low latency, fully
functional and reliable ALSA sound driver running on ARM, it gives maemo
community a nice possibility to scrap all the proprietary DSP binaries. This
provides us with a new and shiny 252MHz C55x DSP core ready to be used by
something else :)
Free linux DSP toolchain from TI [4] supports generation of both DSP kernel
and DSP tasks for OMAP1 based devices which is sufficient for DSP development.
The toolchain license was supposed to permit open source development (with
noncommercial restriction), though the license text itself is a bit
questionable [5].
With DSP avalable for use and having no need to spend efforts on ensuring
compatibility and peaceful coexistence with proprietary binary codecs (free
and proprietary code does not mix well), it should be possible to turn
Nokia 770 into quite a powerful media player.
1. http://lists.maemo.org/pipermail/maemo-developers/2006-June/022231.html
2. http://focus.ti.com/docs/prod/folders/print/tlv320aic23b.html
3. http://thread.gmane.org/gmane.linux.ports.arm.omap/11700/focus=11709
4.
https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/index.html
5. http://www.gossamer-threads.com/lists/maemo/developers/30611
--
Best regards,
Siarhei Siamashka
diff --git a/arch/arm/mach-omap1/board-nokia770.c b/arch/arm/mach-omap1/board-nokia770.c
index 3862a77..90f113a 100644
--- a/arch/arm/mach-omap1/board-nokia770.c
+++ b/arch/arm/mach-omap1/board-nokia770.c
@@ -33,6 +33,8 @@
#include asm/arch/aic23.h
#include asm/arch/gpio.h
#include asm/arch/lcd_mipid.h
+#include asm/arch/mcbsp.h
+#include asm/arch/omap-alsa.h
extern void nokia770_ts_init(void);
extern void nokia770_mmc_init(void);
@@ -67,6 +69,42 @@ static int nokia770_keymap[] = {
0
};
+#define DEFAULT_BITPERSAMPLE 16
+
+static struct omap_mcbsp_reg_cfg mcbsp_regs = {
+.spcr2 = FREE | FRST | GRST | XRST | XINTM(3),
+.spcr1 = RINTM(3) | RRST,
+.rcr2 = RPHASE | RFRLEN2(OMAP_MCBSP_WORD_8) |
+RWDLEN2(OMAP_MCBSP_WORD_16) | RDATDLY(0),
+.rcr1 = RFRLEN1(OMAP_MCBSP_WORD_8) | RWDLEN1(OMAP_MCBSP_WORD_16),
+.xcr2 = XPHASE | XFRLEN2(OMAP_MCBSP_WORD_8) |
+XWDLEN2(OMAP_MCBSP_WORD_16) | XDATDLY(0) | XFIG,
+.xcr1 = XFRLEN1(OMAP_MCBSP_WORD_8) | XWDLEN1(OMAP_MCBSP_WORD_16),
+.srgr1 = FWID(DEFAULT_BITPERSAMPLE - 1),
+.srgr2 = GSYNC | CLKSP | FSGM | FPER(DEFAULT_BITPERSAMPLE * 2 - 1),
+/*.pcr0 = FSXM | FSRM | CLKXM | CLKRM | CLKXP | CLKRP,*/ /* mcbsp: master */
+.pcr0 = CLKXP | CLKRP, /* mcbsp: slave */
+};
+
+static struct omap_alsa_codec_config alsa_config = {
+.name = Nokia770 AIC23,
+.mcbsp_regs_alsa=
Re: ALSA sound driver for Nokia 770 and DSP programming
On Thu, Sep 25, 2008 at 10:07 PM, Siarhei Siamashka [EMAIL PROTECTED] wrote: Hi, As has been discovered long ago [1] but eventually forgotten, Nokia 770 has AIC23 audio hardware [2] which can be used not only from DSP side, but from ARM as well. Moreover, OS2006 kernel sources even contain an ARM driver for it, but this driver is disabled (that's understandable as the driver is not in a very good shape and has quite a number of bugs). Recently I have been trying to make it running and seems like we have a very good chance to have it working nicely. It is also interesting, that the linux-omap guys seem to be developing a new driver [3] for AIC23 which may eventually become a better alternative. Kernel patch is attached. It enables AIC32 driver, adds a hack to power on/off code so that audio codec is permanently powered on (power on/off code is not reliable and needs to be reworked). Also it fixes a problem with audio stuttering on video playback in mplayer (the driver had broken position reporting which is critical for proper audio/video synchronization). Here is some usage instruction (beware that standard disclaimer applies: you can use this patch at your own risk, this code is quite untested. If it somehow manages to fry your device, you have been warned and I'm not responsible for any breakages): 1. Disable esd daemon and DSP stuff in order to move it out of the way (temporarily rename '/usr/bin/esd' and '/usr/sbin/dsp_dld' to something else) 2. Apply the attached patch to OS2006 kernel, compile and flash it to the device 3. Compile and install alsa userspace library, I used alsa-lib-1.0.11.tar.bz2 4. Put attached 'asound.conf' into '/etc' directory on the device, it enables dmix plugin for audio mixing and resampling 5. Compile and try some applications which use ALSA, I tested 'aplay' and 'mplayer' The driver is semi-usable now, but a lot still needs to be done: * proper power management to avoid excessive battery drain * audio volume control * switch between speaker/headphone * audio quality is a bit crappy now, this needs to be fixed * maybe some more fixes for bugs that are yet to be discovered... DMA code is quite suspicious (especially the way it does channels linking) and might be responsible for audio quality issues. Also sofware mixing/resampling code in dmix plugin can benefit from ARM optimizations. Now regarding why we may want it. Once if we get a good, low latency, fully functional and reliable ALSA sound driver running on ARM, it gives maemo community a nice possibility to scrap all the proprietary DSP binaries. This provides us with a new and shiny 252MHz C55x DSP core ready to be used by something else :) Free linux DSP toolchain from TI [4] supports generation of both DSP kernel and DSP tasks for OMAP1 based devices which is sufficient for DSP development. The toolchain license was supposed to permit open source development (with noncommercial restriction), though the license text itself is a bit questionable [5]. With DSP avalable for use and having no need to spend efforts on ensuring compatibility and peaceful coexistence with proprietary binary codecs (free and proprietary code does not mix well), it should be possible to turn Nokia 770 into quite a powerful media player. Great stuff! Do you plan to use the dsp-gateway or dsp-bridge? -- Felipe Contreras ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: ALSA sound driver for Nokia 770 and DSP programming
On Thursday 25 September 2008, Felipe Contreras wrote: On Thu, Sep 25, 2008 at 10:07 PM, Siarhei Siamashka [...] Now regarding why we may want it. Once if we get a good, low latency, fully functional and reliable ALSA sound driver running on ARM, it gives maemo community a nice possibility to scrap all the proprietary DSP binaries. This provides us with a new and shiny 252MHz C55x DSP core ready to be used by something else :) Free linux DSP toolchain from TI [4] supports generation of both DSP kernel and DSP tasks for OMAP1 based devices which is sufficient for DSP development. The toolchain license was supposed to permit open source development (with noncommercial restriction), though the license text itself is a bit questionable [5]. With DSP avalable for use and having no need to spend efforts on ensuring compatibility and peaceful coexistence with proprietary binary codecs (free and proprietary code does not mix well), it should be possible to turn Nokia 770 into quite a powerful media player. Great stuff! Do you plan to use the dsp-gateway or dsp-bridge? Now as you mentioned that, it indeed makes sense to consider other alternatives if they exist. Do you have any links to the information about dspgateway vs. dspbridge comparison (features/performance/reliability)? Using dspgateway has a clear advantage that it is already included in the kernel. And dspgateway is more or less ok, though patching it a bit in order to improve performance will be required. -- Best regards, Siarhei Siamashka ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: ALSA sound driver for Nokia 770 and DSP programming
On Fri, Sep 26, 2008 at 12:06 AM, Siarhei Siamashka [EMAIL PROTECTED] wrote: On Thursday 25 September 2008, Felipe Contreras wrote: On Thu, Sep 25, 2008 at 10:07 PM, Siarhei Siamashka [...] Now regarding why we may want it. Once if we get a good, low latency, fully functional and reliable ALSA sound driver running on ARM, it gives maemo community a nice possibility to scrap all the proprietary DSP binaries. This provides us with a new and shiny 252MHz C55x DSP core ready to be used by something else :) Free linux DSP toolchain from TI [4] supports generation of both DSP kernel and DSP tasks for OMAP1 based devices which is sufficient for DSP development. The toolchain license was supposed to permit open source development (with noncommercial restriction), though the license text itself is a bit questionable [5]. With DSP avalable for use and having no need to spend efforts on ensuring compatibility and peaceful coexistence with proprietary binary codecs (free and proprietary code does not mix well), it should be possible to turn Nokia 770 into quite a powerful media player. Great stuff! Do you plan to use the dsp-gateway or dsp-bridge? Now as you mentioned that, it indeed makes sense to consider other alternatives if they exist. Do you have any links to the information about dspgateway vs. dspbridge comparison (features/performance/reliability)? Using dspgateway has a clear advantage that it is already included in the kernel. And dspgateway is more or less ok, though patching it a bit in order to improve performance will be required. Not really, but I've been thinking that a comparison would be useful. Perhaps some dummy DSP nodes and clients to test them on both would help. I have one for the dsp-bridge, but not dsp-gateway. -- Felipe Contreras ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is there a roadmap for opening of binary blobs of N8x0 hardware ?
Hi Kevin, You are touching topics related with ongoing tasks at http://wiki.maemo.org/100Days/Sprint5 . Thanks for your input and please keep it going, here or in the related wiki pages I'm linking below. ext Kevin Verma wrote: I feel a roadmap rather than bold statement and talks in this context would assure community more to stick to Nokia hardware than to stick it out of Window. Sure: http://wiki.maemo.org/Task:Maemo_public_roadmapping_process - don't miss the discussion page. Now it's an interesting time because last week most of the Fremantle release roadmap was disclosed through several announcements. However, we still need to put this in a single page and call it Roadmap. Also we need an agreed process to keep the roadmap up to date. The principle of sharing the vision and disclosing release content with a special emphasis on the open source components is clear - see the slide 5 at http://flors.wordpress.com/2008/09/20/how-maemo-approaches-open-source/ If you have any specific modules you'd like to see opened, that's the right place to ask (and ideally explain why). In fact Process to request a closed source package to be open - GeneralAntilles is still a task in the backlog. I'd be happy to see it being pushed for the next sprint and nobody is stopping you to start helping out now. Until now the requests have been submitted mostly via feature requests at http://bugs.maemo.org Battery driver for now is what I'd like to see opened, if I have to really explain to Nokia like I have to plead I'd say maybe I'll like to bump up kernel version or perhaps like to try something else than ITOS all-togather , maybe a community spin of Maemo (unsupported by Nokia) That sounds good ? Last week it was announced that DSME will go open source, and one of these days the code should hit http://garage.maemo.org . Have a look to that project, hopefully you will get what you need. If not, let's talk in more detail. I'm currently working on a related task, Explanation of the reasons why the closed source packages are closed. Currently I'm drafting the general reasons why (I hope to have the draft in the wiki at the end of today). Then we will go case by case and explain which of the generic reasons apply to a specific package. This way all requests for opening components with a rationale behind will get either a YES or a NO BECAUSE. What is Nokia strategy to avoid getting in IP which is based on restrictive patents ? Having a full IPR team checking all the features and code supported officially in any Nokia product and evaluating risks. Does Nokia have plans to provide any cover to its community for collaboration of its patented technology ? I'm not sure I understand your question. Is Nokia shipping hardware that needs binary bits for some kind of lock-in to it users ? Maemo and the Nokia Internet Tablets have no lock-in feature. -- Quim Gil marketing manager, open source Maemo Software @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo summit: Please upload/link presentations
Hi, there were so many interesting presentations held at the summit. But there are still many of them not linked in http://wiki.maemo.org/Maemo_Summit_2008 Please update the site - so that the people can (re)read what you've said. Thanks! Uwe ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
