linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Farina <sidhayn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pavel Roskin <proski@gnu.org>, Dave <kilroyd@googlemail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>,
	Hin-Tak Leung <htl10@users.sourceforge.net>,
	Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Subject: Re: Guidelines regarding separate directory
Date: Fri, 31 Oct 2008 13:04:44 -0400	[thread overview]
Message-ID: <490B3AAC.1000803@gmail.com> (raw)
In-Reply-To: <1225399682.3690.82.camel@johannes.berg>

Johannes Berg wrote:
>>> orinoco_pci.c
>>>       
>> orinoco_pci.c is a good candidate for removal.  It only supports the
>> hardware that is already supported by hostap_pci.
>>     
>
> Wait wait. I think everybody would rather see hostap go than orinoco
> since hostap is a huge complex thing and quite buggy.
>
>   
I really disagree with this statement.  Until kernel version 2.6.21 the 
hostap driver was used very widely by the wifi security community 
because of it's great abilities for monitor mode and frame injection.  
In kernel 2.6.21 there was a change that made the injection patches not 
work and my ability is insufficient to fix this regression, however, the 
orinoco driver has always had morbid issues with simple things such as 
monitor mode.

I understand that hostap needs some work, and it would be nice if 
someone volunteered to help fix the packet injection, but removing this 
driver in favor of orinoco_cs would be a serious regression.

thanks,
Rick Farina
> johannes
>   


  parent reply	other threads:[~2008-10-31 17:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 17:10 Guidelines regarding separate directory Larry Finger
2008-10-30 17:21 ` Johannes Berg
2008-10-30 20:24   ` Dave
2008-10-30 20:26     ` Johannes Berg
2008-10-30 20:44     ` Pavel Roskin
2008-10-30 20:48       ` Johannes Berg
2008-10-31  3:10         ` Pavel Roskin
2008-10-31 10:01           ` Johannes Berg
2008-10-31 16:01             ` Pavel Roskin
2008-10-31 16:13             ` Dan Williams
2008-10-31 16:24               ` Johannes Berg
2008-10-31 17:04         ` Richard Farina [this message]
2008-10-31 17:41           ` Pavel Roskin
2008-10-31 19:06             ` Richard Farina
2008-11-04  0:28               ` Pavel Roskin
2008-10-30 20:50       ` Dave
2008-10-30 17:29 ` John W. Linville
2008-10-30 23:47   ` Larry Finger
2008-10-31 10:06     ` Johannes Berg

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=490B3AAC.1000803@gmail.com \
    --to=sidhayn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --cc=htl10@users.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=kilroyd@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=proski@gnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).