public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Schmidt <schmidt@nue.et-inf.uni-siegen.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave
Date: Mon, 06 Sep 2004 13:43:05 +0200	[thread overview]
Message-ID: <413C4D49.9040807@nue.et-inf.uni-siegen.de> (raw)
In-Reply-To: <1094462275.5145.22.camel@notepaq>

Hi Marcel,

Marcel Holtmann schrieb:

<snip>

 > you need at least a HCI 16.4 firmware to get it working. Check my pages
 > and the "hciconfig hci0 revision" command for more information.

Thanks for the info. I'm beginning to understand that I'm scratching
scatternet functionality with my requirements.

Looks like I have to check for a firmware upgrade of my modules (if
available...).


Michael

-- 
===========================================
Michael Schmidt
-------------------------------------------
Institute for Data Communications Systems
University of Siegen, Germany
-------------------------------------------
http:   www.nue.et-inf.uni-siegen.de
===========================================

  parent reply	other threads:[~2004-09-06 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 13:47 [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-05 17:53 ` Collin R. Mulliner
2004-09-06  8:30 ` Marcel Holtmann
2004-09-06  8:50   ` Michael Schmidt
2004-09-06  9:17     ` Marcel Holtmann
2004-09-06 10:38       ` [Bluez-users] general question on the procedure of BlueZ Johannes
2004-09-06 11:21         ` Johannes
2004-09-07  7:56           ` Johannes
2004-09-06 11:43       ` Michael Schmidt [this message]
2004-09-06  8:37 ` [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Xavier Garreau

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=413C4D49.9040807@nue.et-inf.uni-siegen.de \
    --to=schmidt@nue.et-inf.uni-siegen.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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