Subject: Re: kern/32900
To: None <email@example.com, firstname.lastname@example.org,>
From: Christos Zoulas <email@example.com>
Date: 02/22/2006 14:10:05
On Feb 22, 6:40pm, firstname.lastname@example.org (Nino Dehne) wrote:
-- Subject: Re: kern/32900
| The following reply was made to PR kern/32900; it has been noted by GNATS.
| From: Nino Dehne <email@example.com>
| To: firstname.lastname@example.org
| Subject: Re: kern/32900
| Date: Wed, 22 Feb 2006 19:37:30 +0100
| On Wed, Feb 22, 2006 at 06:30:04PM +0000, Christos Zoulas wrote:
| > Great. Do you have sip(4) or gsip(4). From the man page only gsip(4) appears
| > to support vlan tagging.
| It's sip(4):
| sip0 at pci0 dev 14 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
| sip0: interrupting at irq 10
| nsphyter0 at sip0 phy 0: DP83815 10/100 media interface, rev. 1
| sip1 at pci0 dev 15 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
| sip1: interrupting at irq 9
| nsphyter1 at sip1 phy 0: DP83815 10/100 media interface, rev. 1
| sip2 at pci0 dev 16 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
| sip2: interrupting at irq 11
| nsphyter2 at sip2 phy 0: DP83815 10/100 media interface, rev. 1
| This chips are actually supposed to be DP83816. The board is a
| I think the ability to offload the tagging process to the hardware is unrelated.
| fxp(4) doesn't offload the tagging here either, which just means it has to be
| done in software, not that it's not possible at all. Just guessing..
| From the vlan man page it looks like the driver (and hardware?) has to support
| oversized frames, though. But sip(4) is listed there.
| Best regards,
The code apparently sets the ALP bit properly to receive big frames...
I suggest that you add some debugging in if_sip.c...