All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexandre.belloni@bootlin.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: Atmel AT91 support in mainstream kernel 4.4
Date: Wed, 29 Aug 2018 15:34:10 +0200	[thread overview]
Message-ID: <20180829133410.GE16561@piout.net> (raw)
In-Reply-To: <20180821123047.GB3159@1wt.eu>

Hi,

On 21/08/2018 14:30:47+0200, Willy Tarreau wrote:
> Hi,
> 
> On Tue, Aug 21, 2018 at 02:10:14PM +0200, Fernando AE wrote:
> > Hello all,
> > 
> > I'd like to know if AT91 boards (more specifically AT91SAM9G20) is
> > well supported in mainstream Kernel 4.4.
> > 
> > In more details, I'm working in a project of bringing up Linux 4.4 in
> > a iMX6 based board, while trying to keep the same sources for our
> > legacy AT91 based board. So, I'm wondering if it's a good idea to take
> > Freescale's repo based on 4.4 as reference and compiling both for iMX
> > and AT91.
> 
> FWIW I remember having been running an AT91 board (linuxstamp 2) on
> 2.6.35 with a single patch by then, the one needed to create the board.
> Everything else used to work out of the box. I don't see why anything
> would have regressed since then without anyone complaining loud, so I'd
> be inclined to think it's well supported.
> 

I confirm we don't have any out of tree patch for the at91sam9g20 so you
will get the best support there is using a mainline kernel.

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-29 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 12:10 Atmel AT91 support in mainstream kernel 4.4 Fernando AE
2018-08-21 12:26 ` Fabio Estevam
2018-08-21 12:30 ` Willy Tarreau
2018-08-29 13:34   ` Alexandre Belloni [this message]
2018-08-22  8:15 ` Alexander Dahl

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=20180829133410.GE16561@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.