From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
The bluez-utils package adds /etc/pcmcia/bluetooth and
/etc/pcmcia/bluetooth.conf to the pcmcia-cs package so that Bluetooth
PCMCIA devices get correctly set up.
Because some bluetooth cards behave like serial ports, with no
additional help cardmgr will set them up as such, so functionality was
added to give the facility for a card's class to be overridden, like so:
card "Bluetooth Serial Card"
manfid 0x1234, 0x5678
bind "serial_cs" class "bluetooth"
The bluetooth.conf file added by the bluez-utils package originally
had this functionality added, but because the version of pcmcia-cs
currently used is too old, this extra class override has been removed
via a patch in the bluez-utils .spec file to prevent cardmgr
complaining when sourcing this file on startup.
This functionality was apparently added to the pcmcia-cs package in
version 3.2.1 released August 2002 (from the source changelog). Please
can either this class override functionality be backported into the
current pcmcia-cs package or the base version used instead be updated
to 3.2.1 or newer?
Currently, when I insert my H4 mode Brainboxes BL-500, it gets
detected and set up as a serial port, if I then perform the steps that
the /etc/pcmcia/bluetooth script would do, (ie. run hciattach), then
the card works and behaves correctly as it should with the rest of the
Fedora Bluetooth packages, so this fix would make the card work
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert a UART-based (serial_cs driver) PCMCIA card
2. Examine /var/log/messages
Actual Results: Log messages show the card is handed to the PCMCIA
serial subsystem and set up as standard serial port
Expected Results: Log messages should show the card handed to the
PCMCIA bluetooth subsystem and set up as a serial port followed by
hciattach to attach the device into the running bluetooth daemons.
We have pcmcia-cs-3.2.7 in FC3. It ought to be fine.
Yes, I imagine it is. The bug was originally and specifically against
FC1 so I'm not sure why it was reclassified against FC2 or FC3. I
imagine this won't ever get fixed in FC1 (I'm not running it anywhere
now) so it's pointless keeping this bug new/open.