linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFCv1] mac80211: Adds Software / Virtual AMP 80211
Date: Wed, 18 Apr 2012 16:29:55 +0200	[thread overview]
Message-ID: <1334759395.16897.231.camel@aeonflux> (raw)
In-Reply-To: <20120418132224.GG19228@aemeltch-MOBL1>

Hi Andrei,

> > > > > > This is also a little bit of confusing since FullMac cards will not
> > > > > > create an AMP virtual interface. With them you just see the HCI AMP
> > > > > > controller on the Bluetooth side. Can an AMP virtual interface be just
> > > > > > virtual inside mac80211 or does it have to have a netdev attached to it?
> > > > > 
> > > > > If we create virtual interface then netdev is allocated and we can handle
> > > > > it with common tools.
> > > > 
> > > > what common tools do you wanna use here. We actually do not wanna have
> > > > them show up as netdev devices at all. AMP connections don't have IP
> > > > addresses or anything else for that matter.
> > > 
> > > I might want to set up MAC address. Otherwise I might not need netdev. I
> > > feel that I need it for interface separation.
> > 
> > what MAC address? And where do you get this MAC address from? AMP
> > controllers do not have MAC addresses.
> 
> I assume I need some address to send/receive data over wireless.

from a Bluetooth point, we do not have to deal with the MAC address.
When looking at the mac80211 part, I do not know. However even then,
that address should come from the driver and not from userspace.

Regards

Marcel



  reply	other threads:[~2012-04-18 14:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 12:11 [RFCv1] Draft Software/Virtual AMP80211 Andrei Emeltchenko
2012-04-10 12:11 ` [RFCv1] mac80211: Adds Software / Virtual AMP 80211 Andrei Emeltchenko
2012-04-10 12:26   ` Julian Calaby
2012-04-10 12:47     ` Andrei Emeltchenko
2012-04-10 16:39   ` Johannes Berg
2012-04-10 21:17     ` Marcel Holtmann
2012-04-10 21:20       ` Johannes Berg
2012-04-10 21:24         ` Johannes Berg
2012-04-11  7:11           ` Andrei Emeltchenko
2012-04-18  2:03             ` Johannes Berg
2012-04-18 12:15               ` Andrei Emeltchenko
2012-04-18 14:38                 ` Johannes Berg
2012-04-18 14:52                   ` Andrei Emeltchenko
2012-04-18 15:09                     ` Johannes Berg
2012-04-18 15:39                       ` Mat Martineau
2012-04-19  6:36                       ` Andrei Emeltchenko
2012-04-19 13:28                         ` Johannes Berg
2012-04-19 13:39                           ` Andrei Emeltchenko
2012-04-19 14:21                             ` Johannes Berg
2012-04-10 21:29         ` Marcel Holtmann
2012-04-11  7:05           ` Andrei Emeltchenko
2012-04-18  2:07             ` Johannes Berg
2012-04-18 11:20               ` Andrei Emeltchenko
2012-04-18 11:51                 ` Marcel Holtmann
2012-04-18 12:10                   ` Andrei Emeltchenko
2012-04-18 12:15                     ` Marcel Holtmann
2012-04-18 12:33                       ` Andrei Emeltchenko
2012-04-18 13:11                         ` Marcel Holtmann
2012-04-18 13:22                           ` Andrei Emeltchenko
2012-04-18 14:29                             ` Marcel Holtmann [this message]
2012-04-18 15:02                               ` Andrei Emeltchenko
2012-04-18 14:34                   ` Johannes Berg
2012-04-18 14:56                     ` Marcel Holtmann
2012-04-18 14:30                 ` Johannes Berg

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=1334759395.16897.231.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).