b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: francesco.gringoli@ing.unibs.it
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	b43-dev@lists.infradead.org, Bo Han <bohan@cs.umd.edu>
Subject: Release of Maranello firmware source code for Broadcom cards
Date: Sun, 10 Oct 2010 19:35:32 +0200	[thread overview]
Message-ID: <AANLkTimUdX1duphd=QYRz_i-TERfXbjOM1QEXaTUO13M@mail.gmail.com> (raw)
In-Reply-To: <E338C554-ADF5-490D-825D-E04D295664F0@ing.unibs.it>

W dniu 10 pa?dziernika 2010 18:53 u?ytkownik
<francesco.gringoli@ing.unibs.it> napisa?:
> On Oct 10, 2010, at 4:47 PM, Rafa? Mi?ecki wrote:
>
>> 2010/10/10 ?<francesco.gringoli@ing.unibs.it>:
>>> Hello there,
>>>
>>> we released the source code of the Maranello firmware and all the
>>> necessary kernel patches. It was tested on Broadcom 4318/4306 pci
>>> cards on PC architecture. Find all the necessary files browsing from
>>>
>>> http://www.ing.unibs.it/openfwwf
>>>
>>> or go directly here
>>>
>>> http://www.cs.umd.edu/projects/maranello
>>>
>>>
>>> Maranello is an enhancement of the 802.11 DCF standard: it implements
>>> a Partial Packet Recovery technique to retransmit only the corrupt
>>> parts of failed packets. This reduces the airtime and contributes to
>>> enhance the throughput. It was written starting from OpenFWWF5.2 by
>>> adding a number of new features.
>>>
>> Did you just add recovery feature to OpenFWWF 5.2 or did you improve
>> basic OpenFWWF as well?
>>
>> My 4318 with OpenFWWF 5.2 stops transmitting after few MB. Can
>> Maranello contain any fix for this? I'll able to test this later next
>> week.
>
> No, I don't think so. OpenFWWF5.2 does not handle correctly fifo overflow conditions. We have a testing firmware that handles them (and that works perfectly on WRT54GL): I hope we can release it soon.

Wow, that's great! If you need more testing, I'm willing to do some.
If you need full root access to machine with 4318 running
wireless-testing, just mail me privately.

Really hope you will manage to release that soon :)

-- 
Rafa?

  reply	other threads:[~2010-10-10 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2518B44B-D014-4ABA-AE31-BD75691488AB@ing.unibs.it>
2010-10-10 10:19 ` Release of Maranello firmware source code for Broadcom cards francesco.gringoli at ing.unibs.it
2010-10-10 12:34   ` Michael Büsch
2010-10-10 16:49     ` francesco.gringoli at ing.unibs.it
2010-10-10 17:11       ` Michael Büsch
2010-10-10 14:47   ` Rafał Miłecki
2010-10-10 16:53     ` francesco.gringoli at ing.unibs.it
2010-10-10 17:35       ` Rafał Miłecki [this message]
2010-12-13 19:44         ` AW: " h2o-post

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='AANLkTimUdX1duphd=QYRz_i-TERfXbjOM1QEXaTUO13M@mail.gmail.com' \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=bohan@cs.umd.edu \
    --cc=francesco.gringoli@ing.unibs.it \
    --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).