Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Ron Rindjunsky <ron.rindjunsky@intel.com>
Subject: Re: [PATCH 1/1] mac80211: adding bss_config to low driver ops
Date: Fri, 19 Oct 2007 14:25:44 +0200	[thread overview]
Message-ID: <1192796744.4167.7.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240710181146t111bd63ek97cf0c102d17369@mail.gmail.com> (sfid-20071018_194612_884567_BC7A460B)

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On Thu, 2007-10-18 at 20:46 +0200, Tomas Winkler wrote:

> > I think this is a bit dangerous. Above, you defined the structure member
> > 'changed_map' which I personally would read as "take care, in this
> > structure the fields X, Y and Z changed over what I gave you last time".
> > However, the way it's used here is as a 'valid' bitmap, in "In this
> > struct, only the fields X, Y and Z are valid". This is a huge difference
> > if the driver happens to need multiple things at the same time, with the
> > approach you're doing here you'd need to keep track of everything in the
> > driver.
> >
> Yes we can have both valid and change bitmap to lower that burden from
> form driver.

Oh I just realised that I didn't read this closely enough. If you
actually keep this structure around then we don't need a 'valid' bitmap
at all because all info will be valid all the time. If possible, I think
that would be much preferable, but I haven't really given much thought
to how complex it would be to implement.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2007-10-19 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 23:51 [PATCH 1/1] mac80211: adding bss_config to low driver ops Tomas Winkler
2007-10-18  0:06 ` Tomas Winkler
2007-10-18  1:38 ` Michael Wu
2007-10-21 11:23   ` Rindjunsky, Ron
2007-10-18 16:48 ` Johannes Berg
2007-10-18 18:46   ` Tomas Winkler
2007-10-18 18:57     ` Johannes Berg
2007-10-19 12:25     ` Johannes Berg [this message]
     [not found]       ` <c85cb4470710230045j71339683n10d9807ea23104b3@mail.gmail.com>
2007-10-23  9:59         ` Johannes Berg
2007-10-19 12:20   ` 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=1192796744.4167.7.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=ron.rindjunsky@intel.com \
    --cc=tomasw@gmail.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