Re: Getting the socket number from within the driver

Hi Dave,

> The socket number is not provided to the driver.  Why do you think
> that information would be useful?  The numbering of sockets is very
> arbitrary.

I have the 3Com Bluetooth card and this card needs a firmware download.
This download must be done before we can register this device to the
BlueZ HCI layer. As I can't distribute the firmware within the driver
for legal reasons it should be loaded trough a user space program on
card init. I want to call this program as a kernel thread and only give
the socket as a parameter. The user program reads the iobase and the
manfid from the socket and performs the firmware download. With the
completation of the user program the device is fully initialized and can
be registered to the HCI layer. I don't want to have a firmware loader
that I have to call with the iobase. Are there any other possibilities
to solve my problem?

Regards

Marcel