On Tue, Jul 7, 2009 at 9:34 AM, Marc Jones <marcj303@gmail.com> wrote:

On Tue, Jul 7, 2009 at 9:28 AM, Myles Watson<mylesgw@gmail.com> wrote:
>> That seems like a defective card but something is strange. Why
>> wouldn't it detect the functions when the first function was enabled?
>
> It doesn't probe the other functions when the first function is enabled
> because it is not a multi-function device. It reads that from the config
> space and skips to the next slot.

Ah, OK. Maybe we should make the scan a little smarter by checking the
device capability and skip to the next device instead of next
function.

That would work in my situation. I guess I was also asking what it means for a device to be disabled. Does that mean that we don't touch it at all? Should we read config space values from a disabled device?

Maybe it's too much of a corner case to worry about. Disabling all 8 functions isn't too much of a pain.

Thanks,
Myles