From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JAbx2-0005Vf-FD
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 21:06:24 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JAbx0-0005Rl-To
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 21:06:24 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JAbx0-0005Rb-Qu
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 21:06:22 -0500
Received: from ug-out-1314.google.com ([66.249.92.174])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <balrogg@gmail.com>) id 1JAbx0-0002ml-Or
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 21:06:22 -0500
Received: by ug-out-1314.google.com with SMTP id m2so3015451uge.4
	for <qemu-devel@nongnu.org>; Thu, 03 Jan 2008 18:06:21 -0800 (PST)
Message-ID: <fb249edb0801031806g1194e548ydcb7bbb060b186e1@mail.gmail.com>
Date: Fri, 4 Jan 2008 03:06:20 +0100
From: "andrzej zaborowski" <balrogg@gmail.com>
Subject: Re: [Qemu-devel] Multiple Ethernet interfaces for Gumstix connex
	(NetDUO-mmc)
In-Reply-To: <696059.68697.qm@web56002.mail.re3.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <696059.68697.qm@web56002.mail.re3.yahoo.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hi,

On 04/01/2008, John W <jmwoo2@yahoo.com> wrote:
> 3.  gpio line 37, I took a stab in the dark.
>
> With this change, eth0 seemed to continue to work
> perfectly.
>
> As for Eth1:
> 1.  The Linux Kernel seemed to ALSO recognize eth1.
> (example: ifconfig eth1 seemed to work fine)
>
> 2.  Sending packets out the eth1 interface seemed
> "okay", since I could run tcpdump on the tap1 host
> interface and see packets coming from the virtualized
> Connex eth1.
>
> 3.  Unfortunately, the eth1 device seems to have
> problems receiving packets due to some Interrupt
> conflict.  I seem to get a number of the following
> errors:
> NETDEV WATCHDOG: eth1: transmit timed out
>
>
>
> I was wondering if:
> 1. Anyone else out there was working on adding support
> for another Ethernet interface for the Gumstix connex
> (or Gumstix verdex)
> OR
> 2. Anyone could suggest some information on trying to
> add in another Ethernet interface.

cat /proc/interrupts may yield some information on which pin the
second NIC is connected to. The distance between the interrupt numbers
for eth0 and eth1 should be the same as between eth0 GPIO and eth1
GPIO. In particular they may be using the same GPIO with the two
signals being ORed or ANDed, or other combination, this can be done in
qemu too.

Regards