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 16:17:16 +0100 [thread overview]
Message-ID: <1352733436.9445.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5760018.dRG2Gq6GXs@lx-vladimir>
On Mon, 2012-11-12 at 16:57 +0200, Vladimir Kondratiev wrote:
> > 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? [...]
> I wonder how do we do so if I substitute 5G instead of 60G, i.e. 2.4G client
> and 5G AP, not same time. How do we handle per-band cababilities in this case?
We don't -- they share the same MAC and everything, so there's no real
difference between 2.4 and 5 GHz that would make a device have such
contrived capabilities with 2.4/5 GHz. (and if we did, we'd have a big
problem :) )
Somehow I have a feeling 60 GHz is different though.
> Something makes me think that in your example it should be 2 wiphy structs;
> but need then I need to express inter-device restriction. I don't know right
> answer to this.
Would there be inter-device restrictions though? In my contrived
example, there would be, but with a real device?
With my example, the only way to handle it seems to be separate
interface types for 60 GHz, but maybe you can convince me that the
example is stupid :)
johannes
next prev parent reply other threads:[~2012-11-12 15:16 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
2012-11-12 14:57 ` Vladimir Kondratiev
2012-11-12 15:17 ` Johannes Berg [this message]
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=1352733436.9445.2.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