public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: christo.radev@gmail.com
Cc: linux-sunxi <linux-sunxi@googlegroups.com>,
	wens@csie.org, tsvetan@olimex.com, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	linux@arm.linux.org.uk, hdegoede@redhat.com, dev@linux-sunxi.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, oliver@schinagl.nl
Subject: Re: [PATCH 1/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc
Date: Tue, 3 May 2016 15:14:37 +0200	[thread overview]
Message-ID: <20160503131437.GV17159@lukather> (raw)
In-Reply-To: <f3da30a6-9ac0-4d5e-8611-ebb80cb3589e@googlegroups.com>

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

Hi,

On Tue, May 03, 2016 at 12:12:06AM -0700, christo.radev@gmail.com wrote:
> Hi to All,
> 
> I have already solved and tested this issue on Armbian build.  Find
> patches for both legacy (3.4.111) and mainline (4.5.2) kernels on:
> http://forum.armbian.com/index.php/topic/853-armbian-customization/page-2#entry7494
> There it is also described how to do eMMC bootable and much more.
> 
> About the board - Olimex already sold all 3 kinds after migration to
> their HW rev. E. One have to specify Lime2-eMMC as
> A20-Olinuxino-Lime2-eMMC instead of their old 2 options
> A20-Olinuxino-Lime2(-4GB).

Interesting, you have a link to that device?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-03 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  7:19 [PATCH 1/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc Olliver Schinagl
2016-05-02 10:55 ` Maxime Ripard
2016-05-03  3:33 ` Chen-Yu Tsai
2016-05-03  7:21   ` Olliver Schinagl
2016-05-03  7:25     ` Chen-Yu Tsai
2016-05-04 12:30       ` Radoslav Kolev
2016-05-04 12:52         ` Olliver Schinagl
     [not found]           ` <948be370-4401-43cb-862e-d4376755a75d@googlegroups.com>
     [not found]             ` <5729F6D6.8030100@schinagl.nl>
     [not found]               ` <4704fa35-9a2a-4e6e-8fd4-f4778405c598@googlegroups.com>
     [not found]                 ` <572A0052.9060202@schinagl.nl>
     [not found]                   ` <2e745ef7-ddc0-40fc-b867-414543690276@googlegroups.com>
     [not found]                     ` <572A10B3.2020803@schinagl.nl>
     [not found]                       ` <4375220a-f939-4ed0-a6d7-2cf887b07509@googlegroups.com>
     [not found]                         ` <9fe7ebb6-6d74-4b73-b6d6-93b79650cdb6@googlegroups.com>
     [not found]                           ` <9745a80b-5444-43f7-b772-68684c96c9e5@googlegroups.com>
     [not found]                             ` <57322C8D.5060806@schinagl.nl>
     [not found]                               ` <8afbe753-4e74-4b30-ad7e-a12027d28264@googlegroups.com>
     [not found]                                 ` <57323CAB.7090202@schinagl.nl>
     [not found]                                   ` <f959ee5c-fa63-48f6-9819-4822c055b928@googlegroups.com>
     [not found]                                     ` <6bfa242e-c0ce-4dc5-9144-b3f16d8fb75c@googlegroups.com>
     [not found]                                       ` <5732EB34.6070203@schinagl.nl>
2016-07-15  8:39                                         ` stefan.mavrodiev
2016-07-15  8:57                                           ` Olliver Schinagl
2016-05-03  7:12 ` christo.radev
2016-05-03 13:14   ` Maxime Ripard [this message]
2016-05-03 15:02     ` christo.radev
2016-05-03 15:52       ` Olliver Schinagl
2016-05-04  5:13         ` [linux-sunxi] " Priit Laes

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=20160503131437.GV17159@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=christo.radev@gmail.com \
    --cc=dev@linux-sunxi.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=hdegoede@redhat.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=oliver@schinagl.nl \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tsvetan@olimex.com \
    --cc=wens@csie.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