On Freitag, 3. März 2006 23:23 Jeff Garzik wrote: > I'll happen but not soon. Motivation is low at NV and here as well, > since newer NV is AHCI. The code in question, "NV ADMA", is > essentially legacy at this point -- though I certainly acknowledge > the large current installed base. Just being honest about the > current state of things... I'd like to raise motivation a lot because most MB sold here (central Europe) are Nforce4 with Athlon64x2 at the moment. It would be nice from vendors if they support OSS developers more, as it's their interest to have good drivers. For the moment, I'd recommend *against* using Nforce4 because of that problems we had (and that caused us a lot of unpaid repairing work). Hopefully NV does something quick to resolve the remaining issues, especially as the 4GB "border" is hit more and more often. mfg zmi -- // Michael Monnerie, Ing.BSc --- it-management Michael Monnerie // http://zmi.at Tel: 0660/4156531 Linux 2.6.11 // PGP Key: "lynx -source http://zmi.at/zmi2.asc | gpg --import" // Fingerprint: EB93 ED8A 1DCD BB6C F952 F7F4 3911 B933 7054 5879 // Keyserver: www.keyserver.net Key-ID: 0x70545879
Attachment:
pgpn0rPHO32fd.pgp
Description: PGP signature
- References:
- RE: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
- From: "Allen Martin" <[email protected]>
- Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
- From: Andi Kleen <[email protected]>
- Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
- From: Jeff Garzik <[email protected]>
- RE: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
- Prev by Date: Re: Doubt about scheduler
- Next by Date: Re: [patch 2.6.16-rc5-mm2] sched_cleanup-V17 - task throttling patch 1 of 2
- Previous by thread: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
- Next by thread: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
- Index(es):
 |