From: Marcel Holtmann <marcel@holtmann.org>
To: Oguzhan Eris <eris3@ekls.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem "coldplugging"
Date: Sun, 04 Jan 2004 20:19:36 +0100 [thread overview]
Message-ID: <1073243976.25261.160.camel@pegasus> (raw)
In-Reply-To: <1073239248.2928.18.camel@localhost>
Hi,
> Hi, I was wondering if someone could help me out with a problem using
> the IOGEAR GBU301 device which requires bluefw.
>
> Everything works fine if I hotplug the device with the device matching
> bluefw.usermap and running the appropriate bluefw command.
>
> I have kernel 2.6.0 (now upto rc1-mm1) with the bluetooth matches
> from patch-2.6.0-mh1 (it applied cleanly to 2.6.0-rc1) I have tried
> ALL combinations.
the patch-2.6.0-mh1 don't apply cleanly to 2.6.0-rc1 :(
Try to use 2.6.0-mh2 and don't install bluefw. The new bcm203x provides
the same functionalty and uses the firmware.agent hotplug script for
firmware loading.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-01-04 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 18:00 [Bluez-users] Problem "coldplugging" Oguzhan Eris
2004-01-04 19:19 ` Marcel Holtmann [this message]
2004-01-04 21:42 ` Oguzhan Eris
2004-01-04 21:59 ` Marcel Holtmann
2004-01-04 19:23 ` [Bluez-users] " Michael Mauch
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=1073243976.25261.160.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=eris3@ekls.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.