Jack Vogel wrote:
This is a patch for the stack and the em driver to enable TSO
on CURRENT. Previously I had problems getting it to work, but
this is functional.
I should note that CURRENT is being a pain right now, when
I comment out em in the config the kernel panics coming up,
so I had to
Maxim Konovalov wrote:
On Tue, 29 Aug 2006, 17:15+0200, Andre Oppermann wrote:
John-Mark Gurney wrote:
Randall Stewart wrote this message on Mon, Aug 28, 2006 at 17:04 -0400:
atomic_fetchadd_int(m-m_ext.ref_cnt, -1) == 0) {
^
This should be 1 not 0.. as apparently fetchadd_int
The following reply was made to PR kern/102035; it has been noted by GNATS.
From: George Mitchell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/102035: [plip] plip networking disables parallel port printing
Date: Sat, 2 Sep 2006 10:35:32 -0700 (PDT)
Here is a corrected patch
The following reply was made to PR kern/102035; it has been noted by GNATS.
From: George Mitchell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/102035: [plip] plip networking disables parallel port printing
Date: Sat, 2 Sep 2006 10:36:22 -0700 (PDT)
Here is a corrected patch
The following reply was made to PR kern/102035; it has been noted by GNATS.
From: George Mitchell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/102035: [plip] plip networking disables parallel port printing
Date: Sat, 2 Sep 2006 10:38:10 -0700 (PDT)
Here is a corrected patch
The following reply was made to PR kern/102607; it has been noted by GNATS.
From: Stefan Bethke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/102607: [if_bridge] don't generate random L2 address
Date: Sun, 3 Sep 2006 01:09:16 +0200
Here's my suggestion for an addition to
On 9/2/06, Andre Oppermann [EMAIL PROTECTED] wrote:
Jack Vogel wrote:
This is a patch for the stack and the em driver to enable TSO
on CURRENT. Previously I had problems getting it to work, but
this is functional.
I should note that CURRENT is being a pain right now, when
I comment out em
On 9/2/06, Andre Oppermann [EMAIL PROTECTED] wrote:
I can't comment on the em part but the tcp_output.c stuff looks
very much like a straight port from NetBSD. If we take code from
the other BSDs we have to remark this in the emails we send with
patches and the commit message (otherwise we get
The following reply was made to PR kern/102035; it has been noted by GNATS.
From: George Mitchell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/102035: [plip] plip networking disables parallel port printing
Date: Sat, 2 Sep 2006 19:12:18 -0700 (PDT)
My apologies for the
I am sometime using the environment IEEE802.1a SNAP on ethernet.
But FreeBSD's network stack supports only EtherframeII as IP. So
I researched how to use on IEEE802.1a SNAP. I think that following
approch is good. But I couldn't do it:-(.
# ngctl mkpeer
On Sun, 3 Sep 2006 13:20:50 +0900
Norikatsu Shigemura [EMAIL PROTECTED] wrote:
I am sometime using the environment IEEE802.1a SNAP on ethernet.
But FreeBSD's network stack supports only EtherframeII as IP. So
I researched how to use on IEEE802.1a SNAP. I think that following
Your approach is interesting, but I'm not sure I like the idea of adding a
new semantic to the defaults file.
Would you consider instead modifying network6_interface_setup in
network.subr to not automatically configure a plip interface if
ipv6_ifconfig_plipN is unset or null? That would
12 matches
Mail list logo
