From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>
Cc: Kostas Gewrgiou <gewrgiou@imbc.gr>,
Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: beige g3 rage II xf4.0.1 and miBoot
Date: Mon, 02 Oct 2000 11:52:16 +0200 [thread overview]
Message-ID: <39D85AD0.D2B28422@student.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10010011902590.1560-100000@zirkon.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
>
> > > Did you try with a framebuffer (vesafb for instance) on x86, and the
> > > UseFBDev option? Did anyone ever try?
> >
> > Yeap i tried it with aty128fb (long time ago), without busID set
> > everything works you don't get anything in the screen, no panics/locks as
> > in the ppc side.
>
> Which isn't exactly the same because the problem only manifests with
> conflicting PCI resources set up before the kernel starts. And that -so
> far- only happened with some Mach64 based Macs.
>
> aty128fb not having any problem doesn't prove atyfb can't have these
> problems on Intel, too.
AFAIK Kostas was talking about the problem that if you don't specify the bus
ID when using an fbdev driver, X disables the graphics chip because no driver
claims it. And he wondered why this locks the machine on PPC while it only
makes the server fail on i386. Right, Kostas?
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-02 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-28 15:03 beige g3 rage II xf4.0.1 and miBoot R Shapiro
2000-09-28 17:23 ` Kostas Gewrgiou
2000-09-28 19:25 ` Geert Uytterhoeven
2000-09-28 21:07 ` Michel Lanners
2000-09-28 22:57 ` Benjamin Herrenschmidt
2000-09-29 19:27 ` Michael Schmitz
2000-09-29 17:33 ` Michael Schmitz
2000-09-29 19:09 ` Michel Dänzer
2000-09-29 19:44 ` Michael Schmitz
2000-09-30 13:51 ` Kostas Gewrgiou
2000-10-01 17:05 ` Michael Schmitz
2000-10-02 9:52 ` Michel Dänzer [this message]
2000-10-02 13:24 ` Michael Schmitz
2000-09-28 21:31 ` Claus
2000-09-28 21:59 ` R Shapiro
2000-09-29 7:51 ` Timothy A. Seufert
2000-09-29 2:13 ` Ethan Benson
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=39D85AD0.D2B28422@student.ethz.ch \
--to=daenzerm@student.ethz.ch \
--cc=gewrgiou@imbc.gr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=schmitz@zirkon.biophys.uni-duesseldorf.de \
/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).