public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems
Date: Tue, 13 Sep 2005 02:34:04 +0900	[thread overview]
Message-ID: <dg4e7t$cu4$1@sea.gmane.org> (raw)
In-Reply-To: <4325B1C0.80405@gentoo.org>

Daniel Drake wrote:
> Kalin KOZHUHAROV wrote:
> 
>> Well, I did test it, but skge didn't even find the hardware :-(
>> No device was created, no dmesg output on load.
>> Instead I am running 2.6.13.1 with sk98lin-8.23.1.3.patch
>> The MB is ASUS P5GDC-V-Deluxe and the the on-board NIC:
>>
>> # lspci -v  -s 02:00.0
>> 0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd. 
>> 88E8053 Gigabit Ethernet Controller (rev 15)
> 
> 
> This patch was to solve an issue in skge, a driver for Marvell Yukon 
> network adapters.
> 
> Your hardware is a yukon-2 adapter, you want to use the sky2 driver from 
> the netdev tree.
Ok, that makes the things clear, thank you.

After quite a lot of fiddling iwth google and git, I found what you 
are talking about here:
http://www.mail-archive.com/netdev@vger.kernel.org/msg01592.html
http://www.kernel.org/git/?p=linux/kernel/git/jgarzik/netdev-2.6.git;a=commitdiff;h=cd28ab6a4e50a7601d22752aa7ce0c8197b10bdf

Somehow I missed it on LKML.
Unfortunately the machine with this chipset is  heavily used, so I 
am not very likely to get it off-line for testing.
Will have it in mind and try it if possible.

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|


  reply	other threads:[~2005-09-12 17:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  8:35 Very strange Marvell/Yukon Gigabit NIC networking problems Steve Kieu
2005-08-30  9:56 ` Daniel Drake
2005-08-30  9:58   ` Steve Kieu
2005-08-30 10:18     ` Daniel Drake
2005-08-30 10:24       ` Steve Kieu
2005-08-30 10:52       ` Steve Kieu
2005-08-30 11:54         ` Daniel Drake
2005-08-30 12:29           ` Steve Kieu
2005-08-30 13:31             ` Daniel Drake
2005-08-30 20:18               ` Jesse Brandeburg
2005-08-30 20:39                 ` Stephen Hemminger
2005-08-30 20:50                   ` Steve Kieu
2005-08-30 21:05                     ` Stephen Hemminger
2005-08-30 21:49                       ` Steve Kieu
2005-08-30 22:29                         ` Stephen Hemminger
2005-08-31  0:09                           ` Steve Kieu
2005-09-01 17:59                             ` Stephen Hemminger
2005-08-31  9:56                       ` Daniel Drake
2005-09-01 18:09           ` Stephen Hemminger
2005-09-01 21:21             ` Steve Kieu
2005-09-01 21:45               ` Howard Chu
2005-09-11 15:24               ` Daniel Drake
2005-09-11 18:12                 ` Kalin KOZHUHAROV
2005-09-12 16:01                   ` Kalin KOZHUHAROV
2005-09-12 16:50                     ` Daniel Drake
2005-09-12 17:34                       ` Kalin KOZHUHAROV [this message]
2005-09-12  0:02                 ` Steve Kieu

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='dg4e7t$cu4$1@sea.gmane.org' \
    --to=kalin@thinrope.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox