From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
Date: Thu, 14 Dec 2006 00:00:48 +0100 [thread overview]
Message-ID: <45808620.30503@scientia.net> (raw)
In-Reply-To: <20061213223944.GA8591@csclub.uwaterloo.ca>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
Lennart Sorensen wrote:
> I upgrade my plextor firmware using linux. pxupdate for most devices,
> and pxfw for new drivers (like the PX760). Works perfectly for me. It
> is one of the reasons I buy plextors.
Yes I know about it,.. although never tested it,... anyway the main
reason for Windows is Exact Audio Copy (but Andre Wiehthoff is working
on a C port :-D )
Unfortunately my PX760 seems to be defect,.. posted about the issue to
lkml but no success :-(
Best wishes,
Chris.
[-- Attachment #2: calestyo.vcf --]
[-- Type: text/x-vcard, Size: 156 bytes --]
begin:vcard
fn:Mitterer, Christoph Anton
n:Mitterer;Christoph Anton
email;internet:calestyo@scientia.net
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2006-12-13 23:00 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0612021202000.2981@addx.localnet>
2006-12-11 9:24 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Karsten Weiss
2006-12-12 6:18 ` amd64 iommu causing corruption? (was Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!) Chris Wedgwood
2006-12-13 19:18 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Christoph Anton Mitterer
2006-12-13 19:53 ` Chris Wedgwood
2006-12-13 20:34 ` Karsten Weiss
2006-12-14 9:22 ` Muli Ben-Yehuda
2006-12-14 11:38 ` [PATCH] " Karsten Weiss
2006-12-14 11:56 ` Muli Ben-Yehuda
2006-12-14 13:16 ` [PATCH 2nd try] " Karsten Weiss
2006-12-14 18:10 ` Muli Ben-Yehuda
2006-12-23 2:04 ` Christoph Anton Mitterer
2006-12-23 2:56 ` John A Chaves
2006-12-23 3:26 ` Christoph Anton Mitterer
2006-12-13 19:20 ` Christoph Anton Mitterer
2006-12-13 19:54 ` Chris Wedgwood
2006-12-13 19:57 ` Christoph Anton Mitterer
2006-12-13 22:39 ` Lennart Sorensen
2006-12-13 23:00 ` Christoph Anton Mitterer [this message]
2006-12-13 19:53 ` Erik Andersen
2006-12-13 19:59 ` Karsten Weiss
2006-12-13 20:02 ` Christoph Anton Mitterer
2006-12-13 20:29 ` Erik Andersen
2006-12-13 20:32 ` Christoph Anton Mitterer
2006-12-13 23:33 ` Christoph Anton Mitterer
2006-12-14 9:24 ` Muli Ben-Yehuda
2006-12-14 19:23 ` Christoph Anton Mitterer
2006-12-14 9:23 ` Muli Ben-Yehuda
2006-12-14 9:52 ` Erik Andersen
2006-12-14 9:56 ` Muli Ben-Yehuda
2007-01-03 15:02 ` Christoph Anton Mitterer
2007-01-04 13:04 ` Christoph Anton Mitterer
2007-03-22 14:48 Dan Halbert
[not found] <fa.E9jVXDLMKzMZNCbslzUxjMhsInE@ifi.uio.no>
2007-01-03 23:41 ` Robert Hancock
2007-01-15 22:56 ` Christoph Anton Mitterer
2007-01-15 23:05 ` Christoph Anton Mitterer
2007-01-16 0:23 ` Robert Hancock
2007-01-16 13:54 ` Christoph Anton Mitterer
2007-01-16 14:26 ` Robert Hancock
2007-03-22 12:32 ` Christoph Anton Mitterer
-- strict thread matches above, loose matches on Subject: below --
2006-12-15 15:57 Paul Slootman
2006-12-02 0:56 Christoph Anton Mitterer
2006-12-02 1:15 ` Erik Andersen
2006-12-02 1:28 ` Christoph Anton Mitterer
2006-12-02 5:17 ` Chris Wedgwood
2006-12-02 12:10 ` Christoph Anton Mitterer
[not found] ` <20061202111644.GF9995@vianova.fi>
2006-12-08 2:16 ` Christoph Anton Mitterer
2006-12-02 11:00 ` Karsten Weiss
2006-12-02 11:37 ` Alan
2006-12-02 11:39 ` Christoph Anton Mitterer
2006-12-13 18:52 ` Christoph Anton Mitterer
2006-12-13 19:56 ` Karsten Weiss
2006-12-13 20:11 ` Christoph Anton Mitterer
2006-12-14 9:34 ` Chris Wedgwood
2007-01-15 22:26 ` Christoph Anton Mitterer
2006-12-14 23:39 ` Dax Kelson
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=45808620.30503@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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.