linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Lin <dlin@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Chor Teck Law <ctlaw@marvell.com>, Pete Hsieh <peteh@marvell.com>
Subject: Re: [PATCH v3] Add new mac80211 driver mwlwifi.
Date: Fri, 26 Jun 2015 09:07:58 +0200	[thread overview]
Message-ID: <1435302478.2106.2.camel@sipsolutions.net> (raw)
In-Reply-To: <9228e2c85d5d4bab9ad2cc859fa6c946@SC-EXCH02.marvell.com>

On Fri, 2015-06-26 at 01:25 +0000, David Lin wrote:

> Both the drivers are operable for the same chip part number 8897 and 
> its modules (boards) manufactured out there. The PCI Device ID is a 
> fixed value (by chip/manufacturer) on those modules. As said earlier, 
> the two drivers are for mac80211 host mac, and firmware mac 
> respectively. They serve different purposes. Users need to choose 
> which driver they want to use for the same wifi hardware, and they 
> cannot use both of them at the same time. The mwifiex is more widely 
> used now and sta centric. We do not want to break it.
> 
> I am not sure but I believe they are also multiple flavors of driver 
> for some other chips. Any advice how they are handled, considering 
> that changing the hardware/board is not an option? I guess we want 
> the community to be better served using the same hardware. Opinion 
> from others are welcomed.

Hmm, interesting, I didn't realize it was the same device.

Perhaps it simply shouldn't conflict at build time, and you can
recommend to blacklist one or the other? Or, in fact, return an error
from probe if you can't find the correct firmware file, so the other
driver would be attempted?

> Although "-D__CHECK_ENDIAN__" does not put into Makefile, I had used 
> "C=2 CF="-D__CHECK_ENDIAN__" to check warnings for endian and remove 
> these warnings.

Ok. Then I guess my issues were mostly due to 64-bit system.

> If you think we need to add this to Makefile and make sure zero 
> warning messages, we will do that (only for sparser).

Well it just helps not forget adding CF=-D... to the command line, it's
equivalent. I just prefer it in a sense since then if people run with
C=1 or C=2 they get that part for free, and since the driver is clean
to start with then that's a good thing to do I think.

I'll try to take a closer look later.

johannes

  reply	other threads:[~2015-06-26  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  3:48 [PATCH v3] Add new mac80211 driver mwlwifi David Lin
2015-06-25  9:38 ` Johannes Berg
2015-06-26  1:25   ` David Lin
2015-06-26  7:07     ` Johannes Berg [this message]
2015-06-26  7:56       ` David Lin
2015-09-07 11:09     ` Kalle Valo

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=1435302478.2106.2.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ctlaw@marvell.com \
    --cc=dlin@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peteh@marvell.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).