linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM i.MX51: Add Efika MX Smartbook devicetree
Date: Wed, 16 Apr 2014 14:23:23 +0200	[thread overview]
Message-ID: <87ppkho43o.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <1397650038.299778344@f431.i.mail.ru> (Alexander Shiyan's message of "Wed, 16 Apr 2014 16:07:18 +0400")

Alexander Shiyan <shc_work@mail.ru> writes:

> Wed, 16 Apr 2014 13:19:40 +0200 ?? Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>:
>> Alexander Shiyan <shc_work@mail.ru> writes:
>> 
>> > This patch adds support for Efika MX Smartbook.
>> 
>> I'm curious, how did you test that ? From a very quick look,
>> seems it has no chance to work with the uboot shipped with the devices.
>
> Uboot it is not the only option for booting.
> With any loader, this can be used with "appended DTB" option in the kernel.
>
> This board support was be introduced by Sascha Hauer for the "barebox".
> So I think he was checking its workability.

As I said, I'm talking of the uboot shipped with the devices. I do know
that barebox is doing things differently than this uboot. For
instance, with this DTB and barebox, usb should(?) work but for sure, it
won't work with this uboot.
If we merge something, it should work with all bootloaders otherwise it
would mean that the dtb is bootloader specific...

Arnaud

  reply	other threads:[~2014-04-16 12:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  9:41 [PATCH] ARM i.MX51: Add Efika MX Smartbook devicetree Alexander Shiyan
2014-04-16 11:19 ` Arnaud Patard (Rtp)
2014-04-16 12:07   ` Alexander Shiyan
2014-04-16 12:23     ` Arnaud Patard (Rtp) [this message]
2014-04-18  4:41       ` Alexander Shiyan
2014-05-08  6:26 ` Sascha Hauer
2014-05-09  3:11   ` Fabio Estevam
2014-05-09  6:18     ` Sascha Hauer

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=87ppkho43o.fsf@lebrac.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).