ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Mon, 26 Jun 2017 22:49:32 +0200	[thread overview]
Message-ID: <20170626204932.GA19396@amd> (raw)
In-Reply-To: <20170626134904.GH23064@atomide.com>

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

Hi!

> > > > > > On Sun, Jun 25 2017, Pavel Machek 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). Graphics acceleration is still
> > > > > > > missing.
> > > > > 
> > > > > Also droid 4 should be getting there eventually too with 3G data working
> > > > > and audio driver in progress.
> > > > 
> > > > Yes, good luck with Droid 4 getting there. 
> > > 
> > > Well actually it's sort of already there for some use cases as it's been
> > > usable for me for about a month as a low-power laptop/ssh terminal with
> > > Linux next and lapdock or hdmi dock :) Typing away with kernel
> > > 4.12.0-rc6-next-20170622 right now.
> > 
> > Do you have X running in useful configuration?
> 
> Yeah for most part I'm using X with HDMI, LCD works but there are six
> out of tree omapdrm patches that need more work similar to n950. Also
> the LCD backlight patch is also still pending.

HDMI is nice; that's a feature I'd like. And I guess you also have
real and working USB host?

Anyway I was interested... do you have useful X running on localhost?
I mean... finger is too big to control X applications, and you have
capacitive touchsreen, right?

> > > Personally I just stick to standard mainline kernel and standard
> > > distros so problem solved for me by limiting my use cases..
> > 
> > Well, I'm currently doing the same. On N900, I have X running (miss
> > right button on the touchscreen, and 800x480 is a bit small),
> > gprs/edge/umts data working, so I have usable ssh and web
> > browser. (But bufferbloat is ugly and reconnections are not handled
> > well). SMSes work. WIFI works (with exception of networkmanager). GPS
> > is usable. Camera is useful, including autofocus, but limited to
> > 1.2MPix. It lasts for a "day" which is good enough.
> 
> OK to get to that point droid 4 still needs audio calls, camera,
> and GPS at least. And PM needs more work. For reference, Sebastian
> Reichel has pretty good mainline driver status matrix for both n900
> and droid 4 on his website.

Well, camera is something I'm playing with, not a requirement. Can
live without GPS, but would prefer not to. But audio, audio is
mandatory :-).

Ah, thanks for the pointer. Built-in battery is very bad for
debugging, and very bad when PM is not quite finished. But I remember
droid4 was something that disqualified it for European use. Aha, LTE @
700MHz, which is not available here. Hmm, but GSM/UMTS works in v4.12
according to the table, so that's not too bad.

Does ofonod support the modems in an useful way?

Is GSM connected directly to the audio, or does it need real-time
task, similar to N900?

It looks like nice machine. OTOH N950 looks like a nice machine, too,
and N900 is actually nicer because of the resistive touch, battery,
and friendly bootloader...

> > Biggest problem I have now is poor quality of audio calls... Fixing
> > that would enable me to make it my primary phone...
> 
> That's with HSI modems, right?

Yes.

Best regards,
									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 --]

  reply	other threads:[~2017-06-26 20:49 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 [this message]
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
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=20170626204932.GA19396@amd \
    --to=pavel@ucw.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=sebastian.reichel@collabora.co.uk \
    --cc=tony@atomide.com \
    /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