public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] RFC: 802.1Q VLAN support in eCos
Date: Fri, 14 Sep 2012 13:16:00 -0000	[thread overview]
Message-ID: <BAY146-W58C5CA21B260F273E0423FE4900@phx.gbl> (raw)
In-Reply-To: <50524A75.8060207@televic.com>


Hi Jürgen,
> Hello Bernd,
> 
> I don't know if you saw my email below - maybe you can give me some advice?
> 
> Kind regards,
> Jürgen
> 

yes. If you want any kind of support for VLAN tagging in eCos, you have to change the
network driver first. It is normally not configured to send 1522 bytes data packets.
So this has to change, in any case. It might be possible to strip VLAN tags, of filter
certain VLANs in the interface to the network stack.

You could also use a Marvell Switch, to handle the VLAN tags.
This is an ASIC of about the same size than the Atmel Processor, it could be integrated on a
Custom PCB this device can remove the VLAN tags, or add them.

It can handle the QOS field, and reserve certain Bandwith for different QOS values. I do
not see any way the Atmel could process that data volume at all.

This might allow you to keep the network stack unmodified, and use the Switch to
do the hard work.

I added the Transaction oriented interface to the PHY component, to talk to a Marvell
Switching Device, it uses the same SMI protocol as the PHY for the management.

Regards
Bernd. 		 	   		  

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2012-09-14 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 11:58 Lambrecht Jürgen
2012-07-17  8:13 ` Lambrecht Jürgen
2012-09-13 21:05   ` Lambrecht Jürgen
2012-09-14 13:16     ` Bernd Edlinger [this message]

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=BAY146-W58C5CA21B260F273E0423FE4900@phx.gbl \
    --to=bernd.edlinger@hotmail.de \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).