All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Randy 'ayaka' Li <ayaka@soulik.info>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-rockchip] [PATCH 0/5] add new SoCs support
Date: Tue, 23 Apr 2019 04:02:40 -0400	[thread overview]
Message-ID: <20190423080240.GA12920@linux-uys3> (raw)
In-Reply-To: <20190421155339.6332-1-ayaka@soulik.info>

Hi Randy,

On Sun 2019-04-21 @ 11:53:34 PM, Randy 'ayaka' Li wrote:
> After the FOSDEM, my patches for ARMv8 cortex tuning
> are finally merged. So I think it is complete the
> lose piece at meta-rockchip.
> 
> Since the big-litte is not supported by OE now,
> I make all the chips' configure to use the big core
> tuning.
> 
> Randy 'ayaka' Li (5):
>   conf/machine: rk3288: Add some machine files
>   conf/machine: add rk3399 support
>   conf/machine: add support for rk3328
>   conf/machine: add support for rk3036
>   conf/machine: add support for rv1108

I don't get the impression any of these patches were created for
git.yoctoproject.org/meta-rockchip. Although they apply, none of them actually
work. Or if they were intended for git.yoctoproject.org/meta-rockchip, then it
doesn't look like they were intended for the master branch (which is the
assumption when no branch tags are mentioned).

For example, many of these new MACHINEs indicate the Linux kernel
to use is "linux-rockchip" or "linux". Neither of these exist in
git.yoctoproject.org/meta-rockchip (or openembedded-core), so building any of
the MACHINEs introduced in these patches that specify either of these kernels
will fail.

git.yoctoproject.org/meta-rockchip is a community layer focused on providing
builds composed of upstream and open-source components (i.e. U-Boot from
git.denx.de/u-boot.git and the Linux kernel from kernel.org). Some BSP layers
(e.g. meta-freescale) are able to provide users with a switch so that builds
can be built either from vendor sources or upstream sources by setting one
parameter, but so far git.yoctoproject.org/meta-rockchip doesn't have this
functionality and my attempts to get this functionality integrated at a
higher level (i.e. instead of having every BSP layer implement this logic
independently) haven't met with success.

Best regards,
	Trevor


  parent reply	other threads:[~2019-04-23  8:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21 15:53 [meta-rockchip] [PATCH 0/5] add new SoCs support Randy 'ayaka' Li
2019-04-21 15:53 ` [PATCH 1/5] conf/machine: rk3288: Add some machine files Randy 'ayaka' Li
2019-04-23  8:24   ` Trevor Woerner
2019-04-21 15:53 ` [PATCH 2/5] conf/machine: add rk3399 support Randy 'ayaka' Li
2019-04-22  3:47   ` Khem Raj
2019-04-22  6:29     ` Ayaka
2019-04-22 20:31       ` Khem Raj
2019-04-23  8:10   ` Trevor Woerner
2019-04-21 15:53 ` [PATCH 3/5] conf/machine: add support for rk3328 Randy 'ayaka' Li
2019-04-23  8:15   ` Trevor Woerner
2019-04-21 15:53 ` [PATCH 4/5] conf/machine: add support for rk3036 Randy 'ayaka' Li
2019-04-23  8:13   ` Trevor Woerner
2019-04-21 15:53 ` [PATCH 5/5] conf/machine: add support for rv1108 Randy 'ayaka' Li
2019-04-23  8:11   ` Trevor Woerner
2019-04-22 15:05 ` [meta-rockchip] [PATCH 0/5] add new SoCs support Trevor Woerner
2019-04-23  8:02 ` Trevor Woerner [this message]
2019-04-23 10:56   ` Ayaka

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=20190423080240.GA12920@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=ayaka@soulik.info \
    --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.