From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] linkkeys on jffs2
Date: Tue, 17 Jan 2006 11:53:40 +0100 [thread overview]
Message-ID: <1137495220.5688.7.camel@localhost> (raw)
In-Reply-To: <38907.62.33.148.3.1137487338.squirrel@62.33.148.3>
Hi Andrey,
> Got a problem with hcid storing link keys on jffs2 file system.
> Hcid is able to store only one link key, all subsequent keys doesn't
> appear in linkkeys file.
> After looking into sources I find out in common/textfile.c call of mmap()
> with MAP_SHARED flag which is not suported on jffs2.
> As mmap is used only for seeking keys in maped memory not for storing into
> file seems it's good idea to use MAP_PRIVATE flag. In this case there are
> no error on jffs2
if you inline the patch, make sure your mail client doesn't do line
breaks in that area. Otherwise attach it.
However the patch is in the CVS now. Thanks.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-01-17 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 8:42 [Bluez-devel] linkkeys on jffs2 andrew
2006-01-17 10:53 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1137495220.5688.7.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).