linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave <kilroyd@googlemail.com>
To: Karl Relton <karllinuxtest.relton@ntlworld.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	dwmw2@infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver.
Date: Wed, 01 Jul 2009 18:51:27 +0100	[thread overview]
Message-ID: <4A4BA21F.1070101@gmail.com> (raw)
In-Reply-To: <1246464991.4331.18.camel@localhost>

Karl Relton wrote:
> On Tue, 2009-06-30 at 14:58 -0700, Luis R. Rodriguez wrote:
>> Why all the srec->binary conversion? Doesn't this waste space on
>> people's firmware directories?
>>
> Yes, technically it does. The srec file is ~185KB, a binary image would
> be ~64KB.
> 
> The reason it was left is that the driver has to do some runtime
> plugging of data into the image, so pre-compilation would have meant
> inventing both a compiler tool and an intermediate format for the driver
> to read and process. Putting all the srec processing in the driver was
> more expedient (just meant porting existing userspace code into driver
> space).

I can't find the wlan_ng request_firmware call in my wireless-testing
tree (week or so old). Is that new?

>From what I can tell the wlan_ng, hostap and orinoco drivers all program
firmware that has the same basic format. Hostap doesn't use
request_firmware, and gives userspace the control over the write
sequence. orinoco places a very simple header in front of the binary image.

Do we really want to add srec processing to the driver (or even the kernel)?

It would be nice if the FW image was in the same format for orinoco and
wlan_ng, as the prism firmware ought to work on non-USB prism cards, and
we should be able to make orinoco use it.


Regards,

Dave.

  parent reply	other threads:[~2009-07-01 17:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 19:05 [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver Karl Relton
2009-06-30 19:17 ` Luis R. Rodriguez
2009-06-30 21:09   ` Karl Relton
2009-06-30 21:58     ` Luis R. Rodriguez
2009-07-01 16:16       ` Karl Relton
2009-07-01 17:14         ` Luis R. Rodriguez
2009-07-01 17:22           ` Pavel Roskin
2009-07-01 17:51         ` Dave [this message]
2009-07-01 18:12           ` Luis R. Rodriguez
2009-07-01 18:35             ` Dan Williams
2009-07-01 19:36               ` Insist on cfg80211 for new drivers? John W. Linville
2009-07-01 19:49                 ` Luis R. Rodriguez
2009-07-01 19:53                 ` Johannes Berg
2009-07-01 20:40                 ` Kalle Valo
2009-07-01 21:52                 ` Marcel Holtmann
2009-07-01 21:56                   ` Luis R. Rodriguez
2009-07-01 22:08                     ` Marcel Holtmann
2009-07-01 22:13                       ` Greg KH
2009-07-01 22:18                         ` Marcel Holtmann
2009-07-01 22:42                           ` Greg KH
2009-07-02 11:07                           ` Bartlomiej Zolnierkiewicz
2009-07-02 12:44                             ` Dan Williams
2009-07-02  9:19                       ` Christoph Hellwig
2009-07-06 12:52                 ` Johannes Berg
2009-07-06 14:23                   ` John W. Linville
2009-07-06 14:45                   ` Larry Finger
2009-07-06 14:57                     ` Johannes Berg
2009-07-06 15:05                       ` Nick Kossifidis
2009-07-01 19:46         ` [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver David Woodhouse
2009-07-02 16:59           ` Karl Relton
2009-06-30 19:39 ` John W. Linville

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=4A4BA21F.1070101@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=dwmw2@infradead.org \
    --cc=karllinuxtest.relton@ntlworld.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).