qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Multiple Ethernet interfaces for Gumstix connex (NetDUO-mmc)
Date: Fri, 4 Jan 2008 03:06:20 +0100	[thread overview]
Message-ID: <fb249edb0801031806g1194e548ydcb7bbb060b186e1@mail.gmail.com> (raw)
In-Reply-To: <696059.68697.qm@web56002.mail.re3.yahoo.com>

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

      reply	other threads:[~2008-01-04  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  1:03 [Qemu-devel] Multiple Ethernet interfaces for Gumstix connex (NetDUO-mmc) John W
2008-01-04  2:06 ` andrzej zaborowski [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=fb249edb0801031806g1194e548ydcb7bbb060b186e1@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=qemu-devel@nongnu.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).