From: Martin Michlmayr <tbm@cyrius.com>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: Tulip driver broken on Cobalt RaQ1 in 2.6
Date: Fri, 24 Aug 2007 10:02:16 +0200 [thread overview]
Message-ID: <20070824080215.GA31646@deprecation.cyrius.com> (raw)
In-Reply-To: <20070824133656.4163c577.yoichi_yuasa@tripeaks.co.jp>
* Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp> [2007-08-24 13:36]:
> What error occurs on Raq1?
There is no error, but I never get a DHCP response:
Listening on LPF/eth0/00:10:e0:00:27:5c
Sending on LPF/eth0/00:10:e0:00:27:5c
Sending on Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
> > Galileo: PCI retry count exceeded (06.0)
>
> I cannot find this line in current git.
It's in arch/mips/cobalt/irq.c
> Do you apply any patch for Debian kernel?
This is a pristine kernel from git (well, I had to apply your patch to
get IDE going).
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2007-08-24 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 20:37 Tulip driver broken on Cobalt RaQ1 in 2.6 Martin Michlmayr
2007-08-24 3:22 ` Markus Gothe
2007-08-24 4:36 ` Yoichi Yuasa
2007-08-24 8:02 ` Martin Michlmayr [this message]
2007-08-24 9:04 ` Peter Horton
2007-08-24 11:24 ` Martin Michlmayr
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=20070824080215.GA31646@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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