From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ra.tuxdriver.com ([70.61.120.52]:3338 "EHLO ra.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756933AbXJaUzh (ORCPT ); Wed, 31 Oct 2007 16:55:37 -0400 Date: Wed, 31 Oct 2007 16:54:46 -0400 From: "John W. Linville" To: Pavel Roskin Cc: Dan Williams , linux-wireless@vger.kernel.org Subject: Re: InProComm IPN2120 Message-ID: <20071031205446.GB14943@tuxdriver.com> (sfid-20071031_205612_131786_0D2115EA) References: <1193852430.11271.3.camel@localhost.localdomain> <1193863536.9260.11.camel@dv> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1193863536.9260.11.camel@dv> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Oct 31, 2007 at 04:45:36PM -0400, Pavel Roskin wrote: > > On Wed, 2007-10-31 at 13:40 -0400, Dan Williams wrote: > > I know this hardware has no existing drivers. However, does anyone know > > anything about this chipset? It's B-only from about 2003 or so, I > > think. > > I looked at its Windows drivers. Normally, it's not hard to find some > identifiers like "Atmel" or "HERMES" that give away the actual chipset > manufacturer. Not in this case. All I see are strings like: FWIW, they have a Wikipedia entry: http://en.wikipedia.org/wiki/Inprocomm -- John W. Linville linville@tuxdriver.com