linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [crypto] [marvell-cesa] Driver hangs on Armada 385 device
Date: Wed, 24 Aug 2016 10:26:47 +0100	[thread overview]
Message-ID: <20160824092647.GH1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <57bd659d.0f4d190a.e025.5da4@mx.google.com>

On Wed, Aug 24, 2016 at 12:15:07PM +0300, radioconfusion at gmail.com wrote:
> The problem caused by my mistake, I was using the following kernel parameter:
> mem=1048448k

Try mem=1046M - reducing it by 2MB.  If that works, try mem=1047M
instead.  Yes, that's more than you want to reserve, but please
check how the system behaves with these.

> 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.

memmap= has no meaning on ARM.  It's an x86 thing, the ARM arch has
never implemented it.  I've seen this come up a few times, and I don't
know why people keep trying to use it (always with an "it doesn't seem
to work" result.)  It's even documented as being an ACPI / x86 thing
in Documentation/kernel-parameters.txt...

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-08-24  9:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  9:15 [crypto] [marvell-cesa] Driver hangs on Armada 385 device radioconfusion at gmail.com
2016-08-24  9:26 ` Russell King - ARM Linux [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-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=20160824092647.GH1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).