Author Topic: bInterfaceNumber - does IF0 have to exist?  (Read 10087 times)

roger

  • Member
  • ***
  • Posts: 1
bInterfaceNumber - does IF0 have to exist?
« on: September 29, 2010, 06:57:33 pm »
Hi,

bInterfaceNumber is described as "Zero-based value identifying the index in the array of concurrent interfaces supported by this configuration."

My question is if it is valid to have non-contiguous interface numbers?

If I have three interfaces, which of the following respective values for bInterfaceNumber is valid:

* 0, 1, 2
* 1, 2, 0
* 1, 2, 4


Jan Axelson

  • Administrator
  • Frequent Contributor
  • *****
  • Posts: 3033
    • Lakeview Research
Re: bInterfaceNumber - does IF0 have to exist?
« Reply #1 on: September 30, 2010, 08:28:08 pm »
Check the class specification or driver documentation for any limitations on this.

Jan

Guido Koerber

  • Frequent Contributor
  • ****
  • Posts: 72
Re: bInterfaceNumber - does IF0 have to exist?
« Reply #2 on: October 01, 2010, 03:14:03 am »
Having non-continous numbers is fine by the spec but may not be with the driver. I remember that I had problems with some version of Windows that did not work with non-continous interface numbers, though can't recall the details.

Bret

  • Frequent Contributor
  • ****
  • Posts: 68
Re: bInterfaceNumber - does IF0 have to exist?
« Reply #3 on: October 01, 2010, 01:53:22 pm »
Unless you have a REALLY good reason to not number them sequentially starting with zero, that would be the way to do it.  You will likely save yourself all kinds of grief and compatibility problems in the future if you do it that way, even if a particular specification or driver says you don't need to.