From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Daniël Mantione" <daniel@deadlock.et.tudelft.nl>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>,
"David S. Miller" <davem@redhat.com>,
mroos@linux.ee,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Olaf Hering <olh@suse.de>
Subject: Re: atyfb still broken on 2.4.23-pre4 (on sparc64)
Date: Tue, 16 Sep 2003 00:07:12 +0200 [thread overview]
Message-ID: <1063663632.585.61.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0309152320130.24675-100000@deadlock.et.tudelft.nl>
On Mon, 2003-09-15 at 23:24, Daniël Mantione wrote:
> On Mon, 15 Sep 2003, Marcelo Tosatti wrote:
>
> > Ben reported it breaks PPC, too...
>
> The patch was tested on ppc, it is propably not PowerPC specific.
>
> Benjamin, on what kind of machine did things break? Can you provide some
> info?
I reported that I got user reports of breakage... so far, I don't know
more as I only have one mach64 machine that I couldn't test on yet.
At least, iBook1 is broken (M1 chipset) from what Olaf says (in CC
list).
There are a few PPC machines for which atyfb is "critical":
- PowerBook Wallstreet I (Rage LT-G, that one I can test)
- PowerBook Wallstreet II (Rage LT-Pro I think)
- PowerBook 101 (aka Lombard) (Rage LT-Pro)
- iBook1 (Rage M1)
- iMac rev A,B and C (not sure which chip, LT-Pro or just 3D Pro)
- Beige G3 (older XL iirc)
Along with some older "performa" I forgot about (5400 I think).
The current driver works at least well enough to get a console on all
of these. I'm not sure a stable serie should get a new driver if it
has not been properly validated on these. Unfortunately, I don't have
access to all of this HW to test with, so...
Why don't you push it to 2.6 first then backport to 2.4 ? That would
be better imho...
Ben.
Ben.
next prev parent reply other threads:[~2003-09-15 22:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 9:02 atyfb still broken on 2.4.23-pre4 (on sparc64) Meelis Roos
2003-09-14 9:35 ` Daniël Mantione
2003-09-15 8:11 ` David S. Miller
2003-09-15 10:58 ` Daniël Mantione
2003-09-15 21:38 ` David S. Miller
2003-09-15 21:56 ` Daniël Mantione
2003-09-15 14:25 ` Daniël Mantione
2003-09-15 21:19 ` Marcelo Tosatti
2003-09-15 21:24 ` Daniël Mantione
2003-09-15 22:07 ` Benjamin Herrenschmidt [this message]
2003-09-15 22:44 ` Daniël Mantione
2003-09-16 6:12 ` Benjamin Herrenschmidt
2003-09-17 21:48 ` James Simmons
2003-09-16 12:18 ` Olaf Hering
2003-09-16 12:41 ` Daniël Mantione
2003-09-16 13:07 ` Benjamin Herrenschmidt
2003-09-17 21:47 ` James Simmons
2003-09-17 21:56 ` Daniël Mantione
2003-09-17 22:02 ` James Simmons
2003-09-17 22:04 ` Daniël Mantione
2003-09-15 8:33 ` Meelis Roos
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=1063663632.585.61.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=daniel@deadlock.et.tudelft.nl \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=mroos@linux.ee \
--cc=olh@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.