From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath5k-devel@lists.ath5k.org, Matthew Wilcox <matthew@wil.cx>,
Stephen Hemminger <shemminger@vyatta.com>,
Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: pci_set_mwi() and ath5k
Date: Wed, 4 Nov 2009 13:52:06 -0800 [thread overview]
Message-ID: <43e72e890911041352i334e170at71a519383d48a08@mail.gmail.com> (raw)
In-Reply-To: <43e72e890911041336n7ffae0d2u135321a588f3e613@mail.gmail.com>
On Wed, Nov 4, 2009 at 1:36 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Wed, Nov 4, 2009 at 1:30 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> On Wed, Nov 4, 2009 at 12:12 PM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>>> 2009/11/4 Luis R. Rodriguez <mcgrof@gmail.com>:
>>>> Curious if anyone recalls the issues seen with enabling MWI on ath5k.
>>>> I could have sworn there was some discussion on this but for the life
>>>> of me I cannot find it.
>>>>
>>>> Luis
>>>
>>> Maybe this one ?
>>> http://osdir.com/ml/linux.drivers.ath5k.devel/2008-07/msg00088.html
>>
>> That was it, thanks! For the record then Kyle pointed to this bug:
>>
>> http://marc.info/?t=121430463700001&r=1&w=2
>>
>> as a reference for possible issues.
>
> Actually the threads above are for MSI, not MWI, which would be set
> with pci_set_mwi() not pci_disable_msi().
>
> MWI is for enabling memory write invalidate.
>
> I guess we never had the MWI discussion then for ath5k,
>
> Either way I'm reluctant to enable it and was actually considering
> simplifying the the PCI cache line size thing on ath/ath5k/ath9k. Will
> send an RFC.
Even better: I just confirmation from our systems team that our legacy
devices and 11n PCI devices don't support MWR so I'll remove all that
cruft crap.
Luis
next prev parent reply other threads:[~2009-11-04 21:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 20:04 pci_set_mwi() and ath5k Luis R. Rodriguez
2009-11-04 20:12 ` Nick Kossifidis
2009-11-04 21:30 ` Luis R. Rodriguez
2009-11-04 21:36 ` Luis R. Rodriguez
2009-11-04 21:52 ` Luis R. Rodriguez [this message]
2009-11-04 21:52 ` Luis R. Rodriguez
2009-11-04 22:00 ` Matthew Wilcox
2009-11-04 22:04 ` Luis R. Rodriguez
2009-11-04 22:14 ` Luis R. Rodriguez
2009-11-04 22:28 ` Luis R. Rodriguez
2009-11-04 22:29 ` Matthew Wilcox
2009-11-04 22:39 ` Luis R. Rodriguez
2009-11-04 22:31 ` Nick Kossifidis
2009-11-04 22:45 ` Luis R. Rodriguez
2009-11-04 22:47 ` Luis R. Rodriguez
2009-11-04 23:14 ` Luis R. Rodriguez
2009-11-05 0:16 ` Nick Kossifidis
2009-11-05 2:55 ` Bob Copeland
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=43e72e890911041352i334e170at71a519383d48a08@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=kyle@mcmartin.ca \
--cc=linux-wireless@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mickflemm@gmail.com \
--cc=shemminger@vyatta.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