From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Wed, 29 Sep 2010 17:42:09 -0700 Subject: [ath9k-devel] [internal-ath9k-devel] PCI device 168c:ff1c ("AR5008", possibly Apple-branded) In-Reply-To: <20100929221612.20608.qmail@stuge.se> References: <93781E992CBA7843962D8B0E7D683F3C15C6EE4E9C@SC1EXMB-MBCL.global.atheros.com> <20100927195402.GA2933263@jupiter.n2.diac24.net> <20100927200839.GB2933263@jupiter.n2.diac24.net> <20100927202502.GJ2429@tux> <20100927204447.GC2933263@jupiter.n2.diac24.net> <20100929214230.GA3323065@jupiter.n2.diac24.net> <20100929220847.GF2050@tux> <20100929221612.20608.qmail@stuge.se> Message-ID: <20100930004209.GE2050@tux> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Wed, Sep 29, 2010 at 03:16:12PM -0700, Peter Stuge wrote: > Luis R. Rodriguez wrote: > > > Any hints on what this elusive 168c:ff1c device (and :ff1d) actually > > > is? Mac and Windows drivers *do* list these IDs... > > > > No, not sure, perhaps a mistake upon programming the EEPROM somehow? > > Except that Mathieu already confirmed it as a known ID. Peter, Mathieu's comment was saying how that PCI Device ID is used internally to support devices used during emulation. Emulation devices are not production devices, they are not applicable to the real world. > Maybe no more can be said. Too bad. I already noted how the device chip test failed, and how this gets run before even the EEPROM gets checksummed and checked, I suspected the device is bust and the tests run indicate it very likely is. Luis