All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>
Cc: linux-kernel@vger.kernel.org, NetDev <netdev@vger.kernel.org>,
	Grant Grundler <grundler@parisc-linux.org>
Subject: Re: tulip driver receive but not send 2.6.25-rc6-git7
Date: Fri, 28 Mar 2008 21:34:44 -0400	[thread overview]
Message-ID: <47ED9CB4.7010603@garzik.org> (raw)
In-Reply-To: <200803281828.39948.gustavo@compunauta.com>

Gustavo Guillermo Pérez wrote:
> I'm putting all wires on the same swirch for testing.
> eth0 is a sis embedded card (good one).
> dealing with dhcp I see that request arrives to the board but the offers never 
> appears on client. system clean no iptables rules, just dhcpd.

> I'm gonna try with rc7-git4 and 2.6.24

Please do.

Also, try the 'dmfe' driver, as it was written specifically for these chips.

	Jeff



  reply	other threads:[~2008-03-29  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  0:28 tulip driver receive but not send 2.6.25-rc6-git7 Gustavo Guillermo Pérez
2008-03-29  1:34 ` Jeff Garzik [this message]
2008-03-30 21:10   ` Gustavo Guillermo Pérez

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=47ED9CB4.7010603@garzik.org \
    --to=jeff@garzik.org \
    --cc=grundler@parisc-linux.org \
    --cc=gustavo@compunauta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.