Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:36354 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750851Ab2KLKXf (ORCPT ); Mon, 12 Nov 2012 05:23:35 -0500 Message-ID: <1352715850.9525.17.camel@jlt4.sipsolutions.net> (sfid-20121112_112339_362932_953D656C) Subject: Re: 60 GHz interface types (was: [PATCH v5 1/2] wireless: Driver for 60GHz card wil6210) From: Johannes Berg To: Vladimir Kondratiev Cc: "John W . Linville" , linux-wireless@vger.kernel.org, "Luis R . Rodriguez" , j@w1.fi Date: Mon, 12 Nov 2012 11:24:10 +0100 In-Reply-To: <1352715356.9525.12.camel@jlt4.sipsolutions.net> (sfid-20121112_111531_023730_9DC299A9) References: <1351701417-3140-1-git-send-email-qca_vkondrat@qca.qualcomm.com> <12645035.o6OUeozobZ@lx-vladimir> <1352641337.12119.7.camel@jlt4.sipsolutions.net> <9805542.8YLh3g7mqN@lx-vladimir> <1352715356.9525.12.camel@jlt4.sipsolutions.net> (sfid-20121112_111531_023730_9DC299A9) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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.