On 8/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> 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, i
Hi,
MMC_MOUNTPOINT variable was present on 770 already and the device had
one (external) mmc slot only. N800 added a second memory card slot
(the internal one) and respective variable...
-Markku-
David Hazel wrote:
>> You can also use the environment variables MMC_MOUNTPOINT and
>> INTERNAL_MMC
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/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
emo.org
Subject: Re: Finding the mmc cards
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
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
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
"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,
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
On 8/29/07, Tony Maro <[EMAIL PROTECTED]> wrote:
> After our thread some weeks ago regarding reading the serial number from a
> MMC card, I've since implemented detection of the MMC card's presence by the
> existence of those same files. I know my solution works on my device
> perfectly.
>
Hello I
12 matches
Mail list logo
