Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Nov 2006 10:17:30 +0900
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Nicolae Namolovan <adrenalinup@gmail.com>
Cc:        freebsd-net@freebsd.org, andre@freebsd.org, support@syskonnect.de
Subject:   Re: Marvell Yukon 88E8056 FreeBsd Drivers
Message-ID:  <20061127011729.GA60591@cdnetworks.co.kr>
In-Reply-To: <f027bef40611251420s6e898e4iba9cf5928266fb5@mail.gmail.com>
References:  <f027bef40611240533k453e90dfve6f662794bba3b84@mail.gmail.com> <20061125015223.GA51565@cdnetworks.co.kr> <f027bef40611251420s6e898e4iba9cf5928266fb5@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 26, 2006 at 12:20:46AM +0200, Nicolae Namolovan wrote:
 > Hooray, msk.HEAD.diff worked ! But only on the CURRENT..
 > 

Thanks for the report.
It would be even better if you can post dmesg output related with msk(4)
and e1000phy(4).

 > For those who don't know very well the "patch" tool(like me ;p),
 > msk.HEAD.diff create some new dirs, you must provide to the patch
 > utility the -p option(thanks to the folk from irc), here's how I got
 > it work(not sure if that's 100% correct):
 > cp msk.HEAD.diff /usr/src/
 > cd /usr/src/
 > patch -i msk.HEAD.diff -p
 > 
 > But I need to use it on a production server and the CURRENT one is too
 > unstable, without too much thinking I just run ping -f 127.0.0.1 and
 > after some minutes I got kernel panic, heh.
 > 

I can't sure it's related with msk(4) but I'll try on my box.

 > I think the msk driver is a great addition to the 7.0 version, great job !
 > 
 > If anyone know how to make Marvell Yukon 88E8056 work under FreeBSD 6
 > stable version, I would be very pleased to hear..
 > 

Last week I've finally fixed long standing Rx performance issue so
it would show up in src tree soon.

Due to the API differences between CURRENT and RELENG_6 it needs more
work to run msk(4) on REELENG_6. In addition, I should fix e1000phy(4)
first to make manual media selection work on msk(4). So please be
patient and give me a more time.

 > On 11/25/06, Pyun YongHyeon <pyunyh@gmail.com> wrote:
 > >On Fri, Nov 24, 2006 at 03:33:21PM +0200, Nicolae Namolovan wrote:
 > > > I took the hack from http://kerneltrap.org/node/7135, that guy said
 > > > that in linux you must "add the 4364 devID into sky2.c symply search
 > > > for 4363".
 > > >
 > > > I apply the same idea to
 > > > http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz,
 > > > modifyed oem.c and oem.h,
 > > >
 > > > oem.c
 > > > { VENDOR_ID_MRVL, DEV_ID_MRVL_4361, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY,
 > > > "Marvell 88E8050 Gigabit Ethernet Controller, Ver. 8.12.1.3"},
 > > > { VENDOR_ID_MRVL, DEV_ID_MRVL_4362, SUBVENDOR_ID_ANY, SUBDEVICE_ID_ANY,
 > > > "Marvell 88E8053 Gigabit Ethernet Controller, Ver. 8.12.1.3"},
 > > > + /* custom add..not sure */
 > > > + { VENDOR_ID_MRVL, DEV_ID_MRVL_4364, SUBVENDOR_ID_ANY, 
 > > SUBDEVICE_ID_ANY,
 > > > + "Marvell 88E8056 Gigabit Ethernet Controller, Ver. 8.12.1.3"},
 > > >
 > > >
 > > > oem.h
 > > >
 > > > #define DEV_ID_MRVL_4362 0x4362
 > > > + /* custom add..not sure */
 > > > + #define DEV_ID_MRVL_4364 0x4364
 > > >
 > > > After I compile it.
 > > >
 > > > That was sufficient to make this driver to hook mine Marvell Yukon
 > > > 88E8056, I can see it in ifconfig but i get:
 > > >
 > > > "status: no carrier"
 > > >
 > > > Tried to make the interface down/up, put away/back the network cable,
 > > > didn't help.. Still "no carrier".
 > > >
 > > > But it works fine under M Windows (so the problem is not in network
 > > > cable or the network device)..
 > > >
 > > > Any suggestions ?
 > > >
 > > > Maybe I must load the Windows drivers with NDIS, but I'm afraid of
 > > > performance degradation/instability ?
 > > >
 > > > Marvell Yukon 88E8056 are in the popular ASUS P5B and Gigabyte 965P-S3
 > > > motherboards.
 > > >
 > >
 > >You can find latest msk(4) at the following URL.
 > >http://people.freebsd.org/~yongari/msk/msk.HEAD.diff
 > >
 > >It supports the device ID you mentioned but I don't know whether it
 > >works or not. ATM the driver has three known issues.
 > > o poor Rx performance
 > >  I'm working on this but had no clue so far.
 > > o 88E8055 hangup :
 > >  One user reported system freeze when msk(4) is loaded. Since I don't
 > >  have the hardware it's very hard to fix. :-(
 > > o Manual speed selection doesn't seem to work.
 > >  It needs additional code for e1000phy(4) to fix.
 > >
 > >You need latest CURRENT to aplly the patch. The driver will print very
 > >ugly number sequnces but you can safely ingore it.
 > >
 > >--
 > >Regards,
 > >Pyun YongHyeon
 > >
 > 
 > 
 > -- 
 > Best regards,
 > Nicolae Namolovan.

-- 
Regards,
Pyun YongHyeon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061127011729.GA60591>