From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Request for bisecting DMA partial fix
Date: Thu, 25 Nov 2010 10:22:22 +0100 [thread overview]
Message-ID: <AANLkTintrxtNDKJRPiNXAvr2XX3Fa5ZNBqwca59d9GfV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikLFuFd=155fO-VScNh7XKtZCMcR0DTo1V4-hHu@mail.gmail.com>
W dniu 8 listopada 2010 20:42 u?ytkownik Rafa? Mi?ecki
<zajec5@gmail.com> napisa?:
> We are quite sure that some patch than gone into mainline between
> 2.6.34 and 2.6.35 partially fixed DMA errors. It was not b43-specific
> fix and it probably wasn't commited via wireless-testing.
>
> The problem is this fix was only partial, under high transfer this is
> still noticeable. I think the shortest way to understand this and fix
> it totally is to find commit that partially fixed DMA errors.
>
> So we need someone with:
> 1) Machine that throws DMA errors on 2.6.34 and works noticeably
> better with 2.6.35
> 2) Time to bisect commit
> 3) Basic kernel building skills (however I believe we can help in case
> of problems)
>
> I believe bisecting has to be done on Linus's tree, between mentioned kernels.
>
> So is there anyone around who could handle this task?
Anyone? Please?
--
Rafa?
next prev parent reply other threads:[~2010-11-25 9:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 19:42 Request for bisecting DMA partial fix Rafał Miłecki
2010-11-08 21:49 ` Gábor Stefanik
2010-11-25 9:22 ` Rafał Miłecki [this message]
2010-11-26 17:39 ` Eric Garrido
2010-12-01 19:55 ` Rafał Miłecki
2010-12-11 8:51 ` Eric Garrido
2010-12-11 17:16 ` Rafał Miłecki
2010-12-11 17:22 ` Larry Finger
2010-12-11 19:55 ` Rafał Miłecki
2010-12-14 4:23 ` Eric Garrido
2011-04-14 18:39 ` Rafał Miłecki
2011-04-14 20:37 ` Juan Carlos Romero
2011-04-14 20:40 ` Rafał Miłecki
2011-04-14 20:47 ` Juan Carlos Romero
2011-04-14 21:07 ` Larry Finger
2011-04-14 23:07 ` Larry Finger
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=AANLkTintrxtNDKJRPiNXAvr2XX3Fa5ZNBqwca59d9GfV@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.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).