public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Peter Osterlund <petero2@telia.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Linux 2.6.3-rc3
Date: Sun, 15 Feb 2004 17:05:16 +0100	[thread overview]
Message-ID: <20040215160516.GA7650@louise.pinerecords.com> (raw)
In-Reply-To: <m2znbk4s8j.fsf@p4.localdomain>

On Feb-15 2004, Sun, 10:17 +0100
Peter Osterlund <petero2@telia.com> wrote:

> Linus Torvalds <torvalds@osdl.org> writes:
> 
> > Benjamin Herrenschmidt:
> >   o New radeonfb
> >   o Fix a link conflict between radeonfb and the radeon DRI
> >   o Fix incorrect kfree in radeonfb
> 
> It doesn't seem to work on my x86 laptop. The screen goes black when
> the framebuffer is enabled early in the boot sequence. The machine
> boots normally anyway and I can log in from the network or log in
> blindly at the console.

The same goes for my ThinkPad T40p.  The old driver works ok.

dmesg:
...
Kernel command line: root=/dev/hda3 rw video=radeonfb
...
radeonfb: Invalid ROM signature 0 should be 0xaa55
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=252.00 Mhz, System=200.00 MHz
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: SXGA+ Single (85MHz)    
radeonfb: detected LVDS panel size from BIOS: 1400x1050
radeondb: BIOS provided dividers will be used
radeonfb: Power Management enabled for Mobility chipsets
radeonfb: ATI Radeon Lf  DDR SGRAM 64 MB
...
Console: switching to colour frame buffer device 116x47

-- 
Tomas Szepe <szepe@pinerecords.com>

  parent reply	other threads:[~2004-02-15 16:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15  3:33 Linux 2.6.3-rc3 Linus Torvalds
2004-02-15  7:41 ` 2.6.3-rc3: twice defined symbols with new radeonfb Adrian Bunk
2004-02-15  7:47   ` Benjamin Herrenschmidt
2004-02-15 13:22     ` Adrian Bunk
2004-02-15 19:19       ` Roman Zippel
2004-02-15  9:17 ` Linux 2.6.3-rc3 Peter Osterlund
2004-02-15  9:54   ` Benjamin Herrenschmidt
2004-02-15 10:25     ` Benjamin Herrenschmidt
2004-02-15 10:51       ` Peter Osterlund
2004-02-15 11:11         ` Benjamin Herrenschmidt
2004-02-15 11:21         ` Geert Uytterhoeven
2004-02-15 10:33     ` Peter Osterlund
2004-02-15 15:03   ` Jonathan Brown
2004-02-15 16:05   ` Tomas Szepe [this message]
2004-02-15 16:44   ` Onur Kucuk
2004-02-16 15:58     ` Moritz Muehlenhoff
2004-02-17 16:29       ` Moritz Muehlenhoff
2004-02-15 19:52   ` Ernst Herzberg
2004-02-15 20:11     ` Peter Osterlund
2004-02-15 21:52       ` Ernst Herzberg
2004-02-15 22:29         ` Benjamin Herrenschmidt
     [not found]           ` <200402152357.25751.earny@net4u.de>
2004-02-15 23:08             ` Benjamin Herrenschmidt
     [not found]               ` <200402160033.43438.earny@net4u.de>
2004-02-15 23:54                 ` Benjamin Herrenschmidt
2004-02-16  0:29                   ` Ernst Herzberg
2004-02-16  0:38                     ` Ernst Herzberg
2004-02-16  0:43                       ` Benjamin Herrenschmidt
2004-02-16  1:18                         ` Ernst Herzberg
2004-02-16  1:47                           ` Benjamin Herrenschmidt
2004-02-16  0:41                     ` Benjamin Herrenschmidt
     [not found]                   ` <124101c3f435$9a66d3a0$1225a8c0@kittycat>
2004-02-16  2:37                     ` Benjamin Herrenschmidt
2004-02-15 22:27       ` Benjamin Herrenschmidt
     [not found]         ` <200402160005.47892.anib@uni-paderborn.de>
2004-02-15 23:11           ` Benjamin Herrenschmidt
2004-02-16 19:18 ` Linux 2.6.3-rc3 (compile stats) John Cherry
  -- strict thread matches above, loose matches on Subject: below --
2004-02-16  6:15 Linux 2.6.3-rc3 Jonathan Brown

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=20040215160516.GA7650@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=torvalds@osdl.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