ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Wed, 28 Jun 2017 18:25:03 +0200	[thread overview]
Message-ID: <20170628162502.GA23902@amd> (raw)
In-Reply-To: <CACRpkdYA6Tai+dAJ8Q2w_xEJonuDtHdUnTeJze_8JyX43KntPQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3093 bytes --]

Hi!

> just annoying you all with my thoughts on $SUBJECT.

:-).

> 
> On Sun, Jun 25, 2017 at 12:48 PM, Pavel Machek <pavel@ucw.cz> wrote:
> 
> > Situation around mobile phones is only improving very slowly. We now
> > have hardware that is supported in the mainline kernel in useful way
> > (Mitac Mio A701, Nokia N900, N9, N950).
> 
> I have been trying to get the Qualcomm original DragonBoard working
> with the mainline kernel. It is nice in this sense, because it has a
> mobile phone(-ish) form-factor.
> https://dflund.se/~triad/krad/dragonboard/
> 
> The problem I have in general, is that I got this development board
> at DesignWest in 2012, and already the Qualcomm people are sort of
> indicating to me that they consider the product so ancient that it
> is

The problem is called "Qualcomm". Other vendors actually care about
mainline and support their boards longer. (TI).

And yes, that means I'm running hardware from 2009. And yes, TI
probably regrets me getting that hardware :-).

> the case for Android devices. Having upstream drivers and using the
> kernel ABI as the hardware abstraction is the key to achieving that,
> and it's weird this is so hard for some to see. Google definitely have
> a role to play here.

Well, Android already has ABI abstraction layer, even projects like
Jolla and Ubuntu phone use it, IIRC, basically running Android in
chroot.

I agree that's not the way to go... but I don't think Google is going
to help us here. Community will have to do it "itself", and then maybe
Google + hw vendors will join.

> > Plus of course, there's a lot of work to be done to get different
> > phones supported.
> 
> I'd be happy if I could "just" compile and boot the latest kernel with
> the latest AOSP (Android Open Source Project) on the Nokia n900 or
> n950 and use it as a smartphone. I would even accept an out-of-tree
> GPU driver since everything and its dog requires 3D acceleration these
> days. Maybe it would nit even drain the battery in 5 minutes and that
> would be GREAT.
> 
> As far as I know we not even close to anything like that. Or are there
> people actually booting Android on these? Or any other phone form-factor
> device running a mainline Linux+Android?

Well, people are running N900 + old Android. And there are maintained
patches to keep original Maemo running on recent kernels (Pali Rohar
has them). I will _not_ touch Android, not with 10 foot pole, but
latest AOSP on N900 should be doable for someone with Android
experience and some free time..

> (Insert compulsory do-not-assume-Android, this other $MOBILE_OS
> with 0.001% market share is so much more interesting-rant here.
> I am talking about what mobile users realistically expects to be able
> to run.)

How does Debian sound? Because that's what I run on N900. And most of
the stuff works, with voice calls being too poor quality...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2017-06-28 16:25 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 10:48 Pavel Machek
2017-06-25 23:55 ` NeilBrown
2017-06-26  6:43   ` Geert Uytterhoeven
2017-06-26  6:49   ` Tony Lindgren
2017-06-26 11:12     ` Pavel Machek
2017-06-26 11:49       ` Tony Lindgren
2017-06-26 13:14         ` Pavel Machek
2017-06-26 13:49           ` Tony Lindgren
2017-06-26 20:49             ` Pavel Machek
2017-06-27  7:18               ` Tony Lindgren
2017-06-27 12:14                 ` Sebastian Reichel
2017-06-27 21:57                   ` Pavel Machek
2017-06-28 16:01                     ` Sebastian Reichel
2017-06-28 20:27                       ` Pavel Machek
2017-07-02 12:03                         ` Sebastian Reichel
2017-06-27 21:57                 ` Pavel Machek
2017-06-26  8:34   ` Pavel Machek
2017-06-26 11:20     ` Mark Brown
2017-06-26 12:22       ` Pavel Machek
2017-06-27 11:40         ` Mark Brown
2017-06-28 18:37           ` Pavel Machek
2017-07-02 12:11             ` Sebastian Reichel
2017-06-26 22:23     ` Alexandre Belloni
2017-06-27  7:06       ` Pavel Machek
2017-06-27 12:39     ` Sebastian Reichel
2017-06-27 21:57       ` Pavel Machek
2017-06-28 16:45         ` Sebastian Reichel
2017-06-28 21:10           ` Pavel Machek
2017-07-02 11:28             ` Sebastian Reichel
2017-07-02 18:14               ` Pavel Machek
2017-06-26 10:54 ` Mark Brown
2017-06-26 11:14   ` Pavel Machek
2017-06-26 11:49     ` Mark Brown
2017-06-26 12:38       ` Pavel Machek
2017-06-26 16:34         ` Mark Brown
2017-06-27 11:41   ` Sebastian Reichel
2017-06-28 14:38 ` Linus Walleij
2017-06-28 15:58   ` Arnd Bergmann
2017-06-28 16:04     ` Laurent Pinchart
2017-06-28 16:25   ` Pavel Machek [this message]
2017-06-28 18:26     ` Mark Brown
2017-06-28 17:01   ` Pavel Machek
2017-06-28 19:03     ` Tony Lindgren

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=20170628162502.GA23902@amd \
    --to=pavel@ucw.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linus.walleij@linaro.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