All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
	Alban Browaeys <prahal@yahoo.com>,
	Benoit PAPILLAULT <benoit.papillault@free.fr>,
	Felix Fietkau <nbd@openwrt.org>,
	Luis Correia <luis.f.correia@gmail.com>,
	Mattias Nissler <mattias.nissler@gmx.de>,
	Mark Asselstine <asselsm@gmail.com>,
	Xose Vazquez Perez <xose.vazquez@gmail.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] rt2x00: Implement support for rt2800pci
Date: Tue, 20 Oct 2009 18:31:11 +0200	[thread overview]
Message-ID: <200910201831.12285.IvDoorn@gmail.com> (raw)
In-Reply-To: <200910200858.54683.hs4233@mail.mn-solutions.de>

On Tuesday 20 October 2009, Holger Schurig wrote:
> > 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.

Thanks,

> 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 :-)

Oh I completely agree, I am not against the extra abstraction layer,
but I do want a nice looking solution. :) I'll take a look at the Orinoco approach.

Thanks,

Ivo

WARNING: multiple messages have this Message-ID (diff)
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, users@host1.serialmonkey.com,
	Alban Browaeys <prahal@yahoo.com>,
	Benoit PAPILLAULT <benoit.papillault@free.fr>,
	Felix Fietkau <nbd@openwrt.org>,
	Luis Correia <luis.f.correia@gmail.com>,
	Mattias Nissler <mattias.nissler@gmx.de>,
	Mark Asselstine <asselsm@gmail.com>,
	Xose Vazquez Perez <xose.vazquez@gmail.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] rt2x00: Implement support for rt2800pci
Date: Tue, 20 Oct 2009 18:31:11 +0200	[thread overview]
Message-ID: <200910201831.12285.IvDoorn@gmail.com> (raw)
In-Reply-To: <200910200858.54683.hs4233@mail.mn-solutions.de>

On Tuesday 20 October 2009, Holger Schurig wrote:
> > 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.

Thanks,

> 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 :-)

Oh I completely agree, I am not against the extra abstraction layer,
but I do want a nice looking solution. :) I'll take a look at the Orinoco approach.

Thanks,

Ivo

  reply	other threads:[~2009-10-20 16:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200910152137.58164.IvDoorn@gmail.com>
2009-10-15 20:04 ` [PATCH 2/2] rt2x00: Implement support for rt2800pci Ivo van Doorn
2009-10-16  9:49   ` Simon Raffeiner
2009-10-16 10:55     ` [rt2x00-users] " Ivo van Doorn
2009-10-16 11:12       ` Xose Vazquez Perez
2009-10-16 12:13         ` Simon Raffeiner
2009-10-17 14:54   ` Bartlomiej Zolnierkiewicz
2009-10-17 14:54     ` Bartlomiej Zolnierkiewicz
2009-10-17 15:08     ` Johannes Berg
2009-10-17 15:08       ` Johannes Berg
2009-10-17 15:19       ` Bartlomiej Zolnierkiewicz
2009-10-17 15:19         ` Bartlomiej Zolnierkiewicz
2009-10-17 21:18     ` Bartlomiej Zolnierkiewicz
2009-10-17 21:18       ` Bartlomiej Zolnierkiewicz
2009-10-18  9:40       ` Luis Correia
2009-10-18  9:40         ` Luis Correia
2009-10-18  3:08     ` Julian Calaby
2009-10-18  3:08       ` Julian Calaby
2009-10-18 16:59     ` Ivo van Doorn
2009-10-18 16:59       ` Ivo van Doorn
2009-10-19 15:56       ` Bartlomiej Zolnierkiewicz
2009-10-19 15:56         ` Bartlomiej Zolnierkiewicz
2009-10-19 17:42         ` Ivo van Doorn
2009-10-19 17:42           ` Ivo van Doorn
2009-10-20  6:58       ` Holger Schurig
2009-10-20  6:58         ` Holger Schurig
2009-10-20 16:31         ` Ivo van Doorn [this message]
2009-10-20 16:31           ` Ivo van Doorn

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=200910201831.12285.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=asselsm@gmail.com \
    --cc=benoit.papillault@free.fr \
    --cc=bzolnier@gmail.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=luis.f.correia@gmail.com \
    --cc=mattias.nissler@gmx.de \
    --cc=nbd@openwrt.org \
    --cc=prahal@yahoo.com \
    --cc=users@rt2x00.serialmonkey.com \
    --cc=xose.vazquez@gmail.com \
    /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.