ok bit more of information .... We don;t use the hciattach, instead we have our own daemon which opens up the UART and installs the line discipline (not N_HCI, but similar one called N_SHARED) when the hciconfig hci0 up happens or even when /dev/radio0 (FM V4L2 device) happens or when generic GPS character device (/dev/tigps) happens... There is non-mailine driver which gets modified to get into mainline @ http://git.omapzoom.org/?p=kernel/omap.git;a=tree;f=drivers/misc/ti-st;h=028ff4a739d7b59b94d0c613b5ef510ff338b65d;hb=refs/heads/p-android-omap-2.6.32 feel free to have a look at it... Yes our solution too works with BlueZ and non-exactly a MFD driver but it is a simple platform device driver .. by looks of things the driver can run as is for your chip too .. (except for the firmware search and download part .. may be...). and note when we would want to support SPI transport for the same, we plan a SPI-TTY driver ('ala usb-serial) where-in we can install this N_TI_WL line discipline on that /dev/ttySPI0 device, and the SPI related stuff to be handled by the spi-tty.c which registers itself as a tty_device and a tty_driver .... regards, Pavan On Fri, Sep 10, 2010 at 2:07 PM, Pavan Savoy <pavan_savoy@xxxxxxxx> wrote: > Can you directly make use of the ti-st driver which is currently staged? > It has _EXACTLY_ the same thing.... which is REALLY REALLY surprising !!! > > On Fri, Sep 10, 2010 at 8:38 AM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: >>> - Is it OK to dynamically use the channels either from Kernel or User space? >> >> Quite a few devices do this. In most cases it makes no sense to burden >> the user with channel management so its only natural that opening the tty >> or direct interfaces should "just work" >> -- >> 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 >> > -- 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
