From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: Russell King - ARM Linux <linux@armlinux.org.uk>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
Vincent Guittot <vincent.guittot@linaro.org>,
Rob Herring <robh@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
rnayak@codeaurora.org, Shiraz Hashim <shashim@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 0/5] drivers: Add boot constraints core
Date: Thu, 29 Jun 2017 13:05:42 +0000 [thread overview]
Message-ID: <7ff5fe0b-72fa-7a23-44df-59761cc6dd1c@gr13.net> (raw)
In-Reply-To: <20170629124908.GV4902@n2100.armlinux.org.uk>
On 29.06.2017 12:49, Russell King - ARM Linux wrote:
> The location of the frame buffer is unknown to the decompressor - and
> as the decompressor self-relocates itself (using purely assembly code),
> it could relocate itself on top of the frame buffer, causing the "nice"
> image to become very colourful.
Could the bootloader pass safe (or blocked) memory regions to the
decompressor ?
--mtx
next prev parent reply other threads:[~2017-06-29 13:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 10:26 Viresh Kumar
2017-06-28 10:26 ` [RFC 1/5] " Viresh Kumar
2017-06-28 15:55 ` Randy Dunlap
2017-06-29 3:51 ` Viresh Kumar
2017-06-29 12:50 ` Russell King - ARM Linux
2017-06-29 14:49 ` Viresh Kumar
2017-06-28 10:26 ` [RFC 2/5] drivers: boot_constraint: Add support for supply constraints Viresh Kumar
2017-06-28 10:26 ` [RFC 3/5] drivers: boot_constraint: Add boot_constraints_disable kernel parameter Viresh Kumar
2017-06-28 15:51 ` Randy Dunlap
2017-06-28 10:26 ` [RFC 4/5] drivers: boot_constraint: Add debugfs support Viresh Kumar
2017-06-28 15:46 ` Randy Dunlap
2017-06-29 4:11 ` Viresh Kumar
2017-06-28 10:26 ` [RFC 5/5] drivers: Code to test boot constraints Viresh Kumar
2017-06-29 12:40 ` [RFC 0/5] drivers: Add boot constraints core Enrico Weigelt, metux IT consult
2017-06-29 14:47 ` Viresh Kumar
2017-06-29 15:06 ` Enrico Weigelt, metux IT consult
2017-06-30 3:16 ` Viresh Kumar
2017-06-30 3:33 ` Chen-Yu Tsai
2017-06-30 3:55 ` Viresh Kumar
2017-06-30 4:05 ` Chen-Yu Tsai
2017-06-30 4:12 ` Viresh Kumar
2017-06-30 4:22 ` Chen-Yu Tsai
2017-06-30 5:12 ` Viresh Kumar
2017-06-30 6:36 ` Chen-Yu Tsai
2017-06-30 8:43 ` Viresh Kumar
2017-06-30 12:10 ` Mark Brown
2017-07-03 6:15 ` Viresh Kumar
2017-07-03 15:07 ` Mark Brown
2017-07-04 6:45 ` Viresh Kumar
2017-06-30 12:12 ` Mark Brown
2017-06-29 12:49 ` Russell King - ARM Linux
2017-06-29 13:05 ` Enrico Weigelt, metux IT consult [this message]
2017-06-29 14:58 ` Viresh Kumar
2017-06-29 15:43 ` Russell King - ARM Linux
2017-06-29 21:00 ` Stephen Boyd
2017-07-05 22:07 ` Rob Clark
2017-07-07 22:39 ` Stephen Boyd
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=7ff5fe0b-72fa-7a23-44df-59761cc6dd1c@gr13.net \
--to=enrico.weigelt@gr13.net \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shashim@codeaurora.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®