From: =?gb18030?B?SmFjb2IgQ2hlbg==?= <jacob-chen@iotwrt.com>
To: =?gb18030?B?QnJ1Y2UgQXNoZmllbGQ=?= <bruce.ashfield@gmail.com>
Cc: =?gb18030?B?eW9jdG9AeW9jdG9wcm9qZWN0Lm9yZw==?=
<yocto@yoctoproject.org>,
=?gb18030?B?ssy34w==?= <eddie.cai@rock-chips.com>
Subject: Re: [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip
Date: Thu, 19 Jan 2017 21:54:32 +0800 [thread overview]
Message-ID: <tencent_5C34BA541506B0770449C279@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 3886 bytes --]
Sorry for sending without prefix, and make you guys confused.
This series patches is sending for meta-rockchip, not core meta data.
I'm new to here, and I just fllow readme in meta-rockchip to send patches.
------------------ Original ------------------
From: "Bruce Ashfield";<bruce.ashfield@gmail.com>;
Date: Thu, Jan 19, 2017 09:40 PM
To: "Jacob Chen"<jacob-chen@iotwrt.com>;
Cc: "Yocto Project Discussion"<yocto@yoctoproject.org>; "eddie.cai"<eddie.cai@rock-chips.com>;
Subject: Re: [yocto] [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip
On Thu, Jan 19, 2017 at 5:09 AM, Jacob Chen <jacob-chen@iotwrt.com> wrote:
This series of patches add below features, will add more supports in the future(medias, more chips).
1. rockchip 4.4 kernel
Rockchip 4.4 kernel is currently the latest version of the rockchip offical kernel, will be an upstream tracking branch.
We regularly release the kernel through github. It support all rockchip 64-bit chips and a few 32-bit chips.
Aha. Here was the 0/N that I was missing when I wrote my first reply. See my comments in
reply to the kernel recipe as to where this should land.
Cheers,
Bruce
2. rockchip next-dev U-boot
Rockchip next-dev U-boot is the next generation of rockchip u-boot, will also be an upstream tracking branch.
At present, this branch is just a rebased upstream u-boot.
3. graphics
We have plans for the acceleration in wayland, x11 in the rockchip platform, but in this series of patches, we only include the mali bianry support.
4. rockchip-next-image
Being different from the previous rk-u-boot which use parameter, next-dev u-boot use gpt partition, so it needs to generate a different image.
Jacob Chen (7):
recipes-kernel: linux-rockchip: Add new recipe for 4.4
machine: Add machine file for the rk3288 linux Boards
machine: firefly: use linux-rockchip by default
recipes-graphics: Add support for mali-userspace
recipes-bsp: add u-boot-rockchip support
rk3288.inc: add some variables
rockchip-next-image: introduce image for rockchip next-dev u-boot
classes/rockchip-next-image.bbclass | 130 +++++++++++++++++++++
conf/machine/evb-rk3288.conf | 12 ++
conf/machine/fennec-rk3288.conf | 12 ++
conf/machine/firefly-rk3288.conf | 4 +
conf/machine/include/rk-linux.inc | 20 ++++
conf/machine/include/rk3288.inc | 10 +-
conf/machine/tinker-rk3288.conf | 13 +++
recipes-bsp/u-boot/u-boot-rockchip_next.bb | 17 +++
recipes-graphics/mali-userspace/mali-userspace.inc | 57 +++++++++
.../mali-userspace/mali-userspace_t76x.bb | 18 +++
recipes-graphics/mesa/mesa_%.bbappend | 9 ++
recipes-kernel/linux/linux-rockchip_4.4.bb | 20 ++++
12 files changed, 321 insertions(+), 1 deletion(-)
create mode 100644 classes/rockchip-next-image.bbclass
create mode 100644 conf/machine/evb-rk3288.conf
create mode 100644 conf/machine/fennec-rk3288.conf
create mode 100644 conf/machine/include/rk-linux.inc
create mode 100644 conf/machine/tinker-rk3288.conf
create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_next.bb
create mode 100644 recipes-graphics/mali-userspace/mali-userspace.inc
create mode 100644 recipes-graphics/mali-userspace/mali-userspace_t76x.bb
create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
create mode 100644 recipes-kernel/linux/linux-rockchip_4.4.bb
--
2.7.4
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
[-- Attachment #2: Type: text/html, Size: 4981 bytes --]
next reply other threads:[~2017-01-19 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 13:54 =?gb18030?B?SmFjb2IgQ2hlbg==?= [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-19 10:09 [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip Jacob Chen
2017-01-19 10:19 ` Jacob Chen
2017-01-19 11:30 ` Burton, Ross
2017-01-19 11:49 ` =?gb18030?B?SmFjb2IgQ2hlbg==?=
2017-01-19 12:49 ` Gary Thomas
2017-01-19 13:55 ` Jacob Chen
2017-01-19 14:11 ` Jacob Chen
2017-01-19 13:40 ` Bruce Ashfield
2017-01-19 15:17 ` Leon Woestenberg
2017-01-24 18:34 ` Trevor Woerner
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=tencent_5C34BA541506B0770449C279@qq.com \
--to=jacob-chen@iotwrt.com \
--cc=bruce.ashfield@gmail.com \
--cc=eddie.cai@rock-chips.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.