public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Edgar Hucek <hostmaster@ed-soft.at>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Edgar Hucek <hostmaster@ed-soft.at>,
	Antonino Daplas <adaplas@pol.net>, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] imacfb: Add Intel-based Macintosh Framebuffer Support
Date: Tue, 27 Jun 2006 08:10:37 +0200	[thread overview]
Message-ID: <44A0CBDD.70104@ed-soft.at> (raw)
In-Reply-To: <20060627000144.GC15047@redhat.com>

At the moment i work on implementing Machine detection through DMI
and make the driver loadable as module. I know that the driver is
not perfekt, but a good starting point :)

cu

Edgar (gimli) Hucek

Dave Jones schrieb:
> On Mon, Jun 26, 2006 at 06:03:02PM +0000, Linux Kernel wrote:
>  > commit 90b4f9aca4d124d114e02bbb3d1d4f3d1d47138f
>  > tree e367b2fd3ad08b706bd7825c6251a95284f3bb76
>  > parent 1a8c9795290361cef232fd54f425a57d143108a8
>  > author Edgar Hucek <hostmaster@ed-soft.at> Mon, 26 Jun 2006 14:26:59 -0700
>  > committer Linus Torvalds <torvalds@g5.osdl.org> Mon, 26 Jun 2006 23:58:32 -0700
>  > 
>  > [PATCH] imacfb: Add Intel-based Macintosh Framebuffer Support
>  > 
>  > This patch adds a new framebuffer driver for the Intel Based macs.  This
>  > framebuffer is needed when booting from EFI to get something out the box.
>  > 
>  > [akpm: note: doesn't support modular building]
> 
> This scares me from a distro kernel point of view too, because
> it does no probing that it's actually running on a mac, (be that
> through DMI strings or PCI idents).  Instead if it hasn't been 
> passed a boot option, it sets model to 'M_NEW'....
> 
>  > +	case M_NEW:
>  > +	case M_I20:
>  > +		screen_info.lfb_width = 1680;
>  > +		screen_info.lfb_height = 1050;
>  > +		screen_info.lfb_linelength = 1728 * 4;
>  > +		screen_info.lfb_base = 0x80010000;
>  > +		break;
> 
> And then assumes it can scribble at 0x80010000.
> 
> Whilst in most cases the request_region that follows is going to fail,
> the possibility exists that something entirely different could be
> mapped there, guaranteeing fun times should Apple ever do something
> silly like, mapping the NVRAM there..
> 
> 		Dave
> 


      reply	other threads:[~2006-06-27  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200606261803.k5QI32W8003539@hera.kernel.org>
2006-06-27  0:01 ` [PATCH] imacfb: Add Intel-based Macintosh Framebuffer Support Dave Jones
2006-06-27  6:10   ` Edgar Hucek [this message]

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=44A0CBDD.70104@ed-soft.at \
    --to=hostmaster@ed-soft.at \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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