From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Robert Hancock <hancockr@shaw.ca>, Alexander <aledin@mail.ru>,
linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>
Subject: Re: PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI] Crash on accessing DVD-RAM
Date: Sun, 13 Jan 2008 16:29:59 +0000 [thread overview]
Message-ID: <20080113162959.01d519db@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1200238725.3179.16.camel@localhost.localdomain>
> Yes, I concur for the short term. The other two possible courses of
> action either involve long discussions (the different device one) or
> you'll never quite be sure you got all the paths (the GFP_DMA32 one).
> At least with this one, you know everything will work.
The different device one is tricky because the PCI layer is involved in
mapping on some systems so you can't just magic up a platform device for
it. Putting a mask on the block queue might perhaps work as a model
which avoids breaking stuff by suprise, with the device left at 32bit
masking.
next prev parent reply other threads:[~2008-01-13 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.krOVfyFmB2aqGjJIoHCLmQxecWc@ifi.uio.no>
2008-01-11 5:46 ` Robert Hancock
2008-01-12 8:25 ` Alexander
2008-01-12 19:25 ` Robert Hancock
2008-01-12 20:35 ` James Bottomley
2008-01-12 23:04 ` Robert Hancock
2008-01-12 23:27 ` James Bottomley
2008-01-13 1:38 ` Robert Hancock
2008-01-13 3:12 ` James Bottomley
2008-01-13 13:33 ` Alan Cox
2008-01-13 15:38 ` James Bottomley
2008-01-13 16:29 ` Alan Cox [this message]
2008-01-13 16:51 ` James Bottomley
2008-01-15 1:41 ` Robert Hancock
2008-01-15 2:23 ` James Bottomley
2008-02-01 0:09 ` Robert Hancock
2008-02-01 9:59 ` Alexander
2008-02-04 8:29 ` Alexander
2008-01-10 13:44 Alexander
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=20080113162959.01d519db@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aledin@mail.ru \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®