From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Simon <simon_alex@web.de>
Date: Mon, 27 Sep 2010 18:06:05 +0200
Subject: [ath9k-devel] PCI device 168c:ff1c ("AR5008",
	possibly Apple-branded)
In-Reply-To: <20100927151652.GD1551619@jupiter.n2.diac24.net>
References: <20100926133935.GA2405354@jupiter.n2.diac24.net>
	<201009271643.58162.simon_alex@web.de>
	<20100927151652.GD1551619@jupiter.n2.diac24.net>
Message-ID: <201009271806.05554.simon_alex@web.de>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Hi david,

> No. For now, I'm assuming the eeprom is fine; the Mac OS X driver lists
> 
> :ff1c and :ff1d as product IDs for Atheros cards, so this is NOT an
> 
> indication for a broken card.
Ok, i agree.
> 
> > Or try madwifi, i think it also supports the AR5008...
> 
> Hmm. This is a 11n card. I don't think madwifi supports 11n cards?
> 
> 
> -David

Hmm.. Just an idea:
Maybe to be compliant with PowerPC, apple converted the eeprom data to big 
endian. Our x86/x64 Linuxes have little endian.
So the "endian mismatch" message could be correct and the ath9k eeprom 
function just doesnt know to handle the big endian data.

If it runs with Madwifi, then its eeprom function should be able to cope with 
the other endianness, and one should be able to adapt this to ath9k...
So: another reason to try it with the madwifi or have a look at its sources :)

Alex