Hi List, Im trying to put an end to this problem of detecting rfcomm port properly, so what seems to be missing is to associate the profile to the port so that udev can properly announce it as modem in case of dun profile. I don't know of any mechanism to attach any profile information to the port itself, but in theory we could identify the port by name, so instead of using rfcomm# for all ports created by Serial interface we could name it dun# for instance, so how about that? Also we probably want to make this persistent so once this is configured this will be restored in the next boot. -- Luiz Augusto von Dentz Engenheiro de Computação -- 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
