From: Mark Rutland <mark.rutland@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: display: Align end of memory to work around a linux-4.0 bug
Date: Tue, 5 May 2015 10:39:14 +0100 [thread overview]
Message-ID: <20150505093914.GA20402@leverpostej> (raw)
In-Reply-To: <1430732203.15640.220.camel@hellion.org.uk>
On Mon, May 04, 2015 at 10:36:43AM +0100, Ian Campbell wrote:
> On Mon, 2015-05-04 at 10:51 +0200, Hans de Goede wrote:
> > Hi,
> >
> > On 02-05-15 15:21, Ian Campbell wrote:
> > > On Fri, 2015-04-24 at 20:39 +0200, Hans de Goede wrote:
> > >> Linux-4.0 as shipped has a bug causing it to not boot if the end of memory
> > >> is not aligned to a multiple of 2 MiB. For details see the linux-arm
> > >> mailing list post titled:
> > >> "Memory size unaligned to section boundary"
> > >> http://www.spinics.net/lists/arm-kernel/msg413811.html
> > >>
> > >> This is something which specifically hits the sunxi display driver because
> > >> we carve out the exact needed framebuffer size at the top of mem, this
> > >> commit works around this issue by aligning the carve out.
> > >
> > > I'm afraid I don't like this, we shouldn't be working around Linux bugs
> > > in the firmware, especially when both are Free software. Lets just fix
> > > Linux and get the fix into the appropriate stable trees and in the
> > > meantime tell people to avoid this buggy kernel.
> > >
> > > The problem with this sort of thing is that it is very hard to get rid
> > > of these workarounds, even once the underlying issue is fixed and we no
> > > longer care about the versions with the bug OS authors (including
> > > non-Linux OSes) can inadvertently come to rely on the quirky behaviour,
> > > (i.e. the work around masks other bugs). Hence we end up in a
> > > quirks-race as everyone works around the other parties last workaround.
> > >
> > > If there is to be a workaround instead of a fix then it should be for
> > > Linux to align memory to 2MB boundaries if that is what it requires.
> >
> > I can understand where you're coming from, the problem is that despite
> > various mails to the arm kernel mailing list no one from the upstream
> > kernel seems to be looking into this,
>
> Mark, do you think you could find some cycles (not necessarily your own)
> to look at this, or perhaps you know the appropriate maintainers to
> ping?
I'll have another look and see if I can come up with a kernel patch.
Perhaps proposing something (even if slightly wrong) will provoke people
to respond.
> I'd really like to avoid having to hack around kernel bugs in the
> firmware.
Likewise.
Mark.
next prev parent reply other threads:[~2015-05-05 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 18:39 [U-Boot] [PATCH] sunxi: display: Align end of memory to work around a linux-4.0 bug Hans de Goede
2015-05-02 13:21 ` Ian Campbell
2015-05-04 8:51 ` Hans de Goede
2015-05-04 9:36 ` Ian Campbell
2015-05-05 9:39 ` Mark Rutland [this message]
2015-05-12 13:53 ` Mark Rutland
2015-05-12 14:31 ` Ian Campbell
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=20150505093914.GA20402@leverpostej \
--to=mark.rutland@arm.com \
--cc=u-boot@lists.denx.de \
/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