From: Edgar Hucek <hostmaster@ed-soft.at>
To: Dennis Munsie <dmunsie@cecropia.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@gmail.com>
Subject: Re: [PATCH 1/1] New Framebuffer for Intel based Macs [try #2] (fwd)
Date: Fri, 23 Jun 2006 06:01:44 +0200 [thread overview]
Message-ID: <449B67A8.70500@ed-soft.at> (raw)
In-Reply-To: <269AA200-402D-4D9B-93AC-773C44F1AF50@cecropia.com>
The driver is needed when making a native EFI boot, it does not work
with BootCamp.
cu
Edgar Hucek
Dennis Munsie schrieb:
> fair enough -- i had thought about it a little more on the way to work,
> and that makes sense. But, once the native drivers work, it would
> probably be a good idea to make note someplace that the other drivers
> would provide better performance than this one.
>
> btw -- the intelfb driver in it's current state might not work on the
> intel macs anyway. The intelfb driver doesn't do well with anything but
> the analog output, and the MacBook and mini both have DVI ports.
>
> another quick question regarding this driver -- is it only needed when a
> native EFI boot is done? or does it also get used when Boot Camp is
> used? I would think that Boot Camp would allow the VESA driver to work,
> since it's purpose is to make it look like the machine has a true x86
> BIOS...
>
> dennis
>
> On Jun 22, 2006, at 7:32 AM, Antonino A. Daplas wrote:
>
>> 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
>>
>
>
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-06-23 4:01 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
2006-06-22 12:43 ` Dennis Munsie
2006-06-23 4:01 ` Edgar Hucek [this message]
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=449B67A8.70500@ed-soft.at \
--to=hostmaster@ed-soft.at \
--cc=adaplas@gmail.com \
--cc=dmunsie@cecropia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.