From: me@bobcopeland.com
To: "Николай Ледовских" <nledovskikh@gmail.com>
Cc: linville@tuxdriver.com, ath5k-devel@lists.ath5k.org,
linux-wireless@vger.kernel.org, lrodriguez@atheros.com,
mickflemm@gmail.com, jirislaby@gmail.com
Subject: Re: [PATCH] ath5k: Use mips generic dma-mapping functions to avoid seqfault on AHB chips
Date: Tue, 15 Feb 2011 09:44:45 -0500 [thread overview]
Message-ID: <20110215144445.GA6066@hash.localnet> (raw)
In-Reply-To: <AANLkTinqN4MjWz4y5D195f9J8vob42GsG9u39xX-RuJf@mail.gmail.com>
On Tue, Feb 15, 2011 at 02:29:13PM +0000, Николай Ледовских wrote:
> This patch fixes seqfault on ar2316 and other AHB based chips.
Ok, but I'm guessing it also breaks PCI functionality?
> struct ath5k_softc *sc = common->priv;
> - struct platform_device *pdev = to_platform_device(sc->dev);
> + struct platform_device *pdev =
> to_platform_device(wiphy_dev(sc->hw->wiphy));
Your patch got wrapped strangely here...
> - mem = ioremap_nocache(res->start, res->end - res->start + 1);
> + mem = res->start;
Won't this break iommu platforms?
> + SET_IEEE80211_DEV(hw, &pdev->dev);
>
> - sc->dev = &pdev->dev;
> + sc->dev = NULL;
> /* Initialize driver private data */
> - SET_IEEE80211_DEV(hw, sc->dev);
> @@ -216,6 +216,7 @@ ath5k_pci_probe(struct pci_dev *pdev,
> ret = -ENOMEM;
> goto err_map;
> }
> + SET_IEEE80211_DEV(hw, &pdev->dev);
This set of changes needs some rationale... in other words, what is
the real problem the patch fixes?
--
Bob Copeland %% www.bobcopeland.com
next parent reply other threads:[~2011-02-15 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinqN4MjWz4y5D195f9J8vob42GsG9u39xX-RuJf@mail.gmail.com>
2011-02-15 14:44 ` me [this message]
2011-02-15 14:49 ` [PATCH] ath5k: Use mips generic dma-mapping functions to avoid seqfault on AHB chips Jiri Slaby
2011-02-15 22:05 ` [ath5k-devel] " Hugh Davenport
[not found] <AANLkTi=6jVGZx0oQdMQmndCB9k_xPywfntsB1LS_4ekM@mail.gmail.com>
2011-02-15 18:58 ` John W. Linville
2011-02-15 19:09 Nikolay Ledovskikh
2011-02-15 19:40 ` Jiri Slaby
[not found] ` <AANLkTiks9rG2CzM2LabNerK3zgJ+R+weytQgvXxDbNe7@mail.gmail.com>
2011-02-15 20:42 ` Jiri Slaby
2011-02-15 20:57 ` Nikolay Ledovskikh
2011-02-15 21:03 ` Jiri Slaby
2011-02-15 21:18 ` Nikolay Ledovskikh
2011-02-15 21:39 ` Nikolay Ledovskikh
2011-02-15 22:16 ` Jiri Slaby
2011-02-15 22:18 ` Jiri Slaby
[not found] ` <20110216011203.GA5773@linux-mips.org>
2011-02-16 10:26 ` Nikolay Ledovskikh
2011-02-23 10:18 ` Wojciech Dubowik
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=20110215144445.GA6066@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mickflemm@gmail.com \
--cc=nledovskikh@gmail.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).