All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Thonke <iogl64nx@gmail.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Lee Revell <rlrevell@joe-job.com>,
	lgb@lgb.hu, Allen Martin <AMartin@nvidia.com>,
	linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: NCQ support NVidia NForce4 (CK804) SATAII
Date: Thu, 11 Aug 2005 19:44:49 +0200	[thread overview]
Message-ID: <42FB8E91.9040905@gmail.com> (raw)
In-Reply-To: <20050811172718.GJ31019@csclub.uwaterloo.ca>

Lennart Sorensen schrieb:

>On Thu, Aug 11, 2005 at 01:20:56PM -0400, Jeff Garzik wrote:
>  
>
>>What specifically does not work, on VIA+AMD64 combination, under Linux?
>>
>>My Athlon64 with VIA chipset works great.
>>    
>>
>
>Mine does too.  Asus A8V Deluxe.  No problems so far.  Everything on the
>board I have tried just works.
>  
>
AMD X2 DualCore?

>Can't say my A7N8X-E Deluxe has any real issues either.  I may only get
>ac97 audio level out of the nifty DSP, but I hardly use sound on the
>system anyhow, so I don't mind.  forcedeth driver works for networking,
>sil3112a sata works with WD drives no problem, nvidia ide controller
>seems to work fine with dvd drives, firewire works, yukon sk98lin works
>  
>
Yes, Marvell, Silicon Image  no problem as they provide OpenSource drivers.
On a normal setup is  nearly everything okay.

I hold up a hardware testlab  to find b** *features* the specification 
don't show/hold.
Things that can go scary for production usage - that's my job.

>too, usb is fine.  No complaints from me.
>  
>
USB works also great for all chipsets :-)

>Len Sorensen
>
>  
>
Michael

-- 
Michael Thonke
IT-Systemintegrator /
System- and Softwareanalyist




  reply	other threads:[~2005-08-11 17:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 20:53 NCQ support NVidia NForce4 (CK804) SATAII Allen Martin
2005-08-10 21:31 ` Lennart Sorensen
2005-08-11  7:09 ` Gábor Lénárt
2005-08-11 13:05   ` Lee Revell
2005-08-11 15:17     ` Michael Thonke
2005-08-11 15:22       ` Lee Revell
2005-08-11 15:43         ` Michael Thonke
2005-08-11 16:18           ` Roger Heflin
2005-08-11 16:32             ` Michael Thonke
2005-08-12 19:02             ` Jan Engelhardt
2005-08-11 15:39       ` Diego Calleja
2005-08-12  6:17         ` Gábor Lénárt
2005-08-11 17:20       ` Jeff Garzik
2005-08-11 17:27         ` Lennart Sorensen
2005-08-11 17:44           ` Michael Thonke [this message]
2005-08-11 17:48             ` Lennart Sorensen
2005-08-11 19:29             ` Heikki Orsila
2005-08-11 17:38         ` Michael Thonke
2005-08-11 17:46           ` Jeff Garzik
2005-08-11 17:57             ` Michael Thonke
2005-08-11 18:32               ` Jeff Garzik
2005-08-11 18:55                 ` Michael Thonke
2005-08-11 18:04           ` Lennart Sorensen
2005-08-11 18:17             ` Michael Thonke
2005-08-12 20:10           ` Andre Tomt
2005-08-11 15:09 ` Michael Thonke
2005-08-15  6:01 ` Christopher Chan
     [not found] <fa.psg95ip.1emqnop@ifi.uio.no>
2005-08-14 13:29 ` Willem Riede
2005-08-14 15:18   ` Lion Vollnhals
2005-08-15 13:42     ` Stephen Frost
2005-08-18 14:23       ` Chris Wedgwood
     [not found] <DBFABB80F7FD3143A911F9E6CFD477B004FAE3E7@hqemmail02.nvidia.com.suse.lists.linux.kernel>
     [not found] ` <20050811070943.GB8025@vega.lgb.hu.suse.lists.linux.kernel>
     [not found]   ` <1123765523.32375.10.camel@mindpipe.suse.lists.linux.kernel>
     [not found]     ` <42FB6C27.1010408@gmail.com.suse.lists.linux.kernel>
     [not found]       ` <42FB88F8.7040807@pobox.com.suse.lists.linux.kernel>
2005-08-11 18:44         ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 19:17 linux
2005-08-10 18:59 Allen Martin
2005-08-10 18:11 Michael Thonke
2005-08-10 18:18 ` Jeff Garzik
2005-08-10 18:28   ` Michael Thonke
2005-08-10 18:52   ` Michael Thonke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42FB8E91.9040905@gmail.com \
    --to=iogl64nx@gmail.com \
    --cc=AMartin@nvidia.com \
    --cc=jgarzik@pobox.com \
    --cc=lgb@lgb.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=rlrevell@joe-job.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.