public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: "Paulo Andre'" <fscked@netvisao.pt>
Cc: jsimmons@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: radeonfb almost there.. but not quite! :)
Date: Thu, 16 Jan 2003 14:27:32 +0100	[thread overview]
Message-ID: <3E26B344.2030400@oracle.com> (raw)
In-Reply-To: <20030115181633.3e058dfd.fscked@netvisao.pt>

Paulo Andre' wrote:
> Hi James,
> 
> First of all, thanks a lot for the amount of work you've been putting
> into the fbdev layer of the linux kernel.
> 
> A few weeks ago I've emailed you about some issues with the radeonfb
> driver on late 2.5 kernels but didn't get any reply from either you or
> Geert. So I'm trying again, providing the (hopefully necessary) input
> for sorting this issue.
> 
> I have an ATI Mobility Radeon 7500 card on a Fujitsu E-7110 laptop and
> the framebuffer console works fine on 2.4 kernels. Not surprising that
> it doesn't work that fine on 2.5 though, considering the new API and all
> the porting that's going on. I compile the radeonfb driver in, selecting
> all the appropriate options as I go along (particularly the Framebuffer
> Console) and upon boot it does detect my card and fb driver just fine,
> along with the appropriate resolution (1400x1050). Here's the snippet
> from 'dmesg':
> 
> radeonfb_pci_register BEGIN
> radeonfb: ref_clk=2700, ref_div=12, xclk=18300 from BIOS
> radeonfb: probed DDR SGRAM 32768k videoram
> radeon_get_moninfo: bios 4 scratch = 1000006
> radeonfb: panel ID string: Samsung LTN150P1-L02    
> radeonfb: detected DFP panel size from BIOS: 1400x1050
> radeonfb: ATI Radeon M7 LW DDR SGRAM 32 MB
> radeonfb: DVI port LCD monitor connected
> radeonfb: CRT port CRT monitor connected
> radeonfb_pci_register END
> 
> Right after detecting this, it tries to display the framebuffer console
> but all I can see is garbage, impossible to read anything, even though
> it keeps booting as usual and I can even (blindly) login and start X
> (though it's all hardware, not framebuffer).
> 

Radeonfb works better for me in 2.5.58, same card but on a
  Dell Latitude C640 - 1024x768 though, and xclk=16600.

I say "better" and not simply "works" because

  - the gpm cursor positioned on characters shows different ones
     (eg. hovering on a 'd' it shows a highlighted 'B')
  - the pre-penguin display is garbage. The console though gets
     to recover right after the penguin display

Definitely usable anyway :)

--alessandro

  "And though it don't seem fair, for every smile that plays
    a tear must fall somewhere"
        (Bruce Springsteen, "The Price You Pay", live 31/12/1980)


  reply	other threads:[~2003-01-16 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 18:16 radeonfb almost there.. but not quite! :) Paulo Andre'
2003-01-16 13:27 ` Alessandro Suardi [this message]
     [not found] <20030115182012$25b7@gated-at.bofh.it>
     [not found] ` <20030116134006$783d@gated-at.bofh.it>
2003-01-16 21:07   ` Arnd Bergmann
2003-01-17 15:31     ` Paulo Andre'
2003-01-17 15:46       ` Arnd Bergmann
2003-01-17 15:59         ` James Simmons
2003-01-17 16:01       ` James Simmons
2003-01-18 12:18         ` Paulo Andre'

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=3E26B344.2030400@oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=fscked@netvisao.pt \
    --cc=jsimmons@infradead.org \
    --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