linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Guido Guenther <agx@sigxcpu.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Wolfram Quester <wolfi@mittelerde.physik.uni-konstanz.de>
Subject: Re: rivafb: finally enable NV30 based pbooks/cleanup probe errors
Date: Fri, 19 Nov 2004 07:19:24 +0800	[thread overview]
Message-ID: <200411190719.24961.adaplas@hotpop.com> (raw)
In-Reply-To: <20041118164946.GA3763@bogon.ms20.nix>

On Friday 19 November 2004 00:49, Guido Guenther wrote:
> Hi Antonio,
> this patch against 2.6.10-rc2 finally detects rivafb on NV30 based power
> books by adding the pciid. Wolfram Quester tested it and reported it
> working. It also cleans up the error code reported from the probe
> function.
>

Thanks.

I also tested NV32 (GeForce FX 5200 0x0322) which also works.  So, I'm
planning to add a lot of NV30 entries to pci_ids.h and the rivafb pci_table
just so we can get a lot of reports (good and bad) from users.

> Singed-Off-By: Guido Guenther <agx@sigxcpu.org>
   ^^^^^^^
:-)

Tony




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

  reply	other threads:[~2004-11-18 23:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 16:49 rivafb: finally enable NV30 based pbooks/cleanup probe errors Guido Guenther
2004-11-18 23:19 ` Antonino A. Daplas [this message]
2004-11-19  8:09   ` Guido Guenther
2004-11-19  9:20     ` Andrew Walrond
2004-11-19 11:09       ` Antonino A. Daplas
2004-11-20  0:42       ` Guido Guenther
2004-11-19 11:09     ` Antonino A. Daplas
2004-11-19 11:58       ` Guido Guenther
2004-11-19 12:24       ` Andrew Walrond
2004-11-19 13:33         ` Guido Guenther

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=200411190719.24961.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=agx@sigxcpu.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=wolfi@mittelerde.physik.uni-konstanz.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).