From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: radeon boot "hot-crash"
Date: Sun, 04 Nov 2007 14:39:45 +1100 [thread overview]
Message-ID: <1194147585.6511.13.camel@pasglop> (raw)
In-Reply-To: <200711021955.49169.mb@bu3sch.de>
On Fri, 2007-11-02 at 19:55 +0100, Michael Buesch wrote:
> Hi,
>
> I'm wondering how we are finally going to fix my radeon
> "hot-crash" issue.
> Fact is, applying the patch below fixes the issue.
And will break somebody else ...
> Though, I see that this is not the correct patch to fix it.
> Other devices might need the register write which is removed here.
> So what about the following:
> We add a specialcase for the exact type (and revision and so on)
> for my chip here.
> How do find out what's my chiprevision?
> What exactly should be checked for here, so that only this chip
> is affected by the workaround?
I think best is to check for the specific machine. What powerbook model
is this ?
Ben.
>
> Index: wireless-2.6/drivers/video/aty/radeon_i2c.c
> ===================================================================
> --- wireless-2.6.orig/drivers/video/aty/radeon_i2c.c 2007-10-17 18:03:10.000000000 +0200
> +++ wireless-2.6/drivers/video/aty/radeon_i2c.c 2007-10-17 18:18:52.000000000 +0200
> @@ -137,13 +137,7 @@ void radeon_delete_i2c_busses(struct rad
> int radeon_probe_i2c_connector(struct radeonfb_info *rinfo, int conn,
> u8 **out_edid)
> {
> - u32 reg = rinfo->i2c[conn-1].ddc_reg;
> - u8 *edid;
> -
> - OUTREG(reg, INREG(reg) &
> - ~(VGA_DDC_DATA_OUTPUT | VGA_DDC_CLK_OUTPUT));
> -
> - edid = fb_ddc_read(&rinfo->i2c[conn-1].adapter);
> + u8 *edid = fb_ddc_read(&rinfo->i2c[conn-1].adapter);
>
> if (out_edid)
> *out_edid = edid;
>
prev parent reply other threads:[~2007-11-04 3:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 18:55 radeon boot "hot-crash" Michael Buesch
2007-11-04 3:39 ` Benjamin Herrenschmidt [this message]
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=1194147585.6511.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mb@bu3sch.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;
as well as URLs for NNTP newsgroup(s).