From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Adrian McMenamin <adrianmcmenamin@gmail.com>
Cc: Adrian McMenamin <lkmladrian@gmail.com>,
linux-kernel@vger.kernel.org, lethal@users.sourceforge.net
Subject: Re: Problems with framebuffer in 2.6.22-git17
Date: Sat, 28 Jul 2007 05:31:30 +0800 [thread overview]
Message-ID: <1185571890.26603.7.camel@daplas> (raw)
In-Reply-To: <92a12cdb0707271318t141ee32bs69cb9dab22eabba2@mail.gmail.com>
On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin wrote:
> On 27/07/07, Adrian McMenamin <adrianmcmenamin@gmail.com> wrote:
>
> > With the patch reverted and 24bpp, it oopses before freezing (with two
> > odd looking boot logos on the screen):
> >
> Tested this further and it fails on:
>
> rev = fb_readl(par->mmio_base + 0x04);
Doubtful if this line is the point of failure, this line is executed
only once, on initialization.
>
> Will try to see what's up - but if anyone knows what is likely to be
> wrong here please shout out!
I'm still thinking there's something wrong on how the resources are
allocated causing a pseudo_palette overrun.
I'll post a clean-up patch later.
Tony
next prev parent reply other threads:[~2007-07-27 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 18:41 Problems with framebuffer in 2.6.22-git17 Adrian McMenamin
2007-07-22 21:02 ` Adrian McMenamin
2007-07-22 23:22 ` Antonino A. Daplas
[not found] ` <8b67d60707231324k28f3cd45p287418fd77feaf00@mail.gmail.com>
2007-07-23 20:35 ` Adrian McMenamin
2007-07-23 21:06 ` Paul Mundt
2007-07-24 21:45 ` Adrian McMenamin
2007-07-25 23:33 ` Antonino A. Daplas
2007-07-27 19:47 ` Adrian McMenamin
2007-07-27 20:18 ` Adrian McMenamin
2007-07-27 21:31 ` Antonino A. Daplas [this message]
2007-07-27 22:25 ` Adrian McMenamin
2007-07-27 23:22 ` Antonino A. Daplas
2007-07-28 0:32 ` Adrian McMenamin
2007-07-28 0:52 ` Antonino A. Daplas
2007-07-28 1:06 ` Adrian McMenamin
2007-07-28 2:14 ` Antonino A. Daplas
2007-07-28 2:18 ` Antonino A. Daplas
2007-07-27 21:43 ` Antonino A. Daplas
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=1185571890.26603.7.camel@daplas \
--to=adaplas@gmail.com \
--cc=adrianmcmenamin@gmail.com \
--cc=lethal@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmladrian@gmail.com \
/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