mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: S Ait-Kassi <sait-kassi@zonnet.nl>
To: linux-kernel@vger.kernel.org
Subject: [update]  Vesafb problem since 2.5.51
Date: Fri, 2 Jan 2004 14:22:44 +0100	[thread overview]
Message-ID: <200401021422.44324.sait-kassi@zonnet.nl> (raw)

Hello,

I figured out in which kernel the problem I was having appeared. It seems to 
work with 2.5.50 and the problems starts with 2.5.51.

I've looked at the changelog and showed these changes that might have 
contibuted to my problem;

-There are some changes in fbcon. Made modular along with some fixes and some 
vesafb fixes.

-Accel wrapper is now intergarted into fbcon.c. VESA fb fixes 

-Made fbcon modular.

-New NVIDIA and Radeon cards pci ids. Soon I will add support for these :-) 
Also a needed fix for fbcon.c. 

-Moved AGP and DRM code back to drivers/char until a proper solution is done 
for handling AGP/DMA based framebuffer devices.

Almost all changes by the same developer <jsimmons>. I've been looking
at the source differences but the introduction of the fbcon module really 
complicates the matter.

I was wondering where to go about reporting the 
problem or where this issue might stem from. (i.e. the includes shown in 
vesafb.h, vesafb.h itself, fb.h or the fbcon module related code.

Or would it be best to just mail the developer? :)
Any help is appreciated.

Regards,

P.S.: Here is the part of my original mail describing the problem. It has been 
confirmed by two other submits to this mailinglist regarding the 2.6.0-test4 
kernel. I'm using the 2.6.0.-bk3 kernel myself.

>The most apparent occurrence of the problem for me is when 
>running mc (Midnight Commander). The blue blackground isn't drawn in the 
>parts where there is no text. When using mcedit this comes all the more clear 
>and  particularly when scrolling is done. The space which hasn't got any text 
>is replaced with RGB pixels (looks grey from a distance). If you jump back 
>from one console and back again the screen is redrawn correctly.



             reply	other threads:[~2004-01-02 13:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 13:22 S Ait-Kassi [this message]
2004-01-04  0:11 S Ait-Kassi
2004-01-05 22:13 ` James Simmons
     [not found] <1a49X-1o2-7@gated-at.bofh.it>
2004-01-04  9:50 ` Andreas Theofilu
2004-01-06 13:40 S Ait-Kassi
2004-01-06 23:06 ` James Simmons
2004-01-07 23:40   ` S Ait-Kassi
2004-01-09 20:57     ` James Simmons
2004-01-08  9:29   ` Pavel Machek
2004-01-13 14:47 S Ait-Kassi

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=200401021422.44324.sait-kassi@zonnet.nl \
    --to=sait-kassi@zonnet.nl \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome