From: Karl Hiramoto <karl@hiramoto.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] PCI IRQ Pins
Date: Thu, 21 May 2009 21:12:21 +0200 [thread overview]
Message-ID: <4A15A795.4090100@hiramoto.org> (raw)
In-Reply-To: <m3r5yi9zkr.fsf@intrepid.localdomain>
Krzysztof Halasa wrote:
> 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.
>
checking IXP4XX_EXP_CFG0 bit 4 is 0 so PCI_CLK should be 33mhz
So i shouldn't have to tie the M66EN to ground.
--
Karl
WARNING: multiple messages have this Message-ID (diff)
From: Karl Hiramoto <karl@hiramoto.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
linux-ide@vger.kernel.org,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: PCI IRQ Pins
Date: Thu, 21 May 2009 21:12:21 +0200 [thread overview]
Message-ID: <4A15A795.4090100@hiramoto.org> (raw)
In-Reply-To: <m3r5yi9zkr.fsf@intrepid.localdomain>
Krzysztof Halasa wrote:
> 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.
>
checking IXP4XX_EXP_CFG0 bit 4 is 0 so PCI_CLK should be 33mhz
So i shouldn't have to tie the M66EN to ground.
--
Karl
next prev parent reply other threads:[~2009-05-21 19:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 11:41 [ath9k-devel] PCI IRQ Pins Karl Hiramoto
2009-05-20 12:39 ` Krzysztof Halasa
2009-05-20 20:51 ` Russell King - ARM Linux
2009-05-20 21:43 ` Krzysztof Halasa
2009-05-21 6:14 ` Karl Hiramoto
2009-05-21 6:14 ` Karl Hiramoto
2009-05-21 8:06 ` [ath9k-devel] " Karl Hiramoto
2009-05-21 8:06 ` Karl Hiramoto
2009-05-21 14:45 ` [ath9k-devel] " Sergei Shtylyov
2009-05-21 14:45 ` Sergei Shtylyov
2009-05-21 14:50 ` [ath9k-devel] " Karl Hiramoto
2009-05-21 14:50 ` Karl Hiramoto
2009-05-21 15:07 ` [ath9k-devel] " Karl Hiramoto
2009-05-21 15:07 ` Karl Hiramoto
2009-05-21 16:43 ` [ath9k-devel] " Krzysztof Halasa
2009-05-21 16:43 ` Krzysztof Halasa
2009-05-21 19:12 ` Karl Hiramoto [this message]
2009-05-21 19:12 ` Karl Hiramoto
2009-05-21 16:44 ` [ath9k-devel] " Sergei Shtylyov
2009-05-21 16:44 ` Sergei Shtylyov
2009-05-21 11:04 ` [ath9k-devel] " Krzysztof Halasa
2009-05-21 11:04 ` Krzysztof Halasa
2009-05-21 16:19 ` [ath9k-devel] " Karl Hiramoto
2009-05-21 16:19 ` Karl Hiramoto
2009-05-20 12:40 ` [ath9k-devel] " Michael Schwingen
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=4A15A795.4090100@hiramoto.org \
--to=karl@hiramoto.org \
--cc=ath9k-devel@lists.ath9k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.