Hi Marcel, >> Ok, so I'll wait to continue my implementation of the DUN client. I >> don't know the oFono internal too much to help on that decision. > > I was talking about the server and not the client. For the client we > have to have a chat about it. I might have missed parts of the initial > discussion. >
As we discussed before, the client needs settings strings to send to the modem. E.g. AT+CGDCONT=foobar; ATD*99***1. oFono atoms are not setup to do this. >>> Also there is no need to create a static library for doing this. That is >>> just wrong. We can do the build magic with autofoo properly and without >>> having to use a hack with a static library. >> >> I meant build statically here like gatchat, without any hack with static >> library. ;) > > Actually gatchat is not build statically. It is build as part of out AT > modem driver. That it is in separate directory is purely cosmetic. > GAtChat will end up used by the core for the ppp integration. I argued that bluetooth should follow the same semantic, since it will be used by both dun client daemon and oFono hfp/sap plugins. Regards, -Denis _______________________________________________ ofono mailing list [email protected] http://lists.ofono.org/listinfo/ofono
