From: Paul Mackerras <paulus@samba.org>
To: "Paul A. Clarke" <pc@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev-devel@lists.sourceforge.net,
adaplas@pol.net
Subject: Re: [Linux-fbdev-devel] [PATCH] Fbdev driver for IBM GXT4500P video cards
Date: Fri, 8 Dec 2006 08:50:14 +1100 [thread overview]
Message-ID: <17784.35990.297107.498146@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <4577B0C7.80502@us.ibm.com>
Paul A. Clarke writes:
> Any reason to believe this wouldn't work with a GXT6500P as well? It's almost
> identical to the GXT4500P except for an added geometry engine.
It should work, as you say, but I haven't tested it.
> I have one, but won't be near it again until mid-January.
Let me know how it goes if/when you get to test it. At a minimum
you'll need to add the 6500's PCI device ID to the table.
Paul.
prev parent reply other threads:[~2006-12-07 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 2:51 [PATCH] Fbdev driver for IBM GXT4500P video cards Paul Mackerras
2006-11-24 19:13 ` Helge Deller
2006-12-07 6:12 ` Paul A. Clarke
2006-12-07 21:50 ` Paul Mackerras [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=17784.35990.297107.498146@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=pc@us.ibm.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;
as well as URLs for NNTP newsgroup(s).