public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Zhikui Chen <zhikui.chen@po.uni-stuttgart.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Re: Help for bluez-bluefw-1.0.
Date: Thu, 01 Jul 2004 15:06:28 +0200	[thread overview]
Message-ID: <1088687188.4540.202.camel@pegasus> (raw)
In-Reply-To: <40E40A44.60008@po.uni-stuttgart.de>

Hi Zhikui,

> Thanks. Whats bluez modules will be needed for 2.6.7?
> 
>  Bluetooth I will use is USB dongle ePox and the courrent kernel is 2.6.7.
> I configured 2.6.7 kernel and built it. and built bluez stuffs: hcidump, 
> hciemu, libs2.7, pan1.1, utils2.7
> And I modified /etc/modules.conf by adding lines:
> alias bt-proto-0 l2cap
> alias net-pf-31 bluez
> alias bt-proto-2 sco
> alias bt-proto-3 rfcomm
> alias bt-proto-4 bnep
> alais char-major-10-250 hci_uhci
> 
> BUT:
> For my redhat 8 (my notebook PCG 2600TEK only can be installed redhat 8, 
> redhat 9 and mandrake 9.2 could not be install), hciconfig could not be 
> found, and using locate hciconfig, there is output. Marcel could tell me 
> the reason and how should I do?
> For my redhat 9 (my PC), hciconfig reports that Can't open HCI socket, 
> Address family not surport by protocol, but for 2.4.25, it is ok. Would 
> you like to tell me, whta sould I do? I want to build a bluetooth 
> connection betweent my pc and my notebook. The both bluetooth drivers 
> are BT-DG03 (USB ePOX).

the EPoX dongles are CSR based and so not bluefw is needed. Load the
hci_usb driver and everything should work.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-07-01 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40E40440.8070109@po.uni-stuttgart.de>
     [not found] ` <1088685238.4540.190.camel@pegasus>
2004-07-01 12:57   ` Help for bluez-bluefw-1.0 Zhikui Chen
2004-07-01 13:06     ` Marcel Holtmann [this message]
     [not found]       ` <40E412AA.4070908@po.uni-stuttgart.de>
2004-07-01 13:39         ` [Bluez-users] " Marcel Holtmann
     [not found]           ` <40E416AB.2040904@po.uni-stuttgart.de>
2004-07-01 13:54             ` Marcel Holtmann
     [not found]               ` <40E41A18.8050201@po.uni-stuttgart.de>
2004-07-01 14:11                 ` Marcel Holtmann
     [not found]                   ` <40E4206F.6060101@po.uni-stuttgart.de>
2004-07-01 14:40                     ` Marcel Holtmann
2004-07-01 15:00                       ` Zhikui Chen
2004-07-01 15:02                         ` [Bluez-users] " 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=1088687188.4540.202.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=zhikui.chen@po.uni-stuttgart.de \
    /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