From: Peter Jones <pjones@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Make efifb check that the base address is plausible on pci systems.
Date: Mon, 13 Sep 2010 10:42:27 -0400 [thread overview]
Message-ID: <4C8E3853.70702@redhat.com> (raw)
In-Reply-To: <20100910171406.bdb4d90d.akpm@linux-foundation.org>
On 09/10/2010 08:14 PM, Andrew Morton wrote:
> On Thu, 9 Sep 2010 15:16:48 -0400
> Peter Jones <pjones@redhat.com> wrote:
>
>> Some Apple machines have identical DMI data but different memory
>> configurations for the video. Given that, check that the address in our
>> table is actually within the range of a PCI BAR on a VGA deivce in the
>> machine.
>>
>> This also fixes up the return value from set_system(), which has
>> always been wrong, but never resulted in bad behavior since there's only
>> ever been one matching entry in the dmi table.
>>
>> This also adds me as the efifb maintainer, since I've effectively been
>> acting as such for quite some time.
>
> And what is the impact (and importance) of this patch? Make some
> people's Mac displays work, I'd be guessing?
>
That's correct.
--
Peter
Gravity is a habit that is hard to shake off.
-- Pratchett
01234567890123456789012345678901234567890123456789012345678901234567890123456789
next prev parent reply other threads:[~2010-09-13 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 19:16 [PATCH 1/2] Make efifb check that the base address is plausible on pci systems Peter Jones
2010-09-09 19:16 ` [PATCH 2/2] efifb: support the EFI framebuffer on more Apple hardware Peter Jones
2010-09-11 0:14 ` [PATCH 1/2] Make efifb check that the base address is plausible on pci systems Andrew Morton
2010-09-13 14:42 ` Peter Jones [this message]
2010-09-13 14:52 ` Peter Jones
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=4C8E3853.70702@redhat.com \
--to=pjones@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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