From: Tom Rix <trix@redhat.com>
To: matthew.gerlach@linux.intel.com
Cc: linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
mdf@kernel.org, hao.wu@intel.com, linux-doc@vger.kernel.org,
corbet@lwn.net
Subject: Re: [PATCH 2/2] fpga: dfl: look for vendor specific capability
Date: Tue, 17 Nov 2020 17:29:51 -0800 [thread overview]
Message-ID: <2a81ac9c-482e-c0ec-ea71-d811fdf8a01a@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2011171457150.312724@rhweight-WRK1>
>> Is this really an either/or ?
>>
>> Could there be a base functionality on bar0 and a skew functionality on vendor bars?
>
> For simplicity I think either or is better. If skew functionality is in vendor bars, why not just use the vendor bars all the time.
>
>>
>> If vendor is going to completely override, why not use bar0 ?
>
> I'm not sure I understand the question, but in v2 the legacy DFL search will only occur if there is no VSEC found.
>
Wondering if vsec was ignored, would the bar0 work ?
Or another way, how badly would an old driver behave.
consider incrementing the driver version if it would be bad.
Tom
>>
>> Tom
>>
>>>
>>> if (ret)
>>> goto irq_free_exit;
>>
>>
>
prev parent reply other threads:[~2020-11-18 1:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 1:25 [PATCH 0/2] fpga: dfl: optional VSEC for start of dfl matthew.gerlach
2020-11-17 1:25 ` [PATCH 1/2] fpga: dfl: refactor cci_enumerate_feature_devs() matthew.gerlach
2020-11-17 10:05 ` Wu, Hao
2020-11-17 18:05 ` matthew.gerlach
2020-11-17 20:01 ` Tom Rix
2020-11-17 1:25 ` [PATCH 2/2] fpga: dfl: look for vendor specific capability matthew.gerlach
2020-11-17 7:56 ` Xu Yilun
2020-11-17 10:00 ` Wu, Hao
2020-11-17 19:41 ` matthew.gerlach
2020-11-18 6:19 ` Xu Yilun
2020-11-17 9:47 ` Wu, Hao
2020-11-17 20:09 ` matthew.gerlach
2020-11-18 1:54 ` Wu, Hao
2020-11-18 17:49 ` matthew.gerlach
2020-11-17 14:33 ` kernel test robot
2020-11-17 20:35 ` Tom Rix
2020-11-17 23:10 ` matthew.gerlach
2020-11-18 1:29 ` Tom Rix [this message]
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=2a81ac9c-482e-c0ec-ea71-d811fdf8a01a@redhat.com \
--to=trix@redhat.com \
--cc=corbet@lwn.net \
--cc=hao.wu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.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 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).