linux-kernel - Re: [PATCH] drm/cirrus: bind also to qemu-xen-traditional

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141022081429.GA21955@aepfle.de>
Date:	Wed, 22 Oct 2014 10:14:29 +0200
From:	Olaf Hering <olaf@...fle.de>
To:	airlied@...ux.ie
Cc:	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/cirrus: bind also to qemu-xen-traditional

Ping?

On Tue, Aug 26, Olaf Hering wrote:

> Ping?
> 
> On Thu, Jun 12, Olaf Hering wrote:
> 
> > Ping?
> > 
> > On Fri, Apr 11, Olaf Hering wrote:
> > 
> > > qemu as used by xend/xm toolstack uses a different subvendor id.
> > > Bind the drm driver also to this emulated card.
> > > 
> > > Signed-off-by: Olaf Hering <olaf@...fle.de>
> > > ---
> > >  drivers/gpu/drm/cirrus/cirrus_drv.c | 2 ++
> > >  1 file changed, 2 insertions(+)
> > > 
> > > diff --git a/drivers/gpu/drm/cirrus/cirrus_drv.c b/drivers/gpu/drm/cirrus/cirrus_drv.c
> > > index 953fc8a..8555548 100644
> > > --- a/drivers/gpu/drm/cirrus/cirrus_drv.c
> > > +++ b/drivers/gpu/drm/cirrus/cirrus_drv.c
> > > @@ -31,6 +31,8 @@ static struct drm_driver driver;
> > >  static DEFINE_PCI_DEVICE_TABLE(pciidlist) = {
> > >  	{ PCI_VENDOR_ID_CIRRUS, PCI_DEVICE_ID_CIRRUS_5446, 0x1af4, 0x1100, 0,
> > >  	  0, 0 },
> > > +	{ PCI_VENDOR_ID_CIRRUS, PCI_DEVICE_ID_CIRRUS_5446, PCI_VENDOR_ID_XEN,
> > > +	  0x0001, 0, 0, 0 },
> > >  	{0,}
> > >  };
> > >  
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/