From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alexei Podtelezhnikov <apodtele@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [patch] PCI ID review
Date: Mon, 27 Apr 2020 10:07:06 -0700 [thread overview]
Message-ID: <20200427170706.GB3697495@intel.com> (raw)
In-Reply-To: <CAJU=AjX8Mhy-KG27r_iQOeuRZ3PtPp9F2TUvA7BL+nNsJEzp1Q@mail.gmail.com>
On Mon, Apr 27, 2020 at 11:18:46AM -0400, Alexei Podtelezhnikov wrote:
> On Mon, Apr 27, 2020 at 10:45 AM Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > Quoting Alexei Podtelezhnikov (2020-04-27 15:40:42)
> > > >
> > > > These do not exist. They are fake PCI-ID for Windows95 multi monitor.
> > > > The single device appears twice on the bus as a second function. We
> > > > never had that restriction and could do multiple monitors on the single
> > > > device.
> > >
> > > Windows 10 drivers list them, they do show up on lspci and I'll quote
> > > from Atom datasheet.
> > > "This register is unique in Function 1 (the Function 0 DID is
> > > separate). This difference in Device ID is necessary for allowing
> > > distinct Plug and Play enumeration of function 1 when both function 0
> > > and function 1 have the same class code."
> > > Whatever this means.
> >
> > It means it's a hack for the Window's driver. There is no HW behind it.
>
> Intel talks about two separate engines (threads?)
> https://www.intel.com/content/www/us/en/support/articles/000005880/graphics-drivers/legacy-graphics.html
> https://www.intel.com/content/www/us/en/support/articles/000005747/graphics-drivers.html
> Still not buying?
Hi Alexei, thanks for these.
With this information in mind it looks very wrong to simply add the PCI ID.
ADD2 device is not supported by i915. I don't believe it will be as simple
as just adding the PCI ID here.
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-27 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 3:22 [Intel-gfx] [patch] PCI ID review Alexei Podtelezhnikov
2020-04-27 3:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-04-27 4:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-04-27 5:52 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-04-27 14:02 ` [Intel-gfx] [patch] " Ville Syrjälä
2020-04-27 14:14 ` Chris Wilson
2020-04-27 14:40 ` Alexei Podtelezhnikov
2020-04-27 14:45 ` Chris Wilson
2020-04-27 15:18 ` Alexei Podtelezhnikov
2020-04-27 17:07 ` Rodrigo Vivi [this message]
2020-04-27 22:14 ` Ville Syrjälä
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=20200427170706.GB3697495@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=apodtele@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.