From: Arnaud Patard (Rtp) <arnaud.patard-dQbF7i+pzddAfugRpC6u6w@public.gmane.org>
To: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: rk3399 evb and sapphire board
Date: Tue, 19 Dec 2017 11:40:32 +0100 [thread overview]
Message-ID: <87efnratlr.fsf@lechat.rtp-net.org> (raw)
Hi,
[ I've asked the question on irc but nobody seemed to know, so I'm asking
to a wider audience. ]
I've bought a sapphire board from vamrs, without the excavator. I was
looking for the device tree to use and found a rk3399-sapphire.dtsi and a
rk3399-evb.dts. I've booted the kernel with the later, given that it's
the only dts file but there are missing things in it. The
rk3399-sapphire.dtsi looks way more complete.
So, are the rk3399 evb board and sapphire really the same board ? If so,
why the rk3399-evb.dts doesn't only include the rk3399-sapphire.dtsi ?
If not, should I use a device tree file including the
rk3399-sapphire.dtsi instead of the rk3399-evb.dts ? Would a patch
adding it would be accepted ?
Thanks,
Arnaud
reply other threads:[~2017-12-19 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87efnratlr.fsf@lechat.rtp-net.org \
--to=arnaud.patard-dqbf7i+pzddafugrpc6u6w@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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.