I'm interested to hear that anything outside of the SD card has a choice in the matter. There was a time when hardware write-protection of this kind was exactly that: harware-enforced write-protection. I would have expected that, if I put the switch on an SD card into the "write-protected" positi
On 8/30/07, Austin Che <[EMAIL PROTECTED]> wrote:
>
>
> I've been wondering: what is the performance hit for not going
> through gstreamer? So based on my understanding, going through
> gstreamer, the mp3 is decoded on the DSP. Supposing it was decoded
> on the cpu and sent out thro
Jesse Guardiani <[EMAIL PROTECTED]> wrote:
> And no, before you ask, I don't think it's not Nokia's fault. gstreamer
> is just unexpectedly buggy. Too bad ALSA doesn't support inline mp3
> decoders... life would be easier for all of us...
I've been wondering: what is the performance hit for n
On 8/29/07, David Hazel <[EMAIL PROTECTED]> wrote:
>
>
> - whether write protected (yes, you can write-protect an SD card)
Yes, but the Nokia's do not support or honor that switch.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lis
> You can also use the environment variables MMC_MOUNTPOINT and
> INTERNAL_MMC_MOUNTPOINT, but then you have to make sure that they are
> always set correctly in your environment. (I don't think using
> environment variables for this kind of system information is a good
> idea.)
Those environment
On 8/29/07, David Hazel <[EMAIL PROTECTED]> wrote:
>
>
>
> It's possible that cards experiencing this problem are not completely
> corrupted "beyond repair", but that they've simply had their FAT
> tables damaged to the point where most software can't deal with them. FAT32
> devices seem to have a
I've added bug #1930. I hope I've done it right, because even that procedure
isn't particularly clear.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Eero Tamminen
Sent: 29 August 2007 10:40
To: ext [EMAIL PROTECTED]
Cc: maemo-developers@maemo.org
Subject:
This is the result of communicating with Tony and Kemal (disq) off list:
https://www.guardiani.us/projects/kagu/changeset/483
Seems to have always been that way. Probably just a typo.
Jesse Guardiani wrote:
> Feel free to post a patch if you've got one.
>
> Tony Maro wrote:
>
>> I may have
Some people seem to have issues that completely corrupt beyond repair a MMC
card and it seems to be possibly tied to using the USB cable to transfer
files to/from your PC and the MMC card in the Nokia.
It's possible that cards experiencing this problem are not completely
corrupted "beyond repair"
Some of you might have seen the screenshot of my (work-in-progress)
Python-based "maemoClock" application on the itt forum
However, I've now "wasted" too many evenings trying to fix a strange issue and
would be very glad for any help/ideas:
I'm trying to use the osso.DeviceState(context).display_
It is possible to get the theme to work on rotated tabs using the procedure
that I outlined. The only useful documentation I found was at the maemo
site:
http://maemo.org/development/documentation/how-tos/3-x/howto_customization_bora.html
I never did find any documentation on parameters in gtkrc
Feel free to post a patch if you've got one.
Tony Maro wrote:
> I may have found the issue - in the Kagu code. Investigating further
> still. I noticed that it was creating a new thread and RPC every time
> you start a new song, and things seem to work just fine without doing
> that...
>
>
>
Hi Folks,
I have been trying to build gtk with the latest root
strap from
http://repository.maemo.org/stable/gregale/armel/Maemo_Dev_Platform_v2.2_armel-rootstrap.tgz
without much success. It fails in config.
After reading though the mailing list I get the sense
that this is a legacy product for
I may have found the issue - in the Kagu code. Investigating further
still. I noticed that it was creating a new thread and RPC every time you
start a new song, and things seem to work just fine without doing that...
On 8/29/07, Tony Maro <[EMAIL PROTECTED]> wrote:
>
> Okay, so I ripped out gst
Yeah, it's using dbus, which is a bit less than instantaneous in this
case. Sorry, I don't have any suggestions.
Tony Maro wrote:
> Okay, so I ripped out gstreamer and put in OSSO Media Server code.
>
> The thing I've noticed is that there's a distinct pause of about 1
> second in my code when y
Okay, so I ripped out gstreamer and put in OSSO Media Server code.
The thing I've noticed is that there's a distinct pause of about 1 second in
my code when you start a new song playing. I didn't have this issue with
gstreamer (though the other issues with gstreamer far outweigh the new
problem.)
Antonio,
Thanks. I checked out and did dpkg buildpackage -us -uc -nc -d. It
failed with the following error. Looks like xpidl under microb-engine is
missing. Do I need to build and install xpidl separately? I already
installed libidl-dev.
---
/scratchbox/tools/bin/sh: line 1: /usr/lib
With the help of timelyx and pupnik (IRC), I was able to build microb. I
have microb-engine_1.0.3-13_armel.deb and other .debs under SDK_ARMEL. I
tried dpkg -i and installation was successful (I had to install other .debs
to get there).
But I am not able to see Microb under Web in maemo (Xephyr).
On Tuesday 28 Aug 2007, Murray Cumming wrote:
> Where was doxygen actually?
>
> I've just noticed that the ARM doxygen package in Maemo Sardine doesn't
> actually seem to install a doxygen binary as it does in the X86 target.
> But maybe I'm not looking in all the right places.
I found it (well t
On 8/29/07, Marius Vollmer <[EMAIL PROTECTED]> wrote:
>
>
> The internal card is always mounted on /media/mmc2, and the external
> card is always mounted on /media/mmc1.
And when the Nokia n900 (just guessing) gets released, and it has a memory
stick socket or some other type of memory card, I as
"ext Acadia Secure Networks" <[EMAIL PROTECTED]> writes:
> It now reads 1.621. So I went ahead and tried the "click to install"
> and this time it worked!
Ok, so the author of ukmp (Urho?) has probably changed something.
> Interestingly, the message that came up while it was installing
> specifi
Zeeshan Ali wrote:
> Hello again!
>
>> Why would I file a bug? I need something that works on all firmwares.
>> Filing a bug won't help that. Besides, I'm sure Nokia's developers
>> couldn't help noticing that gstreamer was broken when they wrote OSSO
>> Media Server. Why didn't *they* file a bug,
On Wed, 2007-08-29 at 12:39 +0300, Eero Tamminen wrote:
> Hi,
>
> Please file a documentation bug into Maemo Bugzilla. We need this
> documented. Handling of removable medias, especially with file systems
> as easily corrupted as FAT, needs special care from applications
> (stop using files when
Hello again!
> Why would I file a bug? I need something that works on all firmwares.
> Filing a bug won't help that. Besides, I'm sure Nokia's developers
> couldn't help noticing that gstreamer was broken when they wrote OSSO
> Media Server. Why didn't *they* file a bug, eh?
I wouldn't know, i
Zeeshan Ali wrote:
> Hi!
>
>> gstreamer is poo. plain and simple. Yes, you need to recreate the
>> pipeline. If you don't, bad things happen, like hanging and such after
>> EOS. And no, EOS detection still doesn't work well in that class despite
>> my many tries.
>
>That sounds like a bug, ha
"ext Tony Maro" <[EMAIL PROTECTED]> writes:
> Also, what determines MMC1 vs MMC2 as the card's path for
> internal/external?
The internal card is always mounted on /media/mmc2, and the external
card is always mounted on /media/mmc1.
You can also use the environment variables MMC_MOUNTPOINT and
I
Hi,
Please file a documentation bug into Maemo Bugzilla. We need this
documented. Handling of removable medias, especially with file systems
as easily corrupted as FAT, needs special care from applications
(stop using files when pre-unmount message is delivered on them so
that unmounts succeed,
Hi!
> gstreamer is poo. plain and simple. Yes, you need to recreate the
> pipeline. If you don't, bad things happen, like hanging and such after
> EOS. And no, EOS detection still doesn't work well in that class despite
> my many tries.
That sounds like a bug, have you cared to file it? Does t
I agree that assuming mmc1 and mmc2 is potentially dangerous. In an answer to my original question on this subject, someone suggested that mmc0 and mmc1 were the correct names, whereas in my Scratchbox environment they are mmc1 and mmc2. Consequently, when I was implementing a scan for memory car
29 matches
Mail list logo
