All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1
Date: Wed, 21 Jan 2004 02:36:43 +0100	[thread overview]
Message-ID: <1074649003.7088.43.camel@pegasus> (raw)
In-Reply-To: <1074626637.1707.103.camel@localhost>

Hi Max,

> > Do you have a contact for me, so we can talk about it. I
> > am also interested in a Bluetooth 1.2 firmware if it exists.
> I'm actually subscribed to Broadcomm release notifications. 
> So I'll get and email as soon as the release something. I don't think
> that they have 1.2 support yet. Anyway this subscription and stuff is
> kind of proprietary. One of the reasons I got it is because I'm a
> Qualcommer :).

I tried to contact the guys from Broadcom, but they never answered. This
makes me really unhappy.

> > I came around with this on 21 Dec and I thought about it for over 3
> > weeks before I finally decided to include this patch. I am not happy
> > with it, but doing nothing and keep the ACL link makes me even more sad.
> > The Apple mouse with its Broadcom HID stack is even more worse than I
> > can think about it. At http://www.holtmann.org/linux/bluetooth/hid.html
> > you find some of my notes about Bluetooth HID devices. And the mouse
> > never disconnects the ACL link. I checked this and it stays forever :(
> 
> I see. Well I guess it's ok as long as it doesn't brake anything.

Actually I must say I hope so ;)

The current way of waiting 4 seconds before we kill an incoming and
unused ACL link should be really long enough and in the most cases the
remote device already disconnected it before the timer kicks in. However
I haven't seen any problems in the last three weeks while I tested this
patch on my machines.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-21  1:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 19:07 [Bluez-devel] Bluetooth kernel patch for 2.6.1 Marcel Holtmann
2004-01-15 19:50 ` BCM2033 firmware loader [was Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1] Max Krasnyansky
2004-01-15 20:16   ` [Bluez-devel] Re: BCM2033 firmware loader Marcel Holtmann
2004-01-16 21:14     ` Max Krasnyansky
2004-01-17  1:19       ` [Bluez-devel] " Marcel Holtmann
2004-01-20 19:27         ` Max Krasnyansky
2004-01-15 20:03 ` [Bluez-devel] Bluetooth kernel patch for 2.6.1 Max Krasnyansky
2004-01-15 20:30   ` Marcel Holtmann
2004-01-16 21:25     ` Max Krasnyansky
2004-01-17  1:08       ` Marcel Holtmann
2004-01-20 19:23         ` Max Krasnyansky
2004-01-21  1:36           ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-13  3:59 Marcel Holtmann
2004-01-09 14:56 Marcel Holtmann

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=1074649003.7088.43.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.