From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6890 invoked by alias); 14 Sep 2012 13:16:21 -0000 Received: (qmail 6404 invoked by uid 22791); 14 Sep 2012 13:16:15 -0000 X-SWARE-Spam-Status: No, hits=2.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from bay0-omc1-s24.bay0.hotmail.com (HELO bay0-omc1-s24.bay0.hotmail.com) (65.54.190.35) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 14 Sep 2012 13:16:00 +0000 Received: from BAY146-W58 ([65.54.190.59]) by bay0-omc1-s24.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 14 Sep 2012 06:16:00 -0700 Message-ID: From: Bernd Edlinger To: Date: Fri, 14 Sep 2012 13:16:00 -0000 In-Reply-To: <50524A75.8060207@televic.com> References: <500401B9.1070304@televic.com> <50051EB6.3090802@televic.com>,<50524A75.8060207@televic.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] RFC: 802.1Q VLAN support in eCos X-SW-Source: 2012-09/txt/msg00017.txt.bz2 Hi J=FCrgen, > Hello Bernd, >=20 > I don't know if you saw my email below - maybe you can give me some advic= e? >=20 > Kind regards, > J=FCrgen >=20 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 b= e 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 Swit= ch 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 manageme= nt. Regards Bernd.=20=09=09=20=09=20=20=20=09=09=20=20 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss