mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Raphaël Poggi" <raphio98@gmail.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Adding minimal support for the UDOO board.
Date: Mon, 17 Feb 2014 20:34:20 +0100	[thread overview]
Message-ID: <CACqcpZBvYh-HpXuk=mwmo0L7rJRwFRfP8VMkqKgQKT0KWQ6k4A@mail.gmail.com> (raw)
In-Reply-To: <1392663269.195942469@f359.i.mail.ru>

Hum I think I have understand, in fact there is 2 differents type of
UDOO board, one quad and one dual. So I think it is a good idea to add
in imx6qdl-udoo.dtsi a compatible string like "udoo,imx6qdl"
and in the imx6q-udoo.dts a compatible string like "udoo,imx6q" is this right ?

Thanks.

Raphaël

2014-02-17 19:54 GMT+01:00 Alexander Shiyan <shc_work@mail.ru>:
> Hello.
>
> Понедельник, 17 февраля 2014, 19:34 +01:00 от Raphaël Poggi <raphio98@gmail.com>:
>>
>> Hi Alexander,
>>
>> I do not understand the problem with "compatible " :
>>
>> > > +#include "imx6qdl-udoo.dtsi"
>> > > +
>> > > +/ {
>> > > +       model = "Freescale i.MX6 Quad UDOO Board";
>> > > +       compatible = "fsl,imx6q-udoo", "fsl,imx6q";
>> > > +};
>> > > +
>>
>> Can you explain me ?
>
> Please answer the question: What describes imx6qdl-udoo.dtsi and
> what describes imx6q-udoo.dts ?
> I suspect for imx6qdl-udoo.dtsi is a module and imx6q-udoo.dts is a board
> uses this module.
> Kernel (as an our bootloader) may contain specific code used for the
> module and/or for a board. To find out should this code to be executed
> or not, some compatibility tests is used.
> So, you should add compatible string "AAA" to the module DT description
> and strings "BBB", "AAA" to the board.
> I hope I have explained clearly. :)
>
> Thanks.
> ---

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-02-17 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 22:20 Raphaël POGGI
2014-02-17  7:48 ` Sascha Hauer
2014-02-17  8:08   ` Alexander Shiyan
     [not found]     ` <CACqcpZDbp2r8z0R4AjEwwkGkJ4+aBi6LcKjBWKyaa-36N+NaCg@mail.gmail.com>
2014-02-17 18:54       ` Alexander Shiyan
2014-02-17 19:34         ` Raphaël Poggi [this message]
     [not found]   ` <CACqcpZDwF=weDsC-+jw97+V4Rw33xMLXUrt3OF0_1fM=d8vkLw@mail.gmail.com>
2014-02-17  8:25     ` 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='CACqcpZBvYh-HpXuk=mwmo0L7rJRwFRfP8VMkqKgQKT0KWQ6k4A@mail.gmail.com' \
    --to=raphio98@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=shc_work@mail.ru \
    /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