public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Swetland <swetland@google.com>
To: Anil S <anils@mistralsolutions.com>
Cc: 'Dirk Behme' <dirk.behme@googlemail.com>,
	linux-omap@vger.kernel.org, colorant@163.com
Subject: Re: Questions on Android
Date: Tue, 29 Apr 2008 03:13:51 -0700	[thread overview]
Message-ID: <20080429101351.GA25657@bulgaria.corp.google.com> (raw)
In-Reply-To: <200804290948.m3T9mLHt021830@smtp.google.com>

[Anil S <anils@mistralsolutions.com>]
> Hello Brian,
> 
> 	It would be really great if you could share thoughts on the
> questions given here on Android:
> 
> I was able to add support for the keypad, touch and network in Android,
> however the interfaces like GPS, Accelerometer, vibrator, hardware 3D
> acceleration, battery etc. are not integrated with Android right now. I
> would appreciate if you could throw some light on these open issues. How
> exactly can these interfaces be integrated with Android? 

We're trying to use the standard kernel/driver interfaces when possible,
but for things that may have a good deal of variation in implementation,
we're looking to provide a very thin "hardware interface library" layer
to adapt between the bottom of the userspace stack and the drivers or
whatnot for specific hardware platforms.  

We'll continue to adopt standardized kernel solutions as they become
available -- We're now using the power supply framework in 2.6.24 for
monitoring battery/charge state (post M5 SDK -- it'll be in the next 
release), for example.

Brian

  parent reply	other threads:[~2008-04-29 10:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6a56d69c0804241248w5e46efe8k757c9e5fb9e3ce22@mail.gmail.com>
2008-04-25  5:42 ` Android on N810 File System Problem Dirk Behme
2008-04-25 18:36   ` Felipe Balbi
2008-04-25 18:31     ` Igor Stoppa
2008-04-25 18:52       ` Felipe Balbi
2008-04-25 18:47         ` Igor Stoppa
2008-04-25 23:29           ` Felipe Balbi
2008-04-27  9:43     ` Kalle Valo
2008-04-27 22:32       ` Felipe Balbi
2008-04-27 23:04         ` Igor Stoppa
2008-04-28  6:24           ` Jarkko Nikula
2008-04-28 23:38         ` Tony Lindgren
2008-04-29  9:00           ` Brian Swetland
2008-04-30  9:49             ` Kalle Valo
2008-04-30 10:20               ` Brian Swetland
2008-04-30 10:46                 ` Felipe Balbi
2008-05-02  6:17                 ` Kalle Valo
2008-05-12 12:32             ` Dirk Behme
2008-04-29  9:49           ` Jarkko Nikula
2008-04-29 22:31             ` Jonathan Herriott
2008-04-30  1:04             ` Tony Lindgren
2008-04-30  9:45           ` Kalle Valo
2008-04-25 19:31   ` Jonathan Herriott
2008-04-25 23:35     ` Jonathan Herriott
2008-04-26  7:13     ` Dirk Behme
2008-04-27  2:21       ` Jonathan Herriott
2008-04-27  6:44         ` Dirk Behme
2008-04-27  8:13           ` Jonathan Herriott
2008-04-29  9:06         ` Brian Swetland
     [not found]           ` <200804290948.m3T9mLHt021830@smtp.google.com>
2008-04-29 10:13             ` Brian Swetland [this message]
2008-05-05 12:38               ` Questions on Android shivananda.hebbarp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080429101351.GA25657@bulgaria.corp.google.com \
    --to=swetland@google.com \
    --cc=anils@mistralsolutions.com \
    --cc=colorant@163.com \
    --cc=dirk.behme@googlemail.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox