[prev in list] [next in list] [prev in thread] [next in thread] 

List:       moblin-dev
Subject:    Re: [Moblin Dev] What sensors you lilke?
From:       "Zhang, Xing Z" <xing.z.zhang () intel ! com>
Date:       2009-12-31 5:43:22
Message-ID: 8B81FACE836F9248894A7844CC0BA8140E6AD27F5B () shzsmsx501 ! ccr ! corp ! intel ! com
[Download RAW message or body]



Zhang Xin(Wing)
Intel(SSG/OTC) ShangHai China 

>-----Original Message-----
>From: Greg KH [mailto:gregkh@suse.de]
>Sent: 2009Äê12Ô 31ÈÕ 13:20
>To: Zhang, Xing Z
>Cc: dev@moblin.org
>Subject: Re: [Moblin Dev] What sensors you lilke?
>
>On Thu, Dec 31, 2009 at 01:02:22PM +0800, Zhang, Xing Z wrote:
>> >
>> >On Wed, Dec 30, 2009 at 05:04:13PM +0800, Zhang, Xing Z wrote:
>> >> Hi developers:
>> >> 	I'd like to buy some external sensors(external means they can be
>> >> connected to my machine through USB cable) for reference. Basically, I
>> >will
>> >> order some phidgets' sensors like vibrator, precision light sensor ...
>> >> 	These sensors will be supported in sensor framework in further.  I
>> >> wonder what sensors you are interested in, pls recommend your favor. I
>> >will
>> >> consider supporting them in sensor framework.
>> >> 	Please note only USB connecting sensors are candidates. If you have
>> >> some specific sensors embedded in your platform, feel free to send me
>a
>> >> patch enables it in sensor framework. Thanks.
>> >
>> >Phidget devices are already supported just fine on Linux with their
>> >userspace libusb-based library, so no new work needs to be done here at
>> >all.
>> >
>> >hope this helps,
>>
>> Thanks for pointing out:) Sensor Framework provides identical API
>interfaces
>> for Moblin(definitely for Linux) with hiding hardware details. We are a
>> pluggable system, so applications need not care vendor of sensor they are
>> accessing, plugins of framework talk to sensor driver or sensor library
>and
>> push data to applications thru API of framework.
>>
>> Phidget's userspace library is well organized, leveraging it I have
>> supported its USB accelerometer in sensor framework. Meanwhile I found
>> phidget only allows application exclusively accesses device while sensor
>> framework provides multi-access capability.
>>
>> I hope my framework could support more and more sensors from different
>> vendors, then developers could focus on application itself without
>learning
>> various driver interfaces or libraries.
>>
>> Below are homepage of sensor framework and its API reference. We are
>still
>> in developing, comments and patches are always welcome.
>>
>> http://moblin.org/projects/sensor-framework
>>
>> http://moblin.org/sites/all/files/moblin2.1api/html/sensor/index.html
>
>So, is this going to try to unify _all_ Linux sensor frameworks?  

Actually we focus on sensors improve exciting user experience, such
as accelerometer, compass, gyro ... they are mainly used in mobile platform.
These system management sensors like thermal, fan sensor will not be covered. 


>you going to support the in-kernel sensor and comedi framework as well?

Oh, this is a good suggestion. I should support sensor who has already put
its drivers in kernel. And I will also go thru hardware list of comedi to
see proper candidates.


>If so, I would suggest starting to do those two first, and then good
>luck on sucking in everything else, there is a _very_ large body of
>different frameworks out there.

I will limit myself to several widely used sensors first, not tend to 
suck in everything:) Hope this could save much effort. Sensor Framework
doesn't intend to replace other frameworks, I just hope people will
choose sensor framework when he wants to bring fashion user experience in
his application by a sensor.

Thanks.

>
>greg k-h
_______________________________________________
Moblin dev Mailing List
dev@moblin.org

To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

[prev in list] [next in list] [prev in thread] [next in thread]