Jeff Garzik wrote: ..
Sounds like un-blacklisting the drive, and adding ATA_FLAG_NO_FUA is the way to go...
Might as well add sata_mv to that blacklist as well. And while I'm at it, the pdc_adma and sata_qstor controllers/drivers are fine with FUA. -ml - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: Jeff Garzik <[email protected]>
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- References:
- Re: LibPATA code issues / 2.6.15.4
- From: Nicolas Mailhot <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Nicolas Mailhot <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: "Eric D. Mudama" <[email protected]>
- FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: Jeff Garzik <[email protected]>
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: Jeff Garzik <[email protected]>
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: "Eric D. Mudama" <[email protected]>
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: Jeff Garzik <[email protected]>
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: "Eric D. Mudama" <[email protected]>
- Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- From: Jeff Garzik <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- Prev by Date: Re: 2.6.16rc5 'found' an extra CPU.
- Next by Date: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- Previous by thread: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- Next by thread: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
- Index(es):