Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)

Nicolas Mailhot wrote:

The controller in the bugzilla entry ie a SiI 3114.
It was a quick fix and I did expect more thorough investigation later
(probably 2.6.17 frame). Though it seems FUA-related problems are so
numerous FUA itself will be blacklisted for 2.6.16, so the limited
blacklist is no longer needed.

Well, we're looking for a long term solution :)

Disabling FUA by default in 2.6.16 is a temporary solution.

	Jeff


-
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/

---

• 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: "Nicolas Mailhot" <[email protected]>

• Prev by Date: Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
• Next by Date: [PATCH] proc: Use sane permission checks on the /proc/<pid>/fd/ symlinks.
• Previous by thread: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
• Next by thread: 2.6.16-rc3: another issue: x86_64 with ATI chipsets
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]