All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Steve Pavao <stevep@korgrd.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi] Compute Module 3 machine .conf questions
Date: Tue, 1 May 2018 14:39:03 +0100	[thread overview]
Message-ID: <CAK18fxEEQ3BGKqeTciFkvzUbsyFNzkHBuz+drQ5j78OuqmZi7g@mail.gmail.com> (raw)
In-Reply-To: <05108809-5601-43F4-B1D3-5F2B8D675EFC@korgrd.com>

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

Hi Steve,

On Tue, May 1, 2018 at 12:40 AM, Steve Pavao <stevep@korgrd.com> wrote:

> Hello,
>
> My company has bought a Raspberry Pi Compute Module 3 for evaluation, and
> I have a 2 questions about the supplied machine .conf files for it.
>
> 1. Should the supplied raspberrypi-cm3.conf file internally refer to the
> Raspberry Pi 3 instead of the Raspberry Pi 2, since the RPi3 is the
> hardware basis of the Compute Module 3?
>

RaspberryPi 3 is currently almost the same as RaspberryPi 2 in terms of
configuration. What is the problem you are facing?


> 2. Should there also be an additional .conf file supplied in the
> meta-raspberry pi layer for a 64-bit version of poky Linux for the Compute
> Module 3, just as there is a raspberrypi3-64 machine .conf for the RPi3?
>

You can use directly raspberrypi3-64 as far as I am aware. The cm confs are
used as aliases right now. They point to one of the Raspberrypi 2 or 3
machine configurations.

--
Andrei G.

[-- Attachment #2: Type: text/html, Size: 2306 bytes --]

  reply	other threads:[~2018-05-01 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 23:40 [meta-raspberrypi] Compute Module 3 machine .conf questions Steve Pavao
2018-05-01 13:39 ` Andrei Gherzan [this message]
2018-05-02 22:56   ` Steve Pavao
2018-05-14 16:21     ` Andrei Gherzan

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=CAK18fxEEQ3BGKqeTciFkvzUbsyFNzkHBuz+drQ5j78OuqmZi7g@mail.gmail.com \
    --to=andrei@gherzan.ro \
    --cc=stevep@korgrd.com \
    --cc=yocto@yoctoproject.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.