From: "Rafał Miłecki" <zajec5@gmail.com>
To: George Kashperko <george@znau.edu.ua>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Michael Büsch" <mb@bu3sch.de>,
b43-dev@lists.infradead.org,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: [RFC][PATCH] ssb: separate common scanning functions
Date: Fri, 18 Mar 2011 22:52:59 +0100 [thread overview]
Message-ID: <AANLkTi=1XOxwS4tMc6eMcNGeHf_ZGaAH5MC97JsP7oWP@mail.gmail.com> (raw)
In-Reply-To: <1300478510.15393.45.camel@dev.znau.edu.ua>
2011/3/18 George Kashperko <george@znau.edu.ua>:
> ?- read pci revision id/vendor id (pci_read_config_word), if required
> to decide if second window is sliding or sprom (actually rev_id should
> be sufficient for that) read offset 0x0000 from bar0 offset to get
> chipid register value
Could you say something about WIN1 and WIN2? What are they for, can we
use them somehow separately? What do you mean by second window being
SPROM? We read sprom without any special window magic:
sprom[i] = ioread16(bus->mmio + bus->sprom_offset + (i * 2));
My understanding is limited to that:
If we want to use device with CORE_ADDR and WRAP_ADDR we have to write
CORE_ADDR to BAR0_WIN and WRAP_ADDR to BAR0_WIN2. Then we can use
readl/writel.
--
Rafa?
next prev parent reply other threads:[~2011-03-18 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 12:02 [RFC][PATCH] ssb: separate common scanning functions Rafał Miłecki
[not found] ` <1300453433.13499.18.camel@dev.znau.edu.ua>
2011-03-18 14:10 ` Rafał Miłecki
2011-03-18 14:50 ` Rafał Miłecki
[not found] ` <1300463392.13499.110.camel@dev.znau.edu.ua>
2011-03-18 16:25 ` Rafał Miłecki
2011-03-18 17:13 ` Larry Finger
[not found] ` <1300471917.14872.28.camel@dev.znau.edu.ua>
2011-03-18 19:04 ` Rafał Miłecki
[not found] ` <1300478510.15393.45.camel@dev.znau.edu.ua>
2011-03-18 21:52 ` Rafał Miłecki [this message]
[not found] ` <1300488010.16395.37.camel@dev.znau.edu.ua>
2011-03-18 23:06 ` Rafał Miłecki
[not found] ` <1300490544.16395.50.camel@dev.znau.edu.ua>
2011-03-18 23:32 ` Rafał Miłecki
[not found] ` <1300460342.13499.60.camel@dev.znau.edu.ua>
2011-03-18 15:17 ` Rafał Miłecki
[not found] ` <1300463925.13499.118.camel@dev.znau.edu.ua>
2011-03-18 16:04 ` Rafał Miłecki
2011-03-18 20:26 ` Rafał Miłecki
[not found] ` <1300483139.15919.42.camel@dev.znau.edu.ua>
2011-03-18 22:42 ` Rafał Miłecki
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='AANLkTi=1XOxwS4tMc6eMcNGeHf_ZGaAH5MC97JsP7oWP@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=george@znau.edu.ua \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).