linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore it
Date: Fri, 7 Dec 2007 22:50:25 +0000	[thread overview]
Message-ID: <20071207225025.GA2055@srcf.ucam.org> (raw)
In-Reply-To: <1197032113.28990.155.camel@queen.suse.de>

On Fri, Dec 07, 2007 at 01:55:13PM +0100, Thomas Renninger wrote:
> Hi Matthew,
> 
> I posted this one already and you had some concerns about it:
> http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg09510.html
> 
> IMO, this one should still be added to -mm, because:
>   - The patch itself is correct, it is the function that is called
>     that must make sure to return the corresponding pci device

No, I don't think that follows. The semantics of 
acpi_get_physical_device are currently to return a physical device only 
if the node directly corresponds to one. What's the correct physical 
device for the video extension? It may be a PCI device, but it's just as 
easy to argue that it corresponds to some piece of platform-specific 
hardware.

We could change the semantics and ensure that all leaf nodes of an ACPI 
node representing a PCI device share the same physical device. That 
would avoid the bug your patch currently introduces of ignoring 
functional devices, but would immediately cause the second video device 
to reappear on Thinkpads.

Incidentally, have you tried this on a Thinkpad with a discrete graphics 
controller? I /suspect/ (but can't verify) that you'll end up discarding 
the working video extension.

In summary, I don't think this approach can be made to work. You're 
throwing out legitimate and working devices. Instead, we should export 
information about the addresses of the video extensions and let 
whoever's handling the graphics (which is userspace right now) handle 
it.
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2007-12-07 22:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 12:55 [PATCH] Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore it Thomas Renninger
2007-12-07 15:27 ` Thomas Renninger
2007-12-07 22:50 ` Matthew Garrett [this message]
2007-12-10 12:48   ` Thomas Renninger
2008-01-17  3:11     ` Matthew Garrett
2008-01-17  3:39       ` [PATCH] Ignore ACPI video devices that aren't present in hardware Matthew Garrett
2008-01-17 10:57         ` Thomas Renninger
2008-01-17 12:02           ` Matthew Garrett
2008-01-22  8:52             ` Zhang Rui
2008-01-22 12:11               ` Julian Sikorski
2008-01-24 22:21         ` Len Brown
2008-01-27  2:09           ` Matthew Garrett
2008-02-02  7:12             ` Len Brown
2008-02-03  0:03               ` Matthew Garrett
2008-02-07  1:44                 ` Matthew Garrett
2008-02-07  7:03                   ` Len Brown

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=20071207225025.GA2055@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=akpm@osdl.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=trenn@suse.de \
    /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).