linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Kranzkowski <dl8bcu@dl8bcu.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: fbdv/fbcon pending problems
Date: Mon, 23 Feb 2004 20:35:28 +0000	[thread overview]
Message-ID: <20040223203528.E433@Marvin.DL8BCU.ampr.org> (raw)
In-Reply-To: <1077497593.5960.28.camel@gaston>; from benh@kernel.crashing.org on Mon, Feb 23, 2004 at 11:53:14AM +1100

On Mon, Feb 23, 2004 at 11:53:14AM +1100, Benjamin Herrenschmidt wrote:
>  - mach64 lockups on LT-G (I'll try on an LT-Pro soon) plus other
> mach64 bugs in the new version in the bk fbdev, I'll have a patch for
> some of the problems, but I didn't find a good explanation for the
> accel lockups yet

Question: Is fbdev supposed to work without BIOS? 

I have an ATI Technologies Inc 3D Rage Pro 215GP in an Alpha AXPpci33,
currently running with MILO as firmware/bootloader. 
For several reasons I want to change to the original SRM firmware. 
Unfortunately its intel_cpu/BIOS emulation locks up on the ATI BIOS. With
the BIOS disabled the SRM succeeds loading the kernel. fbdev seems to
initialize _something_, i.e. the monitor wakes up ans displays a stable
repeating pattern of vertical stripes. But it hangs the machine after
these lines on serial console:

fb0: ATY Mach64 frame buffer device on PCI
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

Booting the same kernel image (2.6.[13]) with MILO (which has a different
cpu emulation that succeeds executing the BIOS) works fine with fbdev. 

Bye,
Thorsten

-- 
| Thorsten Kranzkowski        Internet: dl8bcu@dl8bcu.de                      |
| Mobile: ++49 170 1876134       Snail: Kiebitzstr. 14, 49324 Melle, Germany  |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org [44.130.8.19] |

  parent reply	other threads:[~2004-02-23 20:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  0:53 fbdv/fbcon pending problems Benjamin Herrenschmidt
2004-02-23 15:52 ` Johannes Stezenbach
2004-02-23 18:59 ` James Simmons
2004-02-23 22:50   ` Benjamin Herrenschmidt
2004-02-24  1:19     ` James Simmons
2004-02-24  8:37     ` Geert Uytterhoeven
2004-02-24  8:33       ` Benjamin Herrenschmidt
2004-02-23 20:35 ` Thorsten Kranzkowski [this message]
2004-02-23 22:18   ` James Simmons
2004-02-24  2:37 ` Otto Solares
2004-02-24  8:35   ` Geert Uytterhoeven
2004-02-24 17:21     ` [Linux-fbdev-devel] " James Simmons
2004-02-24 21:41     ` Otto Solares
2004-02-25  1:21       ` James Simmons
2004-02-25  1:26         ` Benjamin Herrenschmidt
2004-02-25 21:24           ` James Simmons
2004-02-25 23:46             ` Benjamin Herrenschmidt
2004-02-26  0:20               ` James Simmons
2004-02-26  0:33                 ` Benjamin Herrenschmidt
2004-02-26  1:11                   ` [Linux-fbdev-devel] " James Simmons
2004-02-25  1:29         ` Benjamin Herrenschmidt
2004-02-25  2:18           ` Otto Solares
2004-02-25  2:33             ` Benjamin Herrenschmidt
2004-02-25  3:15         ` Otto Solares
2004-02-25 11:41           ` Geert Uytterhoeven
2004-02-25 14:01             ` Sven Luther
2004-02-25 14:08               ` Geert Uytterhoeven
2004-02-25 21:43             ` James Simmons
2004-02-26 19:40             ` Otto Solares
2004-02-26 19:45               ` James Simmons
2004-02-26 20:12                 ` Otto Solares
2004-02-25 21:42           ` James Simmons
2004-02-26 15:26           ` [Linux-fbdev-devel] " Michel Dänzer
2004-02-24  5:57 ` Stuart Young
2004-02-24  8:36   ` Geert Uytterhoeven
2004-02-25  7:14     ` Stuart Young
2004-02-26 15:11       ` [Linux-fbdev-devel] " Michel Dänzer

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=20040223203528.E433@Marvin.DL8BCU.ampr.org \
    --to=dl8bcu@dl8bcu.de \
    --cc=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).