public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steve Davies" <davies147@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: VIA Velocity and 802.1q VLAN support
Date: Tue, 18 Dec 2007 17:45:45 +0000	[thread overview]
Message-ID: <5caa9b870712180945o17c797f7rb00a1b0d3fc12fc6@mail.gmail.com> (raw)

Hi,

After a significant amout of archive searching, and code tweaking, I
am giving up and asking the list :)

I have a number of EPIA boards which need to operate in a mixed
tagged-VLAN and untagged-interface environment using their onboard
VIA-Velocity NICs. I am running a Debian ETCH 2.6.18 kernel, but have
managed to backport the latest 2.6.24-rc5 via-velocity driver fairly
simply. Sadly this does not seem to fix the problem.

Having added some debug kprintf, it appears as if the hardware VLAN
support is never enabled in this driver (vptr->vlgrp == NULL at all
times). I added a velocity_vlan_rx_register method, and enabled the
NETIF_F_HW_VLAN_RX feature, which did start to cause the appropriate
NIC registers to be set, but this simply stopped the inbound data
working entirely if a tagged vlan was created.

It manages to send packets both on the correct (tagged) vlan, and on
the untagged interface. The stock driver also receives packets on the
untagged interface okay, but inbound tagged packets never seem to make
it into the net subsystem.

I assume that the NIC is not allowing tagged packets into the driver
due to its built-in hardware acceleration/filtering :(

Is it inappropriate to beg for help and suggestions?

Thanks,
Steve

             reply	other threads:[~2007-12-18 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 17:45 Steve Davies [this message]
2007-12-18 23:07 ` VIA Velocity and 802.1q VLAN support Francois Romieu

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=5caa9b870712180945o17c797f7rb00a1b0d3fc12fc6@mail.gmail.com \
    --to=davies147@gmail.com \
    --cc=linux-kernel@vger.kernel.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