From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18314 invoked by alias); 11 Jan 2008 12:52:10 -0000 Received: (qmail 18306 invoked by uid 22791); 11 Jan 2008 12:52:10 -0000 X-Spam-Check-By: sourceware.org Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 11 Jan 2008 12:51:52 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1JDJMP-0005at-00; Fri, 11 Jan 2008 13:51:45 +0100 Date: Fri, 11 Jan 2008 12:52:00 -0000 From: Andrew Lunn To: Gary Thomas Cc: Antoine Zen-Ruffinen , eCos Discussion Message-ID: <20080111125145.GE20113@lunn.ch> Mail-Followup-To: Gary Thomas , Antoine Zen-Ruffinen , eCos Discussion References: <2cbbd8de0801100509x43959b34ka8e8e6f35dd081e5@mail.gmail.com> <47861B06.30303@mlbassoc.com> <2cbbd8de0801100544j62d5b5ecl75969aaec1da5122@mail.gmail.com> <478623CE.9030406@mlbassoc.com> <2cbbd8de0801100615t7ddec856h752b60c4c747e401@mail.gmail.com> <2cbbd8de0801100732s602930faj583502f8caf2633d@mail.gmail.com> <2cbbd8de0801110047i49478a2fy705443f4505fcd14@mail.gmail.com> <2cbbd8de0801110438ld37c75bpea97698811a5bc5d@mail.gmail.com> <47876536.8070800@mlbassoc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47876536.8070800@mlbassoc.com> User-Agent: Mutt/1.5.17 (2007-11-01) 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] Problem with TCP/IP stack X-SW-Source: 2008-01/txt/msg00060.txt.bz2 On Fri, Jan 11, 2008 at 05:46:46AM -0700, Gary Thomas wrote: > Antoine Zen-Ruffinen wrote: >> Ok, I found the problem but I dont' know how to solve it: My two NIC >> are sharing the same interrupt. So when the second NIC do an >> interrupt, it is handel like it is the first NIC that interrupt. >> >> Does someone know how to solve such an issue ? >> > > The key is to make your interrupt handler (ISR) tell the upper > layers which board did it. The intel i82559 driver can do this. Take a look at its interrupt handler code. Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss