Date: Sat, 1 Jul 2006 14:18:44 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Nikolas Britton <nikolas.britton@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Marvell YukonII Status Update? Message-ID: <20060701051844.GE54876@cdnetworks.co.kr> In-Reply-To: <ef10de9a0606302139t71acf183w645985c467ef0435@mail.gmail.com> References: <ef10de9a0606292053i31abe4e2na30ec0028b54da8e@mail.gmail.com> <20060630060956.GA51353@cdnetworks.co.kr> <ef10de9a0606302139t71acf183w645985c467ef0435@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 30, 2006 at 11:39:14PM -0500, Nikolas Britton wrote: > On 6/30/06, Pyun YongHyeon <pyunyh@gmail.com> wrote: > >On Thu, Jun 29, 2006 at 10:53:52PM -0500, Nikolas Britton wrote: > > > Anyone know what's going on with YukonII support in FreeBSD, > > > specifically the Marvell chips used in PCI-Express add-on cards? > > > > > > Last I checked somebody was developing an experimental driver and > > > Marvell had just released the code to their FreeBSD 5.x/6.x driver: > > > mykbsd60x86-8.12.2.3.tar (bindary kmod package) > > > mykbsd60x86-8.12.1.3-src.tgz (source code) > > > > > > >I don't know current status of the driver. ATM FreeBSD YukonII > >driver has stability issues and the driver needs big cleanups > >if we import the driver into src tree. But I wouldn't do the > >job and I'll spend my spare time to other thing. > >I know, from my previous experience(sk(4), stge(4)), how > >difficult to write a driver without a document and how hard to > >write a correct driver without knowing hardware internals. I'm > >sure there are many developers eager to write YukonII driver if > >they can access the hardware documentation. However I think there > >is no possibility that Marvell releases their chip documentations. > > > > Marvell will give you the docs if you sign an NDA, I know it's stupid > but I think it's the only way... unless we vote with the wallet... Who > has PCI-Express gigabit NIC cards that meet the following criteria?: > > a) Supported by FreeBSD. > b) Unencumbered documentation. > c) Checksum offloading. > There are many PCIe GigE hardwares upported by em(4) or bge/bce(4). AFAIK the only hardware features not supported by em(4)/bge(4) driver is TSO. And hardwares supported by em(4) also have a capability to offload IPv6 checksumming too but it's not yet supported by the driver. -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060701051844.GE54876>