Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
	j@w1.fi
Subject: Re: 60 GHz interface types (was: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210)
Date: Mon, 12 Nov 2012 11:24:10 +0100	[thread overview]
Message-ID: <1352715850.9525.17.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1352715356.9525.12.camel@jlt4.sipsolutions.net> (sfid-20121112_111531_023730_9DC299A9)

On Mon, 2012-11-12 at 11:15 +0100, Johannes Berg wrote:

> > I suppose we can have MAC stuff in the kernel as-is, and at least at the 
> > beginning try to handle multi-band entirely in the supplicant.
> 
> But it does raise the question of what happens if a single device
> supports both 2.4 and 60 GHz, or maybe all three of 2.4, 5 and 60 GHz.
> 
> If that would be on a single wiphy, I think we might run into issues
> with re-using the interface types?

Let me elaborate on this. Lets say we have a hypothetical device that
supports

 2.4 GHz - client mode
 60 GHz  - AP and PCP mode

Yes, that would be pretty stupid, but let's say it exists, and even
worse than that, it only supports 2.4 GHz *or* 60 GHz, not both at the
same time (1).

Now how do you express its capabilities? Obviously it has both 2.4 and
60 GHz channels, and the list of interface types it supports would be
client, AP, PCP -- however there's no way to tell which it supports on
which bands.

Yes, this is a contrived example, but are you sure it won't exist? The
sticking point is the fact that this device only has a single MAC that
handles both 2.4 and 60 GHz, as it is usually the case for 2.4 and 5
GHz, but then the capabilities are the same, since things *are* the
same. Evidently though, a 2.4 GHz client and 60 GHz client are
different.

johannes


(1) If it did support both at the same time, it would register two wiphy
structs with cfg80211.


  reply	other threads:[~2012-11-12 10:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 16:36 [PATCH v5 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-10-31 16:36 ` [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-11-08 19:29   ` Luis R. Rodriguez
2012-11-11 16:15     ` Vladimir Kondratiev
2012-11-12 17:22       ` Kalle Valo
2012-11-12 17:58         ` Vladimir Kondratiev
2012-11-13 19:39           ` Johannes Berg
2012-11-09  8:39   ` 60 GHz interface types (was: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210) Johannes Berg
2012-11-11  8:15     ` Vladimir Kondratiev
2012-11-11 13:42       ` Johannes Berg
2012-11-11 16:53         ` Vladimir Kondratiev
2012-11-12 10:15           ` Johannes Berg
2012-11-12 10:24             ` Johannes Berg [this message]
2012-11-12 14:57               ` Vladimir Kondratiev
2012-11-12 15:17                 ` Johannes Berg
2012-11-12 15:01             ` Vladimir Kondratiev
2012-11-12 17:22             ` Vladimir Kondratiev
2012-10-31 16:36 ` [PATCH v5 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev

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=1352715850.9525.17.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=qca_vkondrat@qca.qualcomm.com \
    --cc=rodrigue@qca.qualcomm.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