Re: As long as we're adding to the Device Connected mgmt event...

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

 



Hi Mat,

> > I noticed your recent bluez.git commit that modifies the Device
> > Connected event.  Would it also make sense to add the results of the
> > READ_REMOTE_VERSION command?
> > 
> > lmp_ver
> > manufacturer
> > lmp_subver
> > 
> > This information was captured in bluetoothd when using hciops, but
> > has so far been missing with mgmtops.
> 
> Do you have a real use-case for it? It'd expect that info to be at most
> useful to the kernel side but not so much for user-space. FWIW, we came
> to the conclusion with Marcel that a better approach with this
> mgmt_ev_device_connected is to encode both the class and the name as an
> EIR blob. We'll also do that for the class that's currently as a
> separate parameter in mgmt_ev_device_found. This simplifies the
> structure of both events and also allows for future extensibility.

in addition, these information are purely debugging details and I think
it would be better to use sysfs or debugfs for it.

Regards

Marcel


--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux