public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdittmer@ppp0.net>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Jurriaan <thunder7@xs4all.nl>,
	linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: no cursor on nvidiafb console in 2.6.14-rc1-mm1
Date: Tue, 20 Sep 2005 18:09:26 +0200	[thread overview]
Message-ID: <43303436.4080007@ppp0.net> (raw)
In-Reply-To: <432FE3E0.3020405@gmail.com>

Antonino A. Daplas wrote:
> Jan Dittmer wrote:
> 
>>Antonino A. Daplas wrote:
>>
>>>Jan Dittmer wrote:
>>>
>>>
>>>>jurriaan wrote:
>>>>
>>>>
>>>>>After updating from 2.6.13-rc4-mm1 to 2.6.14-rc1-mm1 I see no cursor on
>>>>>my console.
>>>>
>>>>Me too, 2.6.14-rc1-git4. Didn't try any kernel before with framebuffer,
>>>>sorry. No fb options on the kernel command line.
>>>>
>>>
>>>Can you try reversing this particular diff?
>>>
>>>http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobdiff_plain;h=af99ea96012ec72ef57fd36655a6d8aaa22e809e;hp=30f80c23f934bb0a76719232f492153fc7cca00a
>>>
>>>Tony
>>>
>>
>>--- 30f80c23f934bb0a76719232f492153fc7cca00a
>>+++ af99ea96012ec72ef57fd36655a6d8aaa22e809e
>>
>>^^^ Which file??
>>
> 
> 
> Heh, didn't realize that. drivers/video/nvidia/nvidia.c, actually.
> But just apply this patch instead, as a Kconfig change is also
> needed.
> 

This fixes it,

Thanks,

Jan

  reply	other threads:[~2005-09-20 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 17:51 no cursor on nvidiafb console in 2.6.14-rc1-mm1 jurriaan
2005-09-19 18:51 ` Jan Dittmer
2005-09-19 22:07   ` Antonino A. Daplas
2005-09-19 23:31     ` [Linux-fbdev-devel] " James Simmons
2005-09-20  0:20       ` Antonino A. Daplas
2005-09-20  7:38     ` Jan Dittmer
2005-09-20 10:26       ` Antonino A. Daplas
2005-09-20 16:09         ` Jan Dittmer [this message]
2005-09-21 11:32         ` jurriaan

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=43303436.4080007@ppp0.net \
    --to=jdittmer@ppp0.net \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    /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