linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Zielinski <grim@undead.cc>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Missing radeonfb_setup
Date: Wed, 12 Nov 2003 23:43:03 -0500	[thread overview]
Message-ID: <3FB30BD7.7070904@undead.cc> (raw)

Changing monitor_layout and mode_option to fixed length arrays was 
causing problems for me.  Looks like it might have been because the 
arrays were uninitialized.  The following patch adds the radeonfb_setup 
function while leaving those variables as pointers:

http://www.undead.cc/linux/patch.radeon_setup

I didn't include the change to the default video mode as I'm still 
mucking around with that.  Also, I left the default video mode code as 
is as the changes in the update looked wrong.

Also, here's a patch to fix some compiler warnings.  Most were harmless 
but the one about xtal was indeed a bug.  Can someone let me know if I 
got the fix for that one right:

http://www.undead.cc/linux/patch.fixwarnings

I'm also having a cursor problem.  It makes the character it's over 
disappear when it flashes active.  So I have the character then the 
cursor then the character then the cursor, etc.  This is very 
distracting since it's the line cursor and not the block cursor.  How do 
I go about fixing this?

One more thing, which patch added the CONFIG_FB_RADEON_I2C menu choice?  
I had to add that one myself to get it?

John





-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/

             reply	other threads:[~2003-11-13  4:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13  4:43 John Zielinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-28 21:55 Missing radeonfb_setup Javier Villavicencio
2003-10-29  9:19 ` Geert Uytterhoeven

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=3FB30BD7.7070904@undead.cc \
    --to=grim@undead.cc \
    --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).