gnokii-users
[Top][All Lists]
Advanced

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

Re: Device or resource busy


From: Daniele Forsi
Subject: Re: Device or resource busy
Date: Mon, 16 Dec 2013 12:52:09 +0100

2013/12/15 Denis Khabarov:

> When smsd is running, I can
> not use any command gnokii:

yes, that's by design; this is the meaning of the message "Couldn't
open PHONET device: Device or resource busy"

while it would be possible to use the GSM mulltiplexer, nowadays it's
not worth it because many phones implement more than one communication
endpoint (even if some are less capable that others or buggy or
weird), with Nokia phones you can use at the same time /dev/ttyACM0
and the FBUS channel, with non-Nokia phones you can use /dev/ttyACM0
and /dev/ttyACM1, however that's untested with libgnokii

> port = /dev/ttyACM0
> connection = dku2libusb

that isn't a valid configuration, that's the meaning of this message:
> port = /dev/ttyACM0 is not valid for connection = dku2libusb using port = 1
> instead

you can see if the following works for you and please report your
results to this mailing list for the benefit of others

in your /etc/gnokiirc add two sections:
[phone_1]
connection = serial
port = /dev/ttyACM0
model = AT

[phone_2]
connection = dku2libusb
port = 1
model = series40

then you run:
smsd --phone 1
and:
gnokii --phone 2 --identify

and see if it works as you expect, then switch 1 and 2 and try if it's
better or worse

Note that it should be possible to establish more than one connection
to the same Nokia phone when using connection = phonet however that
protocol lacks any documentation useful to me and the kernel module
lacks useful comments and in the end our dku2libusb is much bettter
and would allow to do the same if I knew how, if somebody wants to
study this matter, he can look at the sources of the Linux kernel:
drivers/net/usb/cdc-phonet.c
drivers/usb/gadget/f_phonet.c
net/phonet/af_phonet.c

> PS. Sorry for bad english.

don't worry, your English is good

-- 
Daniele Forsi



reply via email to

[Prev in Thread] Current Thread [Next in Thread]