Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: maali Al Janoob <mms82@hotmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: question for developers (help plzz!!)
Date: Mon, 20 Aug 2007 12:44:00 +0200	[thread overview]
Message-ID: <1187606640.6090.83.camel@johannes.berg> (raw)
In-Reply-To: <BAY111-F3965149B92B333B4E37A4DB6D80@phx.gbl>

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

On Fri, 2007-08-17 at 15:49 +0400, maali Al Janoob wrote:
> Thank you so much for the reply. My advisor is not very convinced with this 
> answer, and says that there must be somewhere a linux driver that has an 
> open source firmware for protocol development purposes, or a driver that 
> implements everything in software.

Clearly, your adviser has no clue how things work wrt. Linux and 802.11.
There's gnuradio, but I don't think they already have a working 802.11
implementation. That your adviser thinks that there could be a driver
that implements retry logic in software is a pretty good indication for
something else that I'll refrain from mentioning though.... Retry logic
is timing sensitive on the order of a microsecond and Linux isn't a
real-time operating system. That should tell you at least something.

> So, firstly, can I please ask you for 
> some references affirming your answer that I can include in my research? 

No. Feel free to do the research yourself, I've only answered based on
my own (limited) knowledge.

> and 
> secondly, are you aware of any attempt in the open source firmware 
> direction?

We've partially reverse engineered the Broadcom firmware and others have
partially reverse engineered the prism54 firmware, neither have working
replacement firmware. In fact, for Broadcom firmware I haven't been able
to completely identify the retry logic in the existing code from a quick
look.

> Assuming that there is no way I can access the backoff algorithm in any of 
> the commercial wireless cards, 

I assure you, this is the case unless you want to invest significant
reverse engineering effort or somehow manage to get vendor support. But
as far as I know, for example Broadcom's NDA doesn't include firmware
because there's no reason for a card vendor to have access to it.

> what would be the solution to my case then? I 
> need to modify the backoff algorithm for my masters thesis, and if this is 
> not possible with any card, what should I do?!

Why would you be asking me this question? Remember it's your masters
thesis, not mine, you're the one supposed to solve the problems arising.
I'm told (by my thesis advisers, mind you) one of the points of doing a
Master's is showing that one is able to solve the arising problems.

johannes

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

      reply	other threads:[~2007-08-20 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 20:54 question for developers (help plzz!!) maali Al Janoob
2007-08-17 10:18 ` Johannes Berg
2007-08-17 11:49   ` maali Al Janoob
2007-08-17 11:49   ` maali Al Janoob
2007-08-20 10:44     ` Johannes Berg [this message]

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=1187606640.6090.83.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mms82@hotmail.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