From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 24 09:47:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3DCE16A474 for ; Thu, 24 Jan 2008 09:47:34 +0000 (UTC) (envelope-from cs@wa-sp.com) Received: from csmtp1.b-one.net (csmtp1.one.com [195.47.247.21]) by mx1.freebsd.org (Postfix) with ESMTP id 7424E13C4CE for ; Thu, 24 Jan 2008 09:47:34 +0000 (UTC) (envelope-from cs@wa-sp.com) Received: from [192.168.0.3] (h80n1c1o824.bredband.skanova.com [81.235.28.80]) by csmtp1.b-one.net (Postfix) with ESMTP id 7DBA220023D1; Thu, 24 Jan 2008 10:27:35 +0100 (CET) From: Chris Stromblad To: pyunyh@gmail.com In-Reply-To: <20080124012957.GB18179@cdnetworks.co.kr> References: <4797241D.8080000@wa-sp.com> <20080123123244.GG14495@cdnetworks.co.kr> <47974615.2030901@wa-sp.com> <20080124012957.GB18179@cdnetworks.co.kr> Content-Type: text/plain Organization: WASP Date: Thu, 24 Jan 2008 10:27:31 +0100 Message-Id: <1201166851.8147.18.camel@localhost,> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Dell XPS 1530 - Network card issue - Marvell 88E8040 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2008 09:47:34 -0000 Hi, This is the output from lspci -v: 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 12) Subsystem: Dell Unknown device 022e Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] I/O ports at de00 [size=256] Capabilities: 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) Subsystem: Intel Corporation Unknown device 1021 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at f9eff000 (32-bit, non-prefetchable) [size=4K] Capabilities: I included the wireless data as well because I wanted to ask if you know whether or not this has support from ports? It doesn't get detected when booting FreeBSD so I assume that either it needs a binary blob, or that perhaps there are some drivers in ports that can be installed once I have the wired network functioning properly. Once again thank you very much for your help, and if there is anything else I can do or get you, please let me know! - Chris On Thu, 2008-01-24 at 10:29 +0900, Pyun YongHyeon wrote: > On Wed, Jan 23, 2008 at 02:50:13PM +0100, Chris Stromblad wrote: > > > > > > Pyun YongHyeon wrote: > > >On Wed, Jan 23, 2008 at 12:25:17PM +0100, Chris Stromblad wrote: > > > > (I originally addressed this to the freebsd-hardware, but got no > > > response, > so please forgive me for reposting this here!) > > > > > > > > Hi, > > > > > > > > It appears as if the Marvell 88E8040 is not yet supported by FreeBSD and > > > > specifically the msk(4) driver. I would just like to know if there are > > > any > > > > plans on adding support for the above mentioned NIC. > > > > > > > > > >I'd like to add support 88E8040(Yukon2 FE+ PCIe Fast ethernet > > >controller). I don't think just adding a PCI id is sufficient > > >to make it work but it would be even better if you can send me > > >the 'pciconf -lcv' output to me. > > > > Will I have to download and install FreeBSD in order to provide this > > data, or is there a simpler way of doing it? > > > > Ether Linux or FreeBSD can do that. > If you have to run Linux due to lack of driver on FreeBSD, > send me the output of lspci. > As you said, you have to install FreeBSD first in order to > run "pciconf -lcv". > > If you didn't install FreeBSD yet, just use FreeBSD or Linux > LiveCD to boot the OS and use lspci or pciconf. > > > > > > >I think one of the serious issue of Yukon2 FE+ is introduction > > >of new descriptor format and additional bugs for the chip/phy > > >as other variants. Since there are no documentation for > > >controller/phy hardware, it may take longer than you would > > >expect to see a working/stable driver. I guess disabling TSO and > > >checksum offload may make it possible to write a minimal driver > > >for the hardware. I'll let you know when I have code to test. > > >I cannot say the code written by me would work as I don't have > > >that hardware. > > > > > > > Normally I wouldn't even bother asking, and just shrug and say, tough > > > luck > > > > they don't support it... next distribution. Thing is, I really, really > > > > like FreeBSD. I'm kind of a GNU/Linux guy, but I've never managed to > > > > settle for a distribution and have moved from one to another, never > > > quite > > > > finding something that works with me, and not against me. > > > > > > > > Then I tried FreeBSD, actually I just read much of the available > > > > documentation and I was "converted". _THIS_ is how documentation should > > > be > > > > written; clear, concise, to the point and most of all, USEFUL! Thank > > > you! > > > > > > > > So, my point is that I really want this to work out. I'm willing to give > > > > as much time as necessary to get this driver working. Whether it's just > > > a > > > > little Device_ID change in the source, I don't know. However, if anyone > > > is > > > > up for helping me getting this to work, I'll provide whatever > > > information > > > > I can. > > > > > > > > Many thanks, and keep up the fantastic work on the FreeBSD operating > > > system. > > > > > > > > Regards, > > > > Christoffer Str?mblad > > > > > > > > PS: I've tried 8.0-CURRENT (snapshot from 27122007), 7.0-RC1 and > > > FreeBSD > 6.3, no luck. > > > > -- Chris Stromblad Security Engineer WASP UK Regent Street London, WC2 Dir: +44 207 043 5190