linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Dennis Munsie <dmunsie@cecropia.com>,
	Edgar Hucek <hostmaster@ed-soft.at>
Subject: Re: [PATCH 1/1] New Framebuffer for Intel based Macs [try #2] (fwd)
Date: Thu, 22 Jun 2006 19:32:44 +0800	[thread overview]
Message-ID: <449A7FDC.2030304@gmail.com> (raw)
In-Reply-To: <9D874D8E-7EF1-4C29-98F2-AEDFD78C6676@cecropia.com>

Dennis Munsie wrote:
> Why is a new framebuffer driver required in this case? 

It is a platform driver, much like vga16fb and vesafb are for
x86. They are backup drivers.

> Why not use  
> the intelfb driver for the mini and the MacBook and an ati driver for  
> the iMac and the MacBook Pro?

The same reason that people use vesafb because the chipset-specific
driver either conflicts with X or does not work.

Tony

All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642

  reply	other threads:[~2006-06-22 11:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  8:38 [PATCH 1/1] New Framebuffer for Intel based Macs [try #2] (fwd) Geert Uytterhoeven
2006-06-22  8:52 ` Torgeir Veimo
2006-06-22 10:35   ` Edgar Hucek
2006-06-22 11:24 ` Dennis Munsie
2006-06-22 11:32   ` Antonino A. Daplas [this message]
2006-06-22 12:43     ` Dennis Munsie
2006-06-23  4:01       ` Edgar Hucek
2006-06-22 12:02 ` Aurelien Jacobs
2006-06-22 12:23   ` Malcolm

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=449A7FDC.2030304@gmail.com \
    --to=adaplas@gmail.com \
    --cc=dmunsie@cecropia.com \
    --cc=hostmaster@ed-soft.at \
    --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).