Return-path: Received: from mx51.mymxserver.com ([85.199.173.110]:29411 "EHLO mx51.mymxserver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754358AbZJTG7P (ORCPT ); Tue, 20 Oct 2009 02:59:15 -0400 From: Holger Schurig To: Ivo van Doorn Subject: Re: [PATCH 2/2] rt2x00: Implement support for rt2800pci Date: Tue, 20 Oct 2009 08:58:54 +0200 Cc: Bartlomiej Zolnierkiewicz , John Linville , linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com, Alban Browaeys , Benoit PAPILLAULT , Felix Fietkau , Luis Correia , Mattias Nissler , Mark Asselstine , Xose Vazquez Perez , "linux-kernel" References: <200910152137.58164.IvDoorn@gmail.com> <200910171654.03344.bzolnier@gmail.com> <200910181859.22413.IvDoorn@gmail.com> In-Reply-To: <200910181859.22413.IvDoorn@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <200910200858.54683.hs4233@mail.mn-solutions.de> Sender: linux-wireless-owner@vger.kernel.org List-ID: > I don't agree on this, for starters the whole "abstraction > layer as done in the staging driver, really obfuscated the code > in multiple areas Ivo, you could look at Orinoco or Libertas. Both WLAN drivers support a multitude of different hardware (Libertas: CF/PCMCIA, SDIO, SD, USB and Orinoco: CF/PCMCIA, PCI, PPC_PMAC). And both have hardware abstraction layers that don't suck, obfuscate or create lots of duplicate code. So AFAIK it's not the question *IF* to do hardware abstraction but only a question *HOW* to do it in an intelligent way. Don't luck at one bad implementation and disregard the whole concept :-) -- http://www.holgerschurig.de