From: "Antonino A. Daplas" <adaplas@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: "Calin A. Culianu" <calin@ajvar.org>,
akpm@osdl.org, adaplas@pol.net, linux-kernel@vger.kernel.org,
linux-nvidia@lists.surfsouth.com,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] nvidiafb support for 6600 and 6200
Date: Sun, 27 Nov 2005 05:51:29 +0800 [thread overview]
Message-ID: <4388D8E1.2040806@gmail.com> (raw)
In-Reply-To: <4387FFFD.2000109@gmail.com>
Antonino A. Daplas wrote:
> Calin A. Culianu wrote:
>> Hi,
>>
>> This patch can be applied against 2.6.15-rc1 to add support to the
>> nvidiafb driver for a few obscure (yet on-the-market) nvidia
>> boards/chipsets, including various versions of the Geforce 6600 and 6200.
>>
>> This patch has been tested and allows the above-mentioned boards to get
>> framebuffer console support.
>>
>
> Is this a pci-e card? With a pci-e card, the actual chipset type is located
> in one of the registers (instead of deriving it from the pci device id) and
> will resolve into one of the supported architectures, usually an NV_ARCH_40.
>
> Can you try this patch instead? And send me your dmesg whether it works or
> not.
Forgot to mention that you still have to add your device to nvidiafb_pci_tbl
after applying this patch.
Tony
next prev parent reply other threads:[~2005-11-26 21:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 5:02 [PATCH] nvidiafb support for 6600 and 6200 Calin A. Culianu
2005-11-26 6:26 ` Antonino A. Daplas
2005-11-26 6:33 ` Antonino A. Daplas
2005-11-26 21:51 ` Antonino A. Daplas [this message]
2005-11-28 10:35 ` nvidia fb flicker (was: Re: [PATCH] nvidiafb support for 6600 and 6200) Marc Koschewski
2005-11-28 12:31 ` nvidia fb flicker Antonino A. Daplas
2005-11-28 13:20 ` Marc Koschewski
2005-11-28 14:00 ` Antonino A. Daplas
2005-11-28 21:24 ` Marc Koschewski
2005-11-28 22:20 ` Antonino A. Daplas
2005-11-28 23:01 ` Linus Torvalds
2005-11-29 0:13 ` Antonino A. Daplas
2005-11-28 19:57 ` Giuseppe Bilotta
2005-11-29 0:20 ` Antonino A. Daplas
2005-11-29 9:08 ` Marc Koschewski
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=4388D8E1.2040806@gmail.com \
--to=adaplas@gmail.com \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=calin@ajvar.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvidia@lists.surfsouth.com \
--cc=torvalds@osdl.org \
/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.