Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Apr 2006 20:35:49 -0400
From:      Brad <brad@comstyle.com>
To:        freebsd-net@freebsd.org
Subject:   Re: Marvell 88E8053 lan controller support
Message-ID:  <20060425003549.GG14517@blar.home.comstyle.com>
In-Reply-To: <20060425001851.GB946@cdnetworks.co.kr>
References:  <001201c666d4$b69dc290$0201a8c0@oxy> <20060423140833.V13011@maildrop.int.zabbadoz.net> <e2iokp$5bq$1@sea.gmane.org> <20060424234934.GA946@cdnetworks.co.kr> <20060425000106.GF14517@blar.home.comstyle.com> <20060425001851.GB946@cdnetworks.co.kr>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 25, 2006 at 09:18:51AM +0900, Pyun YongHyeon wrote:
> On Mon, Apr 24, 2006 at 08:01:06PM -0400, Brad wrote:
>  > On Tue, Apr 25, 2006 at 08:49:34AM +0900, Pyun YongHyeon wrote:
>  > > On Mon, Apr 24, 2006 at 07:51:05AM -0700, othermark wrote:
>  > >  > Bjoern A. Zeeb wrote:
>  > >  > 
>  > >  > > On Sun, 23 Apr 2006, OxY wrote:
>  > >  > > 
>  > >  > >> hi!
>  > >  > >>
>  > >  > >> my question is when will this chip being supported by 6.x?
>  > >  > > 
>  > >  > > for x>1 maybe.
>  > >  > > 
>  > >  > >> or is it supported now and i didn't find the proper driver? :)
>  > >  > > 
>  > >  > > search freebsd-net archive of Jan 2006, posting from andre oppermann
>  > >  > > and do not forget to read the follow-ups.
>  > >  > 
>  > >  > Just so other people don't have to do the rummaging, here's the link from
>  > >  > gmane.org. 
>  > >  > 
>  > >  > http://thread.gmane.org/gmane.os.freebsd.current/79126/focus=79126
>  > >  > 
>  > >  > I too am hoping someone will step up to the plate and this support will be
>  > >  > integrated into -current.
>  > >  > 
>  > > 
>  > > I've tried their driver on CURRENT(It needs a minor modification to
>  > > compile on CURRENT). But the driver didn't recognize link and even
>  > > it panicked with numeros witness warnings when I enabled jumbo frame
>  > > support.
>  > > In addition it didn't attach for DGE530T. I think there driver is
>  > > in experimental stage not for production use. In order to support
>  > > Yukon II we need a documentation from Marvell.
>  > 
>  > It is *extremely* unlikely that you will ever see documentation for the
>  > Yukon II from Marvell. At this point the only option is to reverse
>  > engineer the existing driver and/or use the new Linux driver as a source
>  > of information.
> 
> :-(
> 
> Since they released source code for FreeBSD I can't see any point
> not releasing the documentation.

Source exists for newer Broadcom Gig chips (575x and derivatives) yet
there is no documentation available for that either.

> However I'm happy as they didn't released binary only driver such as nve(4).

True, though nve(4) never really worked. Work has been done to resolve
the binary blob issue and have a working driver. FreeBSD needs to catch up.

> Getting hardware information from Linux driver source would be more
> better option due to the complexity of Marvell's driver, I guess.

This is most likely the right approach.



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