Has been seen to work on several cards and communicating with several mobile phones to use them as modems etc. We are still talking with 3com to try get them to allow us to include the firmware for their pccard in the driver but the driver is here.. In the mean time it can be downloaded from the 3com website and loaded using the utility bt3cfw(8) (supplied) (instructions in the man page) Not yet linked to the build Submitted by: Maksim Yevmenkin <myevmenk@exodus.net> Approved by: re
43 lines
966 B
Plaintext
43 lines
966 B
Plaintext
# $FreeBSD$
|
|
|
|
$Id: TODO,v 1.10 2002/09/06 21:03:57 max Exp $
|
|
|
|
FIXME/TODO list
|
|
|
|
This is a list of open issues for HCI node
|
|
|
|
1) Locking/SMP
|
|
|
|
External code now uses ng_send_fn to inject data into Netgraph, so
|
|
it should be fine as long as Netgraph is SMP safe. Just need to
|
|
verify it.
|
|
|
|
3) HCI QoS handling
|
|
|
|
Some code exists, but i have no idea how it should work. Will
|
|
understand and fix later. I only have CSR based hardware and
|
|
it does not support QoS.
|
|
|
|
4) Add proper handling for some HCI commands
|
|
|
|
HCI testing commands is one example. Also might implement Host to
|
|
Host Controller flow control (not sure if it is required).
|
|
|
|
5) Link security
|
|
|
|
Manage link keys and PINs. Options:
|
|
|
|
1) manage keys inside HCI node/unit itself
|
|
2) use user space daemon.
|
|
3) Mix option 1 and option 2.
|
|
|
|
6) Implement watchdog routine for HCI connections
|
|
|
|
Some code exists, but it is not used
|
|
|
|
7) Code cleanup
|
|
|
|
Verify return codes from functions
|
|
Remove some waringns/errors
|
|
|