From: Alex Holland <ah160@york.ac.uk>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] blue-fw not working for USB Belkin F8T001 in Gentoo Linux
Date: Wed, 07 Jan 2004 13:03:31 +0000 [thread overview]
Message-ID: <3FFC03A3.5090807@york.ac.uk> (raw)
In-Reply-To: <1073479827.2508.143.camel@pegasus>
Marcel Holtmann wrote:
> I never got the bluefw working fine with my Broadcom based dongles. So I
> wrote a kernel driver for loading the firmware. My -mh2 patch for 2.6.0
> contains this bcm203x driver, but I haven't one for the 2.4 series.
Interesting - bluefw appeared to work when I was using the 2.4.20-r9
kernel sources. It would report success, but my bluetooth connection was
very dodgy (see previous mails about instability). However, I don't know
if this was due to the usb extension cable I was using, or the firmware
being loaded incorrectly (possibly the latter, as it worked fine in
Windows even with the cable).
Any plans to backport the -mh2 patch to 2.4? The Gentoo devs would
probably be interested, they're patch crazy :)
In the meantime, I'll just do the XP/Linux reboot trick, I guess.
Alex
-------------------------------------------------------
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-07 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 12:31 [Bluez-users] blue-fw not working for USB Belkin F8T001 in Gentoo Linux Alex Holland
2004-01-07 12:50 ` Marcel Holtmann
2004-01-07 13:03 ` Alex Holland [this message]
2004-01-07 16:12 ` Marcel Holtmann
2004-01-07 14:23 ` Marc Hansen
2004-01-07 14:49 ` 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=3FFC03A3.5090807@york.ac.uk \
--to=ah160@york.ac.uk \
--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 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.