[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200705062044.52408.mb@bu3sch.de>
Date: Sun, 6 May 2007 20:44:51 +0200
From: Michael Buesch <mb@...sch.de>
To: "John W. Linville" <linville@...driver.com>
Cc: Jeff Garzik <jeff@...zik.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Gary Zambrano <zambrano@...adcom.com>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
bcm43xx-dev@...ts.berlios.de, ralf@...ux-mips.org,
davej@...emonkey.org.uk, mtakahashi@...no.co.jp
Subject: Re: Merging SSB upstream
On Sunday 06 May 2007 19:38:33 John W. Linville wrote:
> On Sun, May 06, 2007 at 11:44:27AM +0200, Michael Buesch wrote:
> > On Sunday 06 May 2007 04:00:51 John W. Linville wrote:
>
> > > I had to remove
> > > the b44 ssb changes from fedora because a) users reported problems;
> >
> > Which problems were that? The 2 compile issues?
> > Trivial to fix if that's the only issue. ;)
>
> I knew you would ask that... :-)
:P
> I don't think there was a bugzilla, but Dave Jones forwarded an email
> to me from "MASAO TAKAHASHI" in late February. Takahashi-san (forgive
> me if I did that wrong) was complaining about tx timeouts after I
> had added the full wireless-dev patchset to rawhide. Removing the
> b44 bits of the patch seemed to remove the problem.
>
> That's all the info I have. Perhaps Dave or Takahashi-san can add
> to the description?
Hm, interesting issue.
But I'm not convinced that it's caused by the SSB port, though.
What the SSB port essentially does is modifying small areas in the
init and exit paths. The modified things in the TX and RX hotpaths
are really tiny and trivial. TX timeout sounds like something in the
TX/RX paths is going wrong.
But anyway, maybe I got something wrong.
I'll run some burn-in tests on it now.
--
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists