mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Daniel Laube <mail@dlaube.de>
Cc: Maxime Jourdan <mjourdan@baylibre.com>,
	linux-amlogic@lists.infradead.org,
	Kevin Hilman <khilman@baylibre.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Marc Gonzalez <marc.w.gonzalez@free.fr>
Subject: Re: Help offering for AmLogic S905Y2 Mainline Effort
Date: Mon, 24 Jun 2019 10:55:56 +0200	[thread overview]
Message-ID: <cdd4111c-16d7-adce-d7f7-4c3ee77d2a43@baylibre.com> (raw)
In-Reply-To: <2543a892-d7b6-f528-4df3-923edbf1dd85@free.fr>

Hi Daniel,

DRM Display support for the S905Y2 will be available in Linux v5.2,
but necessary devices (mmc, sdcard, sdio, ethernet) will land in Linux v5.3-rc1
in allmost 4weeks, but you can check the integ tree to test these features as
described on http://linux-meson.com/doku.php#development_resources :
https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/log/?h=v5.3/integ

Video decoder support for S905Y2 is in the work, bit we mainly focused to have
the bare minimum driver being merged for S905/S905X/S912 before pushing more
complex decoder and new SoCs support :
https://github.com/Elyotna/linux/tree/mjourdan/media/v5.2/aml/vdec

BTW, you are very welcome !

As Chen-Yu Tsai said, we idle on #linux-amlogic IRC channel on freenode and
activaly use the linux-amlogic@lists.infradead.org ML.

You can also join the u-boot-amlogic@groups.io ML if you are interested in
mainline U-Boot dev for amlogic SoCs.

Neil

On 24/06/2019 10:36, Marc Gonzalez wrote:
> On 23/06/2019 22:42, Daniel Laube wrote:
> 
>> recently bought a cheap HDMI Stick Computer with an AmLogic Chip (S905Y2 on x96s Board) 
>> because i was told that it had mainline linux support. That seems to be 
>> true only partly because there are drm drivers missing for the gpu and 
>> no video encoding/decoding support.
>> Because i would like to get these things working in the future i would 
>> like to offer my help.
>> I already ripped that thing open to get access to UART to see boot progress.
>> Could someone please guide me where i can help with the mainlining effort?
> 
> I suppose the first thing to do is try to get in touch with whomever
> might be working on this at the moment or in the (recent) past.
> 
> Look at the MAINTAINERS file, to find "official" maintainers and reviewers.
> 
> The baylibre team seems to be handling some of the mainlining effort,
> so perhaps they are in a good position to provide relevant information.
> 
> There's also a specific mailing list: linux-amlogic@lists.infradead.org
> 
> Regards.
> 


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

      parent reply	other threads:[~2019-06-24  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0292EC91-0CBE-4F22-8F28-BD581A157CD6@dlaube.de>
2019-06-24  8:36 ` Marc Gonzalez
2019-06-24  8:46   ` Chen-Yu Tsai
2019-06-24  8:55   ` Neil Armstrong [this message]

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=cdd4111c-16d7-adce-d7f7-4c3ee77d2a43@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mail@dlaube.de \
    --cc=marc.w.gonzalez@free.fr \
    --cc=mjourdan@baylibre.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

all inboxes | Powered by JetHome®