public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 0/5] ARM: SoC: changes for v5.9
Date: Wed, 5 Aug 2020 19:27:46 +0200	[thread overview]
Message-ID: <20200805172746.GC1118@bug> (raw)
In-Reply-To: <CAK8P3a1vFJ+uUGPGifZGhECXvxA=2u745WrGNZb08s1nHkZQ9g@mail.gmail.com>

Hi!

> 2. In the past few merge windows we have seen an increase in (usually
>    older) Android phones and tablets gaining mainline kernel support.
>    This time we get a total of eight Snapdragon phones and two Tegra
>    tablets. To me this indicates that we finally have sufficient driver
>    support, in particular on the GPU side, to make this workable.
>    It also shows the impact that a single hobbyist developer can have,
>    as most of the new support was submitted by Konrad Dybcio who only
>    started contributing kernel patches to mainline Linux for postmarketos
>    earlier this year.

I'm happy to see that. So far, Nokia N900 is reaonably supported (basically everything
but Bluetooth works, voicecalls miss userland daemon for audio), and Motorola
Droid 4 (modem needs some more in kernel, camera will be hard).

Is there anything with similar support coming in, or is it usual "it boots,
serial console works"?

Should we have some kind of linux-phones mailing list? There is quite a lot of
stuff common in phones.

Best regards,
									Pavel


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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-08-05 17:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 21:34 [GIT PULL 0/5] ARM: SoC: changes for v5.9 Arnd Bergmann
2020-08-03 21:36 ` [GIT PULL 1/5] ARM: defconfig updates " Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-03 21:44 ` [GIT PULL 2/5] ARM: SoC: DT changes " Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-03 21:47 ` [GIT PULL 3/5] ARM: SoC " Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-04  7:02   ` Joel Stanley
2020-08-04  7:33     ` Andy Shevchenko
2020-08-04  7:39       ` Andy Shevchenko
2020-08-04  7:55       ` Linus Walleij
2020-08-04 18:38     ` Linus Torvalds
2020-08-03 21:49 ` [GIT PULL 4/5] ARM: SoC driver updates " Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-03 21:50 ` [GIT PULL 5/5] ARM: new SoC support " Arnd Bergmann
2020-08-04  2:45   ` pr-tracker-bot
2020-08-05 17:27 ` Pavel Machek [this message]
2020-08-05 19:06   ` [GIT PULL 0/5] ARM: SoC: changes " Arnd Bergmann
2020-08-05 19:28     ` Konrad Dybcio
2020-08-05 19:45       ` Pavel Machek
2020-08-05 19:58         ` Konrad Dybcio
2020-08-05 22:12           ` Konrad Dybcio
2020-08-05 19:32     ` Pavel Machek

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=20200805172746.GC1118@bug \
    --to=pavel@ucw.cz \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=torvalds@linux-foundation.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