From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: Kalle Valo <kvalo@adurom.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210
Date: Tue, 13 Nov 2012 20:39:42 +0100 [thread overview]
Message-ID: <1352835582.9466.12.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <2199722.SIyuOP2QQY@lx-vladimir>
On Mon, 2012-11-12 at 19:58 +0200, Vladimir Kondratiev wrote:
> Yes, it make sense. I noticed also I have to use __raw_{read|write}l functions
> to copy buffers to/from PCI iomem, as otherwise io{read|write}32 would swap
> bytes for big endian hosts, since PCI is little endian.
No, this is what you want, they simple read/write host endian (u32)
values.
johannes
next prev parent reply other threads:[~2012-11-13 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 16:36 [PATCH v5 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-10-31 16:36 ` [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-11-08 19:29 ` Luis R. Rodriguez
2012-11-11 16:15 ` Vladimir Kondratiev
2012-11-12 17:22 ` Kalle Valo
2012-11-12 17:58 ` Vladimir Kondratiev
2012-11-13 19:39 ` Johannes Berg [this message]
2012-11-09 8:39 ` 60 GHz interface types (was: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210) Johannes Berg
2012-11-11 8:15 ` Vladimir Kondratiev
2012-11-11 13:42 ` Johannes Berg
2012-11-11 16:53 ` Vladimir Kondratiev
2012-11-12 10:15 ` Johannes Berg
2012-11-12 10:24 ` Johannes Berg
2012-11-12 14:57 ` Vladimir Kondratiev
2012-11-12 15:17 ` Johannes Berg
2012-11-12 15:01 ` Vladimir Kondratiev
2012-11-12 17:22 ` Vladimir Kondratiev
2012-10-31 16:36 ` [PATCH v5 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev
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=1352835582.9466.12.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@do-not-panic.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.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