RE: ioctl(RFCOMMCREATEDEV) failed: File descriptor in bad state

[Marcel Holtmann <marcel@holtmann.org>]

Hi,

> >> I am calling ioctl(RFCOMMCREATEDEV) to create tty device from a
> >> rfcomm fd using hands-free profile. If the HF send connection
> >> request to AG and make rfcomm connect, the tty could be made
> >> successfully. However, if the AG(mobile) side make request to create
> >> rfcomm connection, the rfcomm could be created but fail to create
> >> the tty device. The kernel returns error because socket is not
> >> connected, see below code. Any idea? Thanks much! 
> > 
> > why do you wanna create the TTY in the first place? Going via the TTY
> > layer is pretty bad idea. Don't even think about doing that. Use the
> > RFCOMM socket.
>
> I want to create TTY and expose it to Ofono as /dev/rfcomm0. Ofono side 
> could treat bluetooth connection as a TTY device, and create 
> GAtChat *chat by using g_at_chat_new_from_tty(tty, syntax).

and that is just wrong to begin with. Write an oFono plugin that uses
Bluetooth RFCOMM sockets directly. I really don't understand why you
wanna make your life so complicated. Within oFono you have to do a
non-blocking RFCOMM connect() anyway using GIOChannel. And once you have
the GIOChannel you can just hand it to g_at_chat_new(). Plain and
simple. Just extend modemconf.c to support a "bluetooth" driver and then
you can even configure address and channel.

Regards

Marcel