linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: RSmith@bitworks.com
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	James Simmons <jsimmons@infradead.org>,
	Alexander Kern <alex.kern@gmx.de>, Jon Smirl <jonsmirl@yahoo.com>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: still ..Confused about atyfb and M1
Date: Thu, 05 Feb 2004 10:29:27 +1100	[thread overview]
Message-ID: <1075937366.4029.43.camel@gaston> (raw)
In-Reply-To: <40210D52.5020009@bitworks.com>

On Thu, 2004-02-05 at 02:18, Richard Smith wrote:
> Geert Uytterhoeven wrote:
> 
> > Indeed, atyfb needs BIOS (or OpenFirmware) initialization. It has
> > initialization code for RAGE XL, though.
> 
> Does OpenFirmware support exist for the M1?

Some iBooks ship with an M1, those have an OF driver

Ben.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-02-04 23:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17  0:23 Fwd: [PATCH] ATI Mach64 accelerated imgblit (sligthly improved) Alexander Kern
2004-01-17  4:26 ` Confused about atyfb status Richard Smith
2004-01-17  6:38   ` Jon Smirl
2004-01-17  7:31     ` Richard Smith
2004-01-17 12:03     ` Alexander Kern
2004-01-18 22:52       ` Benjamin Herrenschmidt
2004-01-20  1:48         ` still ..Confused about atyfb and M1 Richard Smith
2004-01-28  0:07           ` Richard Smith
2004-01-30 21:47             ` James Simmons
2004-02-03 19:16               ` Richard Smith
2004-02-04  9:06                 ` Geert Uytterhoeven
2004-02-04 15:16                   ` Richard Smith
2004-02-04 15:35                     ` Geert Uytterhoeven
2004-02-05 17:55                       ` Richard Smith
2004-02-05 20:16                         ` Geert Uytterhoeven
2004-02-05 21:37                           ` Richard Smith
2004-02-05 22:57                             ` Benjamin Herrenschmidt
2004-02-06  0:22                               ` Richard Smith
2004-02-06  9:17                             ` Geert Uytterhoeven
2004-02-06 20:13                               ` Richard Smith
2004-02-07 17:54                                 ` Geert Uytterhoeven
2004-02-08 20:42                                   ` Alexander Kern
2004-02-09 22:51                                   ` Richard Smith
2004-02-06 23:30                         ` James Simmons
2004-02-06 23:42                           ` Richard Smith
2004-02-04 15:18                   ` Richard Smith
2004-02-04 15:36                     ` Geert Uytterhoeven
2004-02-04 23:29                     ` Benjamin Herrenschmidt [this message]
2004-02-03 22:18               ` Richard Smith
2004-01-17 18:36   ` Confused about atyfb status 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=1075937366.4029.43.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=RSmith@bitworks.com \
    --cc=alex.kern@gmx.de \
    --cc=geert@linux-m68k.org \
    --cc=jonsmirl@yahoo.com \
    --cc=jsimmons@infradead.org \
    --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).