From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
Jinyang He <hejinyang@loongson.cn>,
Mike Rapoport <rppt@kernel.org>,
Youling Tang <tangyouling@loongson.cn>,
Tobias Wolf <dev-NTEO@vplace.de>,
Marcin Nowakowski <marcin.nowakowski@mips.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: fix memory reservation for non-usermem setups
Date: Fri, 12 Mar 2021 16:19:34 +0100 [thread overview]
Message-ID: <20210312151934.GA4209@alpha.franken.de> (raw)
In-Reply-To: <20210307194030.8007-1-ilya.lipnitskiy@gmail.com>
On Sun, Mar 07, 2021 at 11:40:30AM -0800, Ilya Lipnitskiy wrote:
> From: Tobias Wolf <dev-NTEO@vplace.de>
>
> Commit 67a3ba25aa95 ("MIPS: Fix incorrect mem=X@Y handling") introduced a new
> issue for rt288x where "PHYS_OFFSET" is 0x0 but the calculated "ramstart" is
> not. As the prerequisite of custom memory map has been removed, this results
> in the full memory range of 0x0 - 0x8000000 to be marked as reserved for this
> platform.
and where is the problem here ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-03-12 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 19:40 [PATCH] MIPS: fix memory reservation for non-usermem setups Ilya Lipnitskiy
2021-03-12 15:19 ` Thomas Bogendoerfer [this message]
2021-03-17 5:10 ` Ilya Lipnitskiy
2021-03-17 6:33 ` Mike Rapoport
2021-04-04 2:02 ` Ilya Lipnitskiy
2021-04-06 13:10 ` Thomas Bogendoerfer
2021-04-13 6:45 ` Ilya Lipnitskiy
2021-04-13 6:52 ` Ilya Lipnitskiy
2021-04-14 13:46 ` Mike Rapoport
2021-04-04 2:11 ` [PATCH] MIPS: ralink: rt288x: select MIPS_AUTO_PFN_OFFSET Ilya Lipnitskiy
2021-04-06 13:11 ` Thomas Bogendoerfer
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=20210312151934.GA4209@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=dev-NTEO@vplace.de \
--cc=hejinyang@loongson.cn \
--cc=ilya.lipnitskiy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=marcin.nowakowski@mips.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tangyouling@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.