From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 13 20:13:36 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 AD86D106566C for ; Thu, 13 Mar 2008 20:13:36 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 2A9008FC27 for ; Thu, 13 Mar 2008 20:13:35 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so589876uge.37 for ; Thu, 13 Mar 2008 13:13:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=kAaUxZgiymDnQEmiVSX4u11CdYDDisRgeneRIpBSuVo=; b=cAoYT99B+slan/90dgYkp/NFxsuvERZK1MMNPi3lEcZwvRPFUH9UGb3HB54GoF1huPT/g8KJ+vXirTe5XwvutkkugKgJBbtZEDXRNiAQ813cTHFz0MufB6Oh3RxmjY9DnzsLEuZc/nmB+srDXtzZGg0HptyG2zpKrJXIS4yaugY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=R0sNTKnY9qAFVFvqM7uT/G3HNQq1yAO0w8ixKXRyksDGy/k7pqlrvXVotuZzuTMxh3umQyZA7CPZLizMXZ4NQfduszIgRogiuNMSNoiIBE+mZgKsqFWjMeQ4AiN59qTMk4mqb+CUdgapXjyhRRecFr2rKmZqs7yZG+e8eU3eCj8= Received: by 10.151.61.9 with SMTP id o9mr879048ybk.139.1205439213640; Thu, 13 Mar 2008 13:13:33 -0700 (PDT) Received: by 10.150.230.16 with HTTP; Thu, 13 Mar 2008 13:13:33 -0700 (PDT) Message-ID: <3c0b01820803131313u5c848401q6f0b55d6b76c1809@mail.gmail.com> Date: Thu, 13 Mar 2008 16:13:33 -0400 From: "Alexander Sack" To: gary.jennejohn@freenet.de In-Reply-To: <20080313205006.333c6c26@peedub.jennejohn.org> MIME-Version: 1.0 References: <1841496593.20080313175115@gulfstream.by> <20080313191621.1772d40a@peedub.jennejohn.org> <3c0b01820803131149s67cac66vae6834f1480c0aaa@mail.gmail.com> <20080313205006.333c6c26@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: new SATA chipsets support 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, 13 Mar 2008 20:13:36 -0000 On Thu, Mar 13, 2008 at 3:50 PM, Gary Jennejohn wrote: > On Thu, 13 Mar 2008 14:49:52 -0400 > "Alexander Sack" wrote: > > > On Thu, Mar 13, 2008 at 2:16 PM, Gary Jennejohn < > gary.jennejohn@freenet.de> > > wrote: > > > > > > I can't speak to this, but why not use a board which is already known > > > to work? I'm using a Gigabyte M61P-S3 myself. > > > > > > > I think that drivers from ASUS ( > > > > http://support.asus.com/download/download.aspx?SLanguage=en-en&model=M2N-SLI%20Deluxe > ) > > > may not work with FreeBSD? > > > > > > > > > > These are guaranteed not to work, unless you want to port the Linux > > > drivers. > > > > > > I see that 7.0-RELEASE has ATA Nvidia chipset support. Does that not > cover > > the SATA nvidia chipsets of their unified MCP chipset? I'm just curious > if > > this could be fixed by adding this particular chipset PCI information to > > struct ata_nvidia_ident in sys/dev/ata/ata-chipset.c. It looks MCP55 is > > certainly supported but again I'm stabbing slightly in the dark since I > > don't know SATA NV. > > > > Sorry if this is totally off. I'm new to the FreeBSD kernel but not > SATA > > driver development in general. Its just a thought... > > > > Well, according to "man ata" the nforce[23] MCP (among other nvidia > chipsets) are supported. My motherboard has MCP61 which works just fine. > But I'm no expert on nvidia chip sets and can't really evaluate whether > just adding the PCI information will work. > Yea I don't know either since I don't have an Nvidia spec laying around in front of me! What I would do is cross reference the PCI BoardId in the Linux SATA NV chipset driver and see if its supported. If so, there is a good chance that by adding the proper PCI information the ata infrastructure would just take over. Again, I don't know the exact MCP this motherboard is using. Cheers! -aps -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson