linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: yi.zhu@intel.com, reinette.chatre@intel.com,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: iwl + iomap + readl/writel
Date: Tue, 12 Aug 2008 22:48:52 +0200	[thread overview]
Message-ID: <48A1F734.7040801@gmail.com> (raw)

Hi,

I spotted that iwl drivers use readl method on an iomap space. IIRC some archs 
might return a tag instead of an address expected by readl/writel.

I think you should either switch to ioread32/iowrite32 or to ioremap.

             reply	other threads:[~2008-08-12 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 20:48 Jiri Slaby [this message]
2008-08-12 21:49 ` iwl + iomap + readl/writel Tomas Winkler
2008-08-12 21:54   ` Jiri Slaby
2008-08-12 21:57     ` Tomas Winkler
2008-08-12 21:58       ` Jiri Slaby
2008-08-12 22:04         ` Tomas Winkler

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=48A1F734.7040801@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@intel.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).