LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@linuxcare.com.au>
To: Scott Hankin <shankin@rational.com>
Cc: phandel@cise.ufl.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-test10 boot failure on Powerbook G3
Date: Fri, 20 Oct 2000 12:38:55 +1100 (EST)	[thread overview]
Message-ID: <14831.41519.899373.33270@argo.linuxcare.com.au> (raw)
In-Reply-To: <p04320400b61508915079@[172.21.170.210]>


Scott Hankin writes:

> It turned out that the pc was in do_install_cmap, and lr was in
> atyfb_set_var.  The latter calls the former near the end of the
> routine (check out drivers/video/atyfb.c:2940) but as to why it's
> bombing, I have no clue.

Looking at the code for that routine:

static void do_install_cmap(int con, struct fb_info *fb)
{
    struct fb_info_aty *info = (struct fb_info_aty*)info;

that first statement doesn't make sense, change it to:

    struct fb_info_aty *info = (struct fb_info_aty*) fb;

and that should fix it.

BTW, I now have copies of my rsync trees at penguinppc.org, which will
hopefully have more bandwidth available than ppc.samba.org did.  The
tree at penguinppc.org::linux-pmac-devel has this bug fixed.

Paul.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-10-20  1:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19 17:13 2.4.0-test10 boot failure on Powerbook G3 Scott Hankin
2000-10-19 17:36 ` Benjamin Herrenschmidt
2000-10-19 17:44 ` Benjamin Herrenschmidt
2000-10-19 20:06 ` phandel
2000-10-19 20:51   ` Scott Hankin
2000-10-20  1:38     ` Paul Mackerras [this message]
2000-10-20 13:46       ` Scott Hankin

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=14831.41519.899373.33270@argo.linuxcare.com.au \
    --to=paulus@linuxcare.com.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=phandel@cise.ufl.edu \
    --cc=shankin@rational.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