netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Freescale FEC i.MX28 VLAN support?
Date: Wed, 14 May 2014 12:12:31 +0200	[thread overview]
Message-ID: <5373418F.6090602@meduna.org> (raw)

Hi,

is there any particular reason why the FEC_QUIRK_HAS_VLAN
is only set for imx6q-fec ?

According to the reference manual the VLAN support is also
present in i.MX28 and the DMA descriptors look the same
in this regard, but this is from eyeballing only, I did not
try to play with it yet.

The reason I am asking is that I am using a switch that can
tag the frames according to the port a packet is received
from/sent to and I would like to use that feature.

Please Cc: me when replying.

Thanks
-- 
                                Stano

             reply	other threads:[~2014-05-14 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 10:12 Stanislav Meduna [this message]
2014-05-14 10:37 ` Freescale FEC i.MX28 VLAN support? fugang.duan

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=5373418F.6090602@meduna.org \
    --to=stano@meduna.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).