public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: [PATCH 2.6] link trigger for AODV and +
Date: Tue, 10 Aug 2004 10:13:19 +0200	[thread overview]
Message-ID: <1092125599.4564.76.camel@pegasus> (raw)
In-Reply-To: <20040809195448.GA24140@bougret.hpl.hp.com>

Hi Jean,

> > this is a good point and I do think that this patch is a nice additional
> > feature for BlueZ, but I am not fully comfortable with it in its current
> > shape. Actually some time ago I thought about removing the support for
> > stack internal events.
> 
> 	In my stuff, I use internal events to know when hci interfaces
> go up and down and when they appear and disappear. As far as I know,
> those events are not available by any other means. They are not
> available through RtNetlink because hci interfaces are not real netdev
> interfaces.

these events should be available via hotplug and the bluetooth.agent and
because of this I was thinking about removing the stack internal stuff.

If the HCI connections themself are fully integrated into the driver and
device model an event through hotplug would be the best. Comments?

> > I sent the full patch for inclusion, but it came out that one part
> > causes troubles and so I removed this part. I didn't found the time for
> > a further investigation.
> 
> 	That's what I said : I'm going to test it properly. If you
> could remember the issue, that would help.

I searched the email exchange between Michal and me from the mailing
list archives for you. Check out this thread:

	http://thread.gmane.org/gmane.linux.bluez.user/2672

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-08-10  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  1:33 [PATCH 2.6] link trigger for AODV and + Jean Tourrilhes
2004-08-08 14:49 ` [Bluez-devel] " Marcel Holtmann
2004-08-09 18:51   ` Jean Tourrilhes
2004-08-09 19:08     ` [Bluez-devel] " Marcel Holtmann
2004-08-09 19:54       ` Jean Tourrilhes
2004-08-10  8:13         ` Marcel Holtmann [this message]
2004-08-10 16:32           ` Jean Tourrilhes
2004-08-10 22:53             ` [Bluez-devel] " Marcel Holtmann
2004-08-10 23:37               ` Jean Tourrilhes

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=1092125599.4564.76.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jt@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox