From: radioconfusion@gmail•com (radioconfusion at gmail.com)
To: linux-arm-kernel@lists•infradead.org
Subject: [crypto] [marvell-cesa] Driver hangs on Armada 385 device
Date: Wed, 24 Aug 2016 12:15:07 +0300 [thread overview]
Message-ID: <57bd659d.0f4d190a.e025.5da4@mx.google.com> (raw)
Hello,
On Fri, 19 Aug 2016 16:09, Roman Perier wrote:
> 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
Huge thanks to Roman, Thomas and Russell.
The cesa works on your image and rootfs. Now it works on my system too.
The problem caused by my mistake, I was using the following kernel parameter:
mem=1048448k
My device has 1 GiB of RAM and I tried to reserve 128 kiB of memory for ram
oops. I guess this parameter caused overlapping or inaccessible area with cesa's
addresses. Am I right?
I tried to add memmap=0x20000$0x3ffe0000 without success.
Is this normal behaviour?
If yes, what is the right way to reserve RAM without killing the cesa? Should I
reserve memory at physical start point?
Best Regards,
Jussi
next reply other threads:[~2016-08-24 9:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 9:15 radioconfusion at gmail.com [this message]
2016-08-24 9:26 ` [crypto] [marvell-cesa] Driver hangs on Armada 385 device Russell King - ARM Linux
-- 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-19 11:54 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
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=57bd659d.0f4d190a.e025.5da4@mx.google.com \
--to=radioconfusion@gmail$(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