public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Hedin <andrewthegreat@mail.ru>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't understand
Date: Wed, 12 May 2004 15:17:09 +0200	[thread overview]
Message-ID: <1084367829.25099.16.camel@pegasus> (raw)
In-Reply-To: <200405121820.59166.andrewthegreat@mail.ru>

Hi Hedin,

> I have Redhat 9.0 with 2.6.6-mh1 patched kernel and all modules compiled.
> I have Tecom BT3030 Dongle.
> 
> I compiled bluez-libs-2.7 and bluez-utils-2.7. After some effort (big effort!) 
> I managed to compile bluez-pin (why is it needed - no word anywhere...).
> 
> I also installed all other modules without problems, except bluez-bluefw. It 
> gives following errors:

the bluez-bluefw was never ported to work on 2.6 systems. You can use
the bcm203x firmware loader driver instead. For some more information
take a look here http://www.bluez.org/drivers.html

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-05-12 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 11:20 [Bluez-users] Can't understand Hedin
2004-05-12 11:52 ` Michal Semler
2004-05-12 13:17 ` Marcel Holtmann [this message]
     [not found]   ` <200405122046.02992.andrewthegreat@mail.ru>
2004-05-12 17:13     ` Marcel Holtmann
2004-05-12 20:38   ` Achim Bohnet
2004-05-12 21:39     ` 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=1084367829.25099.16.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=andrewthegreat@mail.ru \
    --cc=bluez-users@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