Messages in this thread | | | Date | Thu, 14 Apr 2005 10:34:38 -0700 | From | Tim Hockin <> | Subject | Re: [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode |
| |
On 4/13/05, Dave Jones <davej@redhat.com> wrote:
> If we have a situation where we screw a subset of users with the > config option =y and a different subset with =n, how is this improving > the situation any over what we have today ?
Dave,
What's a good alternative? Do we need to keep a whitelist of hardware that is known to work? A blacklist is pretty risky, since this is a very hard problem to find.
What if it was always on, except when the commandlien was passed (eliminate the CONFIG option)? Really 'leet hacks could tweak a #define if they don't like the command line option..
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |