All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	jimwall@q.com, brian@crystalfontz.com
Subject: Re: [meta-fsl-arm-extra][PATCH 3/8] Add a machine configuration for cfa-10037
Date: Fri, 06 Sep 2013 19:11:03 +0200	[thread overview]
Message-ID: <522A0CA7.1010901@free-electrons.com> (raw)
In-Reply-To: <CAP9ODKrN0yHB6Kg_tN=USVE9gQ0X8ZpCGVv2rg35ROnJ9jeD8w@mail.gmail.com>

On 06/09/2013 18:40, Otavio Salvador wrote:
> On Fri, Sep 6, 2013 at 1:34 PM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> On 06/09/2013 14:10, Otavio Salvador wrote:
>>> On Fri, Sep 6, 2013 at 8:59 AM, Daiane Angolini
>>> <daiane.angolini@freescale.com> wrote:
>>>> On 09/05/2013 06:21 PM, Alexandre Belloni wrote:
>>>>> The cfa-10037 is a breakout board for the cfa-10036.
>>>>>
>>>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>>>> ---
>>>>>   conf/machine/cfa10037.conf | 9 +++++++++
>>>>>   1 file changed, 9 insertions(+)
>>>>>   create mode 100644 conf/machine/cfa10037.conf
>>>>>
>>>>> diff --git a/conf/machine/cfa10037.conf b/conf/machine/cfa10037.conf
>>>>> new file mode 100644
>>>>> index 0000000..7dbdd55
>>>>> --- /dev/null
>>>>> +++ b/conf/machine/cfa10037.conf
>>>>> @@ -0,0 +1,9 @@
>>>>> +#@TYPE: Machine
>>>>> +#@NAME: Crystalfontz CFA-10037
>>>>> +#@SOC: i.MX28
>>>>> +#@DESCRIPTION: Machine configuration for CFA-10037
>>>>> +
>>>>> +include conf/machine/include/cfa10036.inc
>>>>> +
>>>>> +KERNEL_DEVICETREE += "imx28-cfa10037.dtb"
>>>> oh, you need both devicetree files....
>>> Really? I think it is not loading both. Alexandre, can you comment on this?
>>>
>> Sure, you are right, it is only loading one. But in the case the eeprom
>> is not yet written, you may end up with barebox trying to use the
>> cfa-10036 DT. Hence, I'm letting that DT so that you can still boot. You
>> may also detach the cfa-10036 from the peripheral board and so end up
>> booting only on the cfa-10036.
>>
>> I did the same for cfa-10055 and cfa-10056 which are actually cfa-10037
>> with an attached touchscreen. If you ever want to remove it, you
>> probably want to still be able to boot it.
>>
>> Actually, I was wondering whether it wouldn't be better to simply always
>> include all the DTs.
> Personally I disagree with this approach. We are not working with PC
> so people are expected to know what they're doing and choose the right
> board.
>
> I will let you to decide on this as I am clueless about the boards and
> you're the maintainer of these. So in the end it is your call.
>

I personnally don't mind removing the cfa-10037 from the cfa-10055 and
cfa-10056 but I would prefer keeping the cfa-10036 DT for all the board,
as explained, you may end up with a board with an empty eeprom and still
want to boot (for example, to flash that eeprom ;) ).

Also, I believe those boards may end up being used by unexperienced
people (think raspberry pi ;) ) or by people wanting to use the same SD
card on multiple different boards or event moving the cfa-10036+sdcard
to another peripheral board.

Just to be clear enough, the cfa-10036 is a SoM including the imx28,
RAM, sdcard and usb with a 200 pin SO-DIMM connector. You can then host
that SoM on different peripheral boards. See:
http://www.crystalfontz.com/products/index-linux-SOM.html

I can send a v2 with the extre cfa-10037 dt removed.

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



  reply	other threads:[~2013-09-06 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 21:21 [meta-fsl-arm-extra][PATCH 0/8] Split crystalfontz boards Alexandre Belloni
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 1/8] linux-cfa: always use cfa10036 as MACHINE for the kernel link Alexandre Belloni
2013-09-06 11:55   ` Daiane Angolini
2013-09-06 12:39     ` Alexandre Belloni
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 2/8] cfa10036: split configuration Alexandre Belloni
2013-09-06 11:57   ` Daiane Angolini
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 3/8] Add a machine configuration for cfa-10037 Alexandre Belloni
2013-09-06 11:59   ` Daiane Angolini
2013-09-06 12:10     ` Otavio Salvador
2013-09-06 16:34       ` Alexandre Belloni
2013-09-06 16:40         ` Otavio Salvador
2013-09-06 17:11           ` Alexandre Belloni [this message]
2013-09-06 18:12             ` Otavio Salvador
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 4/8] Add a machine configuration for cfa-10049 Alexandre Belloni
2013-09-05 21:21 ` [meta-fsl-arm-extra][PATCH 5/8] Add a machine configuration for cfa-10055 Alexandre Belloni
2013-09-05 21:22 ` [meta-fsl-arm-extra][PATCH 6/8] Add a machine configuration for cfa-10056 Alexandre Belloni
2013-09-05 21:22 ` [meta-fsl-arm-extra][PATCH 7/8] Add a machine configuration for cfa-10057 Alexandre Belloni
2013-09-05 21:22 ` [meta-fsl-arm-extra][PATCH 8/8] Add a machine configuration for cfa-10058 Alexandre Belloni

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=522A0CA7.1010901@free-electrons.com \
    --to=alexandre.belloni@free-electrons.com \
    --cc=brian@crystalfontz.com \
    --cc=jimwall@q.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.