dxdxdt/ModemManager - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2012-08-06	port-probe: no need to keep neither physdev path nor driver	Aleksander Morgado

2012-08-06	device: get vendor/product IDs	Aleksander Morgado
	And don't do it in MMPlugin.
2012-08-06	plugin: simplify interface by passing around the device and/or port objects	Aleksander Morgado

2012-08-06	device: keep a list of port probes instead of just ports	Aleksander Morgado

2012-08-06	device: signal grabbed/released ports	Aleksander Morgado

2012-08-06	device: load driver being used when first port grabbed	Aleksander Morgado

2012-08-06	device: keep sysfs path around for logging	Aleksander Morgado

2012-08-06	device: split `MMDevice' creation and plugin setting	Aleksander Morgado
	We want to be able to create the MMDevice way before we have decided which plugin to use.
2012-08-06	core: compile all ports before creating the modem object	Aleksander Morgado
	Before this, we only exported the modem to DBus when all ports were organized, in order to make sure that we select as primary port the one we really want and not the first AT port grabbed. Given that to get all the ports organized we also needed to wait to get all the ports grabbed, we can now also defer the creation of the modem object until all the ports get grabbed. This allows us to create different types of objects based on the ports available (e.g. we can now create QMI-supported modem objects if we see a QMI port around).