installing n_hci upon DEVUP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I am faced with a problem, where-in my transport is UART and the hci0 interface from my driver (a TTY line discipline driver) is exposed @ boot time.

On Bluetooth-On, I perform a dev-up (or run bluetoothd/hcid which does that), how do I set the initialize my transport @ this point ?

I so desperately don't want to use hciattach, and want to allow my line discipline driver to do the firmware download (the reason why i have johan in CC) like the hci_h4p.

However, I would like to maintain my driver as a line discipline to avoid making use of primitive UART calls [like the hci_h4p].
Want to make use of DMA enabled, PM featured UART if available.

regards,
Pavan


      The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux