On Thu, Jun 30, 2011 at 12:01 PM, Li, Nami <nami@xxxxxxxxxxxxxxxx> wrote:
> Well, if the profile is OPP, then you can get correct service driver. But if the profile is FTP, because in ftp.c:
>
> static struct obex_service_driver ftp = {
> .name = "File Transfer server",
> .service = OBEX_FTP,
> .channel = FTP_CHANNEL,
> .psm = FTP_PSM,
> .record = FTP_RECORD,
> .target = FTP_TARGET,
> .target_size = TARGET_SIZE,
> .connect = ftp_connect,
> .get = ftp_get,
> .put = ftp_put,
> .chkput = ftp_chkput,
> .setpath = ftp_setpath,
> .disconnect = ftp_disconnect
> };
> It`s target is not null, target_size is 16, so " obex_service_driver_find(server->drivers, NULL,0, NULL, 0)" will return null.
>
> And I`m not picking up the first driver in the list, actually it is the only one in the list.
In case of other profiles, there is OBEX connect command required, and
then the appropriate driver will be selected in callback for OBEX
connect event (see cmd_connect()).
--
Slawomir Bochenski
--
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
