From: Jeff Garzik <jeff@garzik.org>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Tejun Heo <htejun@gmail.com>, Jens Axboe <axboe@suse.de>,
Mark Lord <liml@rtr.ca>
Subject: Random libata notes
Date: Sat, 04 Mar 2006 12:33:40 -0500 [thread overview]
Message-ID: <4409CF74.7030808@garzik.org> (raw)
These are small TODO bits that I didn't want to forget... Patches welcome.
1) ATAPI edge case. Due to adding the padding s/g entry, we must adjust
sg_tablesize to include ' - 1' for each driver
2) ata_scsi_slave_config() hardcodes a call to
blk_queue_max_phys_segments(, LIBATA_MAX_PRD), when the value passed
should not be so limited on nice hardware like AHCI.
3) sata_mv: add back SCR_ERR clear?
mv_scr_write(ap, SCR_ERROR, mv_scr_read(ap, SCR_ERROR));
4) sata_mv: set DMA mask
next reply other threads:[~2006-03-04 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 17:33 Jeff Garzik [this message]
2006-03-10 14:20 ` Random libata notes Tejun Heo
2006-03-10 14:33 ` Tejun Heo
2006-03-12 1:37 ` Jeff Garzik
2006-03-13 11:40 ` Tejun Heo
2006-03-12 1:35 ` Jeff Garzik
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=4409CF74.7030808@garzik.org \
--to=jeff@garzik.org \
--cc=axboe@suse.de \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).