All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	wireless <linux-wireless@vger.kernel.org>,
	b43-dev <b43-dev@lists.infradead.org>
Subject: b43 N PHY status report
Date: Tue, 21 Dec 2010 08:30:48 -0600	[thread overview]
Message-ID: <4D10BA18.40606@lwfinger.net> (raw)
In-Reply-To: <1292923526.2577.53.camel@macbook.infradead.org>

On 12/21/2010 03:25 AM, David Woodhouse wrote:
> 
> On-topic:
> 
> Anyone working on or testing network device drivers should be using
> IPv6. IPv6 will exercise code paths and network behaviour that Legacy IP
> rarely does, in particular using multicast to do neighbour discovery.
> And on wireless networks when multicast will be handled differently by
> the AP, that makes more difference than on wired where it's mostly the
> MAC filters that get neglected.
> 
> I've seen a number of broken drivers because their authors were only
> testing with Legacy IP and not IPv6.
> 
> It's not hard to set up IPv6. Larry, if you need any pointers I'd be
> more than happy to help.

I have no problem setting it up. I disabled it mostly to reduce the number of
modules in a kernel recompile. It doesn't make much difference on either of my
multi-core boxes, but some of the lower-powered units already take hours to build.

I take your point, and will be reenabling IPv6.

Larry

WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	wireless <linux-wireless@vger.kernel.org>,
	b43-dev <b43-dev@lists.infradead.org>
Subject: Re: b43 N PHY status report
Date: Tue, 21 Dec 2010 08:30:48 -0600	[thread overview]
Message-ID: <4D10BA18.40606@lwfinger.net> (raw)
In-Reply-To: <1292923526.2577.53.camel@macbook.infradead.org>

On 12/21/2010 03:25 AM, David Woodhouse wrote:
> 
> On-topic:
> 
> Anyone working on or testing network device drivers should be using
> IPv6. IPv6 will exercise code paths and network behaviour that Legacy IP
> rarely does, in particular using multicast to do neighbour discovery.
> And on wireless networks when multicast will be handled differently by
> the AP, that makes more difference than on wired where it's mostly the
> MAC filters that get neglected.
> 
> I've seen a number of broken drivers because their authors were only
> testing with Legacy IP and not IPv6.
> 
> It's not hard to set up IPv6. Larry, if you need any pointers I'd be
> more than happy to help.

I have no problem setting it up. I disabled it mostly to reduce the number of
modules in a kernel recompile. It doesn't make much difference on either of my
multi-core boxes, but some of the lower-powered units already take hours to build.

I take your point, and will be reenabling IPv6.

Larry

  parent reply	other threads:[~2010-12-21 14:30 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 20:55 [PATCH 0/4] Make N-PHY support experimental Rafał Miłecki
2010-12-07 20:55 ` Rafał Miłecki
2010-12-07 20:55 ` [PATCH 1/4] b43: N-PHY: silence warnings Rafał Miłecki
2010-12-07 20:55   ` Rafał Miłecki
2010-12-07 20:55 ` [PATCH 2/4] b43: set TMS to work with current band width for N-PHY Rafał Miłecki
2010-12-07 20:55   ` Rafał Miłecki
2010-12-07 21:08   ` Michael Büsch
2010-12-07 21:08     ` Michael Büsch
2010-12-09 14:12     ` Rafał Miłecki
2010-12-09 14:12       ` Rafał Miłecki
2010-12-09 14:13       ` Rafał Miłecki
2010-12-09 14:13         ` Rafał Miłecki
2010-12-09 14:19         ` Michael Büsch
2010-12-09 14:19           ` Michael Büsch
2010-12-09 14:23           ` Rafał Miłecki
2010-12-09 14:23             ` Rafał Miłecki
2010-12-09 14:28             ` Michael Büsch
2010-12-09 14:28               ` Michael Büsch
2010-12-09 14:41             ` Michael Büsch
2010-12-09 14:41               ` Michael Büsch
2010-12-07 20:55 ` [PATCH 3/4] b43: fix split of N-PHY devices into supported and not (based on PHY rev) Rafał Miłecki
2010-12-07 20:55   ` Rafał Miłecki
2010-12-07 20:56 ` [PATCH 4/4] b43: rename config option for N-PHY, drop BROKEN Rafał Miłecki
2010-12-07 20:56   ` Rafał Miłecki
2010-12-07 21:04 ` [PATCH 0/4] Make N-PHY support experimental Johannes Berg
2010-12-07 21:04   ` Johannes Berg
2010-12-07 22:57 ` Gábor Stefanik
2010-12-07 22:57   ` Gábor Stefanik
2010-12-07 23:11   ` Larry Finger
2010-12-07 23:11     ` Larry Finger
2010-12-08  3:37   ` Larry Finger
2010-12-08  3:37     ` Larry Finger
2010-12-09 14:11     ` Rafał Miłecki
2010-12-09 14:11       ` Rafał Miłecki
2010-12-09 15:20       ` Larry Finger
2010-12-09 15:20         ` Larry Finger
2010-12-09 15:25         ` Johannes Berg
2010-12-09 15:25           ` Johannes Berg
2010-12-09 15:28           ` Rafał Miłecki
2010-12-09 15:28             ` Rafał Miłecki
2010-12-09 15:33             ` Johannes Berg
2010-12-09 15:33               ` Johannes Berg
2010-12-09 15:37               ` Rafał Miłecki
2010-12-09 15:37                 ` Rafał Miłecki
2010-12-09 16:03                 ` Larry Finger
2010-12-09 16:03                   ` Larry Finger
2010-12-10  3:52                   ` Jon Saul
2010-12-10  3:52                     ` Jon Saul
2010-12-10  4:05                     ` Larry Finger
2010-12-10  4:05                       ` Larry Finger
2010-12-09 16:10         ` Rafał Miłecki
2010-12-09 16:10           ` Rafał Miłecki
2010-12-08 15:15   ` b43 N PHY status report Larry Finger
2010-12-08 15:15     ` Larry Finger
2010-12-10 16:57     ` Peter Stuge
2010-12-10 17:15       ` Larry Finger
2010-12-10 18:34         ` Peter Stuge
2010-12-10 18:44           ` Peter Stuge
2010-12-13 17:00             ` Rafał Miłecki
2010-12-13 17:41               ` Larry Finger
2010-12-13 18:17                 ` Rafał Miłecki
2010-12-13 18:37                   ` Larry Finger
2010-12-13 18:34                 ` Peter Stuge
2010-12-13 18:43                   ` Larry Finger
2010-12-10 18:22       ` Francesco Gringoli
2010-12-10 18:30     ` Francesco Gringoli
2010-12-10 18:30       ` Francesco Gringoli
2010-12-10 18:47       ` Johannes Berg
2010-12-10 18:47         ` Johannes Berg
2010-12-10 19:02         ` Larry Finger
2010-12-10 19:02           ` Larry Finger
2010-12-10 19:04           ` Gábor Stefanik
2010-12-10 19:04             ` Gábor Stefanik
2010-12-10 19:08             ` Johannes Berg
2010-12-10 19:08               ` Johannes Berg
2010-12-21  9:25               ` David Woodhouse
2010-12-21  9:25                 ` David Woodhouse
2010-12-21  9:30                 ` Rafał Miłecki
2010-12-21  9:30                   ` Rafał Miłecki
2010-12-21 14:30                 ` Larry Finger [this message]
2010-12-21 14:30                   ` Larry Finger
2010-12-10 18:53     ` Konstantinos Karantias
2010-12-10 19:00       ` Larry Finger
2010-12-10 19:00         ` Larry Finger
2010-12-09 14:09   ` [PATCH 0/4] Make N-PHY support experimental Rafał Miłecki
2010-12-09 14:09     ` Rafał Miłecki

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=4D10BA18.40606@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@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.