From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] About the kernel 2.6.18
Date: Mon, 9 Oct 2006 11:04:50 +0200 [thread overview]
Message-ID: <20061009090450.GI28087@suse.de> (raw)
In-Reply-To: <3f5a9ba20610081957id1408a8m6f1648b8fae14e79@mail.gmail.com>
On Mon, Oct 09, 2006 at 10:57:53AM +0800, Mingfan.Lu wrote:
> Hi,
> I am just use the Bluetooth OBEX Object Push client (0.99 beta1).
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Host:
> Vmware 5.5
> OS: Suse 10.1
> bluetooth dongle: 1.2
> File pushed: testpkg whose size is 137956B
> =
> Target:
> Nokia E61
> =
> kernel version: 2.6.16.13-4 (built from Suse 10.1) about 11-12s kernel
> version: 2.6.16.13-4 (rebuilt from above) about 11-12s
> kernel version: 2.6.17 (built from kernel.org) about 11-12s
> kernel version: 2.6.18: about 145s
> kernel version: 2.6.18 with mh4 (built with the patch from bluez): 143s
> 146s
This means that ~1000bytes/second are transferred. I am using 2.6.18 with =
ppp-via-rfcomm and it does get me at least 45kB/second (3G/UMTS speed), with
a sony-ericsson k600i as target, so there are configurations where it still
works fine.
> Too terrible!!!
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =
> using other RFCOMM applications, 2.6.18 is slower too.
Well, apparentely not everywhere and not for everybody.
-- =
Stefan Seyfried | "Please, just tell people
QA / R&D Team Mobile Devices | to use KDE."
SUSE LINUX Products GmbH, N=FCrnberg | -- Linus Torvalds
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-10-09 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f5a9ba20609291930r5b4e4c97g8b33901666fef491@mail.gmail.com>
2006-10-02 16:46 ` [Bluez-devel] About the kernel 2.6.18 Mingfan.Lu
2006-10-04 14:37 ` Marcel Holtmann
2006-10-08 6:13 ` Mingfan.Lu
2006-10-08 13:29 ` Marcel Holtmann
2006-10-09 2:57 ` Mingfan.Lu
2006-10-09 9:04 ` Stefan Seyfried [this message]
2006-10-09 9:38 ` Mingfan.Lu
2006-10-09 9:39 ` Mingfan.Lu
2006-10-09 9:49 ` Peter Wippich
2006-10-09 9:47 ` Marcel Holtmann
2006-10-09 11:57 ` Mingfan.Lu
2006-10-11 8:30 ` Mingfan.Lu
2006-10-12 2:23 ` Mingfan.Lu
2006-10-13 4:17 ` Fwd: " Mingfan.Lu
2006-10-03 14:55 ` Mingfan.Lu
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=20061009090450.GI28087@suse.de \
--to=seife@suse.de \
--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