> ldisc is the ONLY way to do it, isn't it? Do I have any other option? Userspace but even then it wouldn't solve your problem > The situation was something similar here. > What I was trying to get to is how we can have a per-device context if a driver is just a line discipline driver? tty->driver_data TTY private data tty->disc_data LDISC per instance private data So when your ldisc is opened attach your data to the tty->disc_data, and when it is closed free the data. > I have 3 sub-devices if you will on a device which is interfaced over UART, > One of them is Bluetooth which requires any UART Bluetooth device to have its > Own line discipline - N_HCI. The problem is that your chip by the sound of it does not talk the bluetooth ldisc - it talks something more complex. The obvious question then is Does it talk 1. HCI with bits nailed on 2. Something rather different which contains muxed data some of which is reformatted up to create HCI In the first case it may be worth seeing if the existing N_HCI could support forwarding unknown frame types to a helper. In the latter it's a lot trickier. It is possible to create a mux tty layer (see n_gsm.c) but that is almost certainly overkill for this. I wonder what Marcel thinks in terms of re-using the bluetooth ldisc ? _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
