From mboxrd@z Thu Jan  1 00:00:00 1970
From: Heiko Stuebner <heiko@sntech.de>
Date: Fri, 19 May 2017 16:46:04 +0200
Subject: [U-Boot] [PATCH] rockchip: doc: update latest info to document
In-Reply-To: <41072ecf-93f3-9d5e-d3ab-809281d7fc31@rock-chips.com>
References: <1494854280-10333-1-git-send-email-kever.yang@rock-chips.com>
 <2093150.511RQmXpmO@diego>
 <41072ecf-93f3-9d5e-d3ab-809281d7fc31@rock-chips.com>
Message-ID: <16802608.WcNDPyAU7n@phil>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: u-boot@lists.denx.de

Am Dienstag, 16. Mai 2017, 09:19:57 CEST schrieb Kever Yang:
>=20
> On 05/16/2017 02:51 AM, Heiko St=C3=BCbner wrote:
> > Hi Kever,
> >
> > Am Montag, 15. Mai 2017, 21:18:00 CEST schrieb Kever Yang:
> >> - Add some rk3399 and rk3328 boards;
> >> - use rkdeveloptool instead of rkflashtool;
> >> - use opensource.rock-chips.com instead of wikidot;
> >> - other update.
> >>
> >> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> >> ---
> >>
> >>   doc/README.rockchip | 38 ++++++++++++++++++++++++--------------
> >>   1 file changed, 24 insertions(+), 14 deletions(-)
> >>
> >> diff --git a/doc/README.rockchip b/doc/README.rockchip
> >> index 2d8cf9f..229db0d 100644
> >> --- a/doc/README.rockchip
> >> +++ b/doc/README.rockchip
> >> @@ -14,9 +14,6 @@ many Rockchip devices [1] [2].
> >>   The current mainline support is experimental only and is not useful =
for
> >>   anything. It should provide a base on which to build.
> >>
> >> -So far only support for the RK3288 and RK3036 is provided.
> >> -
> >> -
> >>   Prerequisites
> >>   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>
> >> @@ -26,17 +23,18 @@ You will need:
> >>      - Power connection to 5V using the supplied micro-USB power cable
> >>      - Separate USB serial cable attached to your computer and the Fir=
efly
> >>           (connect to the micro-USB connector below the logo)
> >> -   - rkflashtool [3]
> >> -   - openssl (sudo apt-get install openssl)
> >> +   - rkdeveloptool [3]
> > In my personal opinion, rkflashtool should stay. You can very well add
> > rkdeveloptool as a second option, but rkflashtool was there first and
> > also is the one that most distributions contain in their repositories.
> > And both tools seem to have the same functionality.
>=20
> OK, it can leave there, but I don't know why it does not works well with =

> rk3399.

I'd guess most likely because it is missing the soc-specific id for
the rk3399 [0].


Heiko

[0] https://github.com/linux-rockchip/rkflashtool/blob/master/rkflashtool.c=
#L103