From: Alex Deucher <alexdeucher@gmail.com>
To: aaron.ma@canonical.com
Cc: Dave Airlie <airlied@linux.ie>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Gustavo Padovan <gustavo@padovan.org>
Subject: Re: [PATCH 2/2] vgaarb: Keep adding VGA device in queue
Date: Wed, 12 Sep 2018 16:21:53 -0400 [thread overview]
Message-ID: <CADnq5_P=_Kxg8y48NRQZjKzPi-yaAwKRQhpQ6qEav2rZijHucw@mail.gmail.com> (raw)
In-Reply-To: <1535739600-8842-2-git-send-email-aaron.ma@canonical.com>
On Fri, Aug 31, 2018 at 5:39 PM Aaron Ma <aaron.ma@canonical.com> wrote:
>
> If failed to find the deivice owning the boot framebuffer,
> try to use the first VGA device instead of the last one.
>
> Usually the 1st device is integrated GPU who owns the boot framebuffer.
>
> Signed-off-by: Aaron Ma <aaron.ma@canonical.com>
Series is:
Acked-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> drivers/gpu/vga/vgaarb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/vga/vgaarb.c b/drivers/gpu/vga/vgaarb.c
> index 8d90e66994b0..dc8e039bfab5 100644
> --- a/drivers/gpu/vga/vgaarb.c
> +++ b/drivers/gpu/vga/vgaarb.c
> @@ -676,7 +676,7 @@ static bool vga_arbiter_add_pci_device(struct pci_dev *pdev)
> vga_arbiter_check_bridge_sharing(vgadev);
>
> /* Add to the list */
> - list_add(&vgadev->list, &vga_list);
> + list_add_tail(&vgadev->list, &vga_list);
> vga_count++;
> vgaarb_info(&pdev->dev, "VGA device added: decodes=%s,owns=%s,locks=%s\n",
> vga_iostate_to_str(vgadev->decodes),
> --
> 2.17.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-12 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 18:19 [PATCH 1/2] vgaarb: Add support for 64-bit frame buffer address Aaron Ma
2018-08-31 18:20 ` [PATCH 2/2] vgaarb: Keep adding VGA device in queue Aaron Ma
2018-09-12 20:21 ` Alex Deucher [this message]
2018-10-13 16:09 ` Aaron Ma
2018-10-20 6:56 ` Aaron Ma
2018-10-23 5:23 ` Daniel Vetter
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='CADnq5_P=_Kxg8y48NRQZjKzPi-yaAwKRQhpQ6qEav2rZijHucw@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=aaron.ma@canonical.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.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;
as well as URLs for NNTP newsgroup(s).