From: Sascha Hauer <sha@pengutronix.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
Cc: barebox@lists.infradead.org
Subject: Re: Rockchip rk3328 support?
Date: Fri, 10 Nov 2023 13:42:06 +0100 [thread overview]
Message-ID: <20231110124205.GW3359458@pengutronix.de> (raw)
In-Reply-To: <ZU4C4WtD8k3Xzl4W@hephaistos.inside-m2m.de>
Hi Konsti,
On Fri, Nov 10, 2023 at 11:16:01AM +0100, Konstantin Kletschke wrote:
> Dear barebox community,
>
> is something like the rk3328 supported actually? I have a Dusun DSGW-210
> device here which _seems_ to be mainly 99% like a rk3328 EVB board (Olimex
> rk3328 eval bord).
The rk3328 is not yet supported. We have support for rk3568 and rk3288
though, so the ground work for generally supporting Rockchip SoCs has
been done. I don't know how similar the rk3328 is to the supported SoCs,
you could have a look at the Kernel or U-Boot to see how close they are.
>
> From the CONFIG options or cpu support files I would say no, but there
> is dts/src/arm64/rockchip/rk3328-evb.dts which sounds rather good so I
> wonder if this is hidden as a subset under other board/cpu.
The dts/ directory is taken verbatim from
git://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git
which contains all Linux device tree files. The ones actually supported
by barebox are in arch/*/dts/. These include the upstream device tree
files where possible
Regards,
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-11-10 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 10:16 Konstantin Kletschke
2023-11-10 12:42 ` Sascha Hauer [this message]
2023-11-10 13:12 ` Konstantin Kletschke
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=20231110124205.GW3359458@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=konstantin.kletschke@inside-m2m.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox