From: Olaf Hering <olh@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Daniël Mantione" <daniel@deadlock.et.tudelft.nl>,
"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>
Subject: Re: atyfb still broken on 2.4.23-pre4 (on sparc64)
Date: Tue, 16 Sep 2003 14:18:48 +0200 [thread overview]
Message-ID: <20030916121848.GA9897@suse.de> (raw)
In-Reply-To: <1063663632.585.61.camel@gaston>
On Tue, Sep 16, Benjamin Herrenschmidt wrote:
> There are a few PPC machines for which atyfb is "critical":
> - Beige G3 (older XL iirc)
this one works, but they use different chips.
atyfb: using auxiliary register aperture
atyfb: 3D RAGE (GT) [0x4754 rev 0x9a] 2M SGRAM, 14.31818 MHz XTAL, 200 MHz PLL, 67 Mhz MCLK, 67 Mhz XCLK
atyfb: monitor sense=737, mode 5
Console: switching to colour frame buffer device 80x30
fb0: ATY Mach64 frame buffer device on PCI
MacOS display is /pci/ATY,mach64_3DU
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next prev parent reply other threads:[~2003-09-16 12:18 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
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 [this message]
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=20030916121848.GA9897@suse.de \
--to=olh@suse.de \
--cc=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 \
/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.