All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Andy Green <andy@warmcat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Tomas Winkler <tomasw@gmail.com>, Jiri Benc <jbenc@suse.cz>,
	jketreno <jketreno@linux.intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Michael Wu <flamingice@sourmilk.net>
Subject: Re: Specifing rate control algorithm?
Date: Fri, 11 May 2007 05:07:50 -0400	[thread overview]
Message-ID: <46443266.4060102@garzik.org> (raw)
In-Reply-To: <464424A7.2040301@warmcat.com>

Andy Green wrote:
> Sexy-sounding "hw offloading" is a very different thing to migrating off
> open code and putting it in vendor-specific closed source firmware.  The
> firmware is just code like any other, for an embedded ARM7 or similar,
> except that it is customized for a specific vendor hardware
> implementation and you will never see the sources.  What I understand is
> being talked about (maybe unlike the scan stuff this actually is in
> hardware, but I doubt it) is ignoring code in the stack and instead
> implementing pretty much the same code privately, to compile to a binary
> blob you can't see source for or even reverse according to its license.
>  That is a lot less romantic than mysterious hardware just waiting to be
> used.

OTOH, this is all vague, paranoid hand-waving since I'm guessing you 
don't know the internals of the Intel hardware.

We'll see what happens when Intel posts code to specify a different rate 
control algorithm.

	Jeff



  reply	other threads:[~2007-05-11  9:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 23:05 Specifing rate control algorithm? James Ketrenos
2007-05-10 11:27 ` Jiri Benc
2007-05-10 15:48   ` Jouni Malinen
2007-05-10 16:00     ` Tomas Winkler
2007-05-10 16:17   ` James Ketrenos
2007-05-10 17:11     ` Johannes Berg
2007-05-10 17:26       ` Jouni Malinen
2007-05-10 19:36       ` jketreno
2007-05-11 11:36         ` Johannes Berg
2007-05-10 17:42     ` Jiri Benc
2007-05-10 20:17       ` jketreno
2007-05-10 19:23         ` Jiri Benc
2007-05-10 22:24           ` Tomas Winkler
2007-05-11  0:12             ` John W. Linville
2007-05-11  8:09               ` Andy Green
2007-05-11  9:07                 ` Jeff Garzik [this message]
2007-05-11  9:36                   ` Andy Green
2007-05-11 14:23                 ` Jouni Malinen
2007-05-11 15:04                   ` Andy Green
2007-05-11 15:42                     ` Jouni Malinen
2007-05-11 10:21             ` Jiri Benc

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=46443266.4060102@garzik.org \
    --to=jeff@garzik.org \
    --cc=andy@warmcat.com \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.