From: romain.perier@free-electrons•com (Romain Perier)
To: linux-arm-kernel@lists•infradead.org
Subject: [crypto] [marvell-cesa] Driver hangs on Armada 385 device
Date: Fri, 19 Aug 2016 16:39:24 +0200 [thread overview]
Message-ID: <57B71A1C.3010607@free-electrons.com> (raw)
In-Reply-To: <20160819142145.GQ1041@n2100.armlinux.org.uk>
Hello,
Le 19/08/2016 16:21, Russell King - ARM Linux a ?crit :
> On Fri, Aug 19, 2016 at 04:09:05PM +0200, Romain Perier wrote:
>> I was, wondering, do you boot with a separated DTB or a legacy boot
>> (concatenated to the Image) ?
>>
>>
>> Could you test with uImage.armada-385-db-ap [1], that's a legacy Image.
>> Also, I have uploaded a minimalistic rootfs [2], if you want.
>>
>> 1. http://www.free-electrons.com/~romain/pub/cesa/uImage.armada-385-db-ap
>> 2. http://www.free-electrons.com/~romain/pub/cesa/rootfs.cpio.xz
>
> I assume you mean Thomas rather than myself, as I have only Clearfog
> platforms, which are all Armada 388.
Yep, sorry. I meant, the person who has issues with cesa, i.e
radioconfusion at gmail.com :)
>
> I don't use uImage anymore, except with versions of uboot that are
> unable to support zImage booting. Where zImage booting is supported,
> I'm always using a separated DTB. Doing otherwise is insane IMHO.
>
That's just, we have several ways to boot our Marvell devices, including
legacy or non legacy boots, uImage and zImage. Anyway,
that's not the point of my previous email.
Romain
--
Romain Perier, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-19 14:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 11:54 [crypto] [marvell-cesa] Driver hangs on Armada 385 device radioconfusion at gmail.com
2016-08-19 12:12 ` Thomas Petazzoni
2016-08-19 13:07 ` Romain Perier
2016-08-19 13:08 ` Russell King - ARM Linux
2016-08-19 13:28 ` Russell King - ARM Linux
2016-08-19 14:09 ` Romain Perier
2016-08-19 14:19 ` Romain Perier
2016-08-19 14:21 ` Russell King - ARM Linux
2016-08-19 14:39 ` Romain Perier [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-24 10:52 radioconfusion at gmail.com
2016-08-24 12:38 ` Thomas Petazzoni
2016-08-24 9:15 radioconfusion at gmail.com
2016-08-24 9:26 ` Russell King - ARM Linux
2016-07-14 12:29 radioconfusion at gmail.com
2016-07-08 9:55 radioconfusion at gmail.com
2016-07-07 9:20 radioconfusion at gmail.com
2016-07-07 13:43 ` Thomas Petazzoni
2016-07-05 8:46 radioconfusion at gmail.com
2016-07-06 7:06 ` Thomas Petazzoni
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=57B71A1C.3010607@free-electrons.com \
--to=romain.perier@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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