linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	"Michael Wu" <flamingice@sourmilk.net>,
	"John Linville" <linville@tuxdriver.com>,
	"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: [RFC][PATCH 0/4] p54: various updates
Date: Fri, 4 Apr 2008 04:07:51 +0200	[thread overview]
Message-ID: <200804040407.52432.chunkeey@web.de> (raw)
In-Reply-To: <43e72e890804031534y2afdc8d4h1154414df2ccdcd3@mail.gmail.com>

On Friday 04 April 2008 00:34:35 Luis R. Rodriguez wrote:
> On Thu, Apr 3, 2008 at 11:40 AM, Chr <chunkeey@web.de> wrote:
> > On Thursday 03 April 2008 01:42:59 Luis R. Rodriguez wrote:
> >  > Thanks, can you resend as inline patches so it can help get better
> >  > review. Also while you're at it can you stuff all p54 files into its
> >  > own folder?
> >
> >  hmm, I can.... but:
> >  - in which folder? for now.. I put everything into a new one folder
> > named p54, but as you know the fullmac driver has already the prism54
> > subdirectory... should I put it there? or is this confusing?
>
> p54 directory works nice. Now that you are introducing master mode the
> only thing left I think is IBSS compared to prism54, and if that is
> done I think we should *consider* removing prism54 driver after one
> release cycle of the kernel. I once was told that for some cards the
> softmac driver wouldn't work on some fullmac chipsets. I have yet to
> hear of someone who found these type of cards though. I know we also
> had some WDS code for prism54 lying around, it just never got merged
> in because Jeff didn't find it widely used and IIRC it needed a little
> more cleanup.
>
> Think you can get IBSS and maybe WDS to work too?
>
Hmm, AFAIK they were thinking of the 3877 (802.11a only)... I guess this one
won't work with p54. But have you ever see anyone (except the 
Intersil/Conexant people) with a 5Ghz prism card at all? It'll be interesting 
to get a eeprom dump from them... 

About WDS: is there anything special about WDS, that I should know? 
Since, I thought it's entirely done by mac80211 by now?

About IBSS: yes, it is kind of working... I'll put some code for this in the 
next round.

> >  - the resulting patch is too big to post it here, ~ 271kb as
> > plaintext... is a bz2 (32kb)  attachment ok too?
>
> Oh OK, I see. Can you perhaps split the big patch up into a few series?
that'll be about 3 or 4 parts... tomorrow! I have to figure out how
I can split up the _big_ one.

Regards,
	Chr

  reply	other threads:[~2008-04-04 11:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 21:39 [RFC][PATCH 0/4] p54: various updates Chr
2008-04-02 23:42 ` Luis R. Rodriguez
2008-04-03 15:40   ` Chr
2008-04-03 22:34     ` Luis R. Rodriguez
2008-04-04  2:07       ` Chr [this message]
2008-04-08 12:48         ` [RFC][PATCH 0/4] p54: various updates (all in one) Chr

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=200804040407.52432.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=flamingice@sourmilk.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@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 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).