linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jak <rfjak@eircom.net>
To: Antonino Daplas <adaplas@pol.net>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: rivafb "Badness" using fbdev.diff.gz and 2.5.5[45]
Date: Mon, 20 Jan 2003 19:09:10 +0000	[thread overview]
Message-ID: <200301201909.10951.rfjak@eircom.net> (raw)
In-Reply-To: <1042990390.1058.4.camel@localhost.localdomain>

Tony,
	thanks for your patches, they have fixed most of the problems I had.
>
> Try running stty to fix your display.
>
I can't convince stty to do anything useful for me :
	do I need a specific/patched version ?
	do I need to specify anything except rows cols values ?
	how would I change the colour depth ?
	I have 7 different lines in /etc/fb.modes related to 1024x768@8bpp,
how can I tell stty that I want to use the equivalent of the timing values of
any particular one of these 7 modes ( assuming timings are still relevant ) ?
	what was wrong with fbset which I have to keep for the forseeable
future anyway until 2.6 approaches 2.4 reliability ?
>
> So can you and Jak try the attached patch?  It should prevent VGA
> console corruption on insmod and it should eliminate the kobject trace
> messages.
>
Using your 3 recent patches together clears up the green screen problem
and text corruption as well as kobject "badness".

>  int __init rivafb_init(void)
>  {
> -	int err;
> -	err = pci_module_init(&rivafb_driver);
> -	if (err)
> -		return err;
> -	pci_register_driver(&rivafb_driver);
> -	return 0;
> +	return pci_module_init(&rivafb_driver);
>  }
>
This will normally return 1, not 0 as before. Is this intended ?




-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  reply	other threads:[~2003-01-20 19:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 13:30 rivafb "Badness" using fbdev.diff.gz and 2.5.5[45] Jak
2003-01-15  0:43 ` James Simmons
2003-01-18 20:28   ` Jak
2003-01-19 15:40     ` Antonino Daplas
2003-01-20 19:09       ` Jak [this message]
2003-01-20 22:44         ` Antonino Daplas
2003-01-21 10:29           ` Geert Uytterhoeven
2003-01-21 11:31             ` Antonino Daplas
2003-01-24 22:53             ` James Simmons
2003-01-25  9:00               ` Geert Uytterhoeven
2003-01-30 23:00                 ` Antonino Daplas
2003-02-12 20:13                   ` James Simmons
2003-01-21  0:08         ` Antonino Daplas
2003-01-24 20:14       ` James Simmons
2003-01-30 23:01         ` Antonino Daplas
2003-02-12 20:15           ` James Simmons
2003-02-12 23:37             ` Antonino Daplas
2003-01-24 19:09     ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2003-01-19 11:29 Fredrik Noring
2003-01-19 15:41 ` Antonino Daplas
2003-01-19 16:42   ` Fredrik Noring

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=200301201909.10951.rfjak@eircom.net \
    --to=rfjak@eircom.net \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).