lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 20 Oct 2009 18:31:11 +0200
From:	Ivo van Doorn <>
To:	Holger Schurig <>
Cc:	Bartlomiej Zolnierkiewicz <>,
	John Linville <>,,,
	Alban Browaeys <>,
	Benoit PAPILLAULT <>,
	Felix Fietkau <>,
	Luis Correia <>,
	Mattias Nissler <>,
	Mark Asselstine <>,
	Xose Vazquez Perez <>,
	"linux-kernel" <>
Subject: Re: [PATCH 2/2] rt2x00: Implement support for rt2800pci

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.


> 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists