From: Krzysztof Halasa <khc@pm.waw.pl>
To: Karl Hiramoto <karl@hiramoto.org>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: PCI IRQ Pins
Date: Thu, 21 May 2009 18:43:16 +0200 [thread overview]
Message-ID: <m3r5yi9zkr.fsf@intrepid.localdomain> (raw)
In-Reply-To: <4A156E36.6080806@hiramoto.org> (Karl Hiramoto's message of "Thu\, 21 May 2009 17\:07\:34 +0200")
Karl Hiramoto <karl@hiramoto.org> writes:
> Sorry, think i misspoke, after reading the IXP4xx dev manual it says
> 66Mhz PCI version 2.2.
Typically the PCI clock on IXP4xx is 33 MHz but your board can use any
value from 0 to 66.666 MHz. Most wifi cards don't work with 66 MHz,
though. The only card working @ 66 MHz for me is CM9 (all cards I have
fail to connect the M66EN line to ground, so they simply don't work
instead of forcing 33 MHz clock). They are all based on ath5 chips.
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-05-21 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A13EC76.3020206@hiramoto.org>
[not found] ` <m3r5ykgd97.fsf@intrepid.localdomain>
[not found] ` <20090520205151.GC4095@n2100.arm.linux.org.uk>
[not found] ` <m3zld7cuxk.fsf@intrepid.localdomain>
2009-05-21 6:14 ` PCI IRQ Pins Karl Hiramoto
2009-05-21 8:06 ` Karl Hiramoto
2009-05-21 14:45 ` Sergei Shtylyov
2009-05-21 14:50 ` Karl Hiramoto
2009-05-21 15:07 ` Karl Hiramoto
2009-05-21 16:43 ` Krzysztof Halasa [this message]
2009-05-21 19:12 ` Karl Hiramoto
2009-05-21 16:44 ` Sergei Shtylyov
2009-05-21 11:04 ` Krzysztof Halasa
2009-05-21 16:19 ` Karl Hiramoto
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=m3r5yi9zkr.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=ath9k-devel@lists.ath9k.org \
--cc=karl@hiramoto.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sshtylyov@ru.mvista.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