From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>, dev <dev@dpdk.org>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [dpdk-dev] [kmods PATCH] windows/netuio: add vmxnet3 device ID
Date: Mon, 22 Feb 2021 09:54:13 -0800 [thread overview]
Message-ID: <20210222175413.GA23653@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <CAJFAV8ypKvbKvBeyba+soA2i1gR1ikapGFNMNHbMVFvr=uJFDw@mail.gmail.com>
On Mon, Feb 22, 2021 at 10:20:41AM +0100, David Marchand wrote:
> > diff --git a/windows/netuio/netuio.inf b/windows/netuio/netuio.inf
> > index 666a69c..db97366 100644
> > --- a/windows/netuio/netuio.inf
> > +++ b/windows/netuio/netuio.inf
> > @@ -42,6 +42,7 @@ HKR,,Icon,,-5
> > %Intel.F101F.Description%=netuio_Device, PCI\VEN_8086&DEV_101F
> > %Intel.F104F.Description%=netuio_Device, PCI\VEN_8086&DEV_104F
> > %Intel.F104E.Description%=netuio_Device, PCI\VEN_8086&DEV_104E
> > +%vmxnet3.Description%=netuio_Device, PCI\VEN_15AD&DEV_07B0
> >
>
> Is there no other way than hardcoding those values in the driver?
> Something à la driverctl?
This is how support for vendor / device is expressed for a driver
to the Windows PnP subsystem. The device ids listed in the .inf
file are used to match the driver when the device is enumerated.
It's not really hardcoded though (not compiled anyway) so the list
of ids in a .inf can be changed without recompiled it is just a text
file.
>
>
> --
> David Marchand
next prev parent reply other threads:[~2021-02-22 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 0:51 Dmitry Kozlyuk
2021-02-22 9:20 ` David Marchand
2021-02-22 17:54 ` Tyler Retzlaff [this message]
2021-03-01 21:51 ` Nick Connolly
2021-03-17 9:54 ` Thomas Monjalon
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=20210222175413.GA23653@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
/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).