lkml.org 
[lkml]   [2008]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 0/9] x86, xsave: xsave/xrstor support
On Fri, Aug 01, 2008 at 04:27:53PM +0200, Rene Herman wrote:
> On 01-08-08 11:51, Ingo Molnar wrote:
>
> >find attached below a newer version of the original list i published
> >half a year ago:
> >
> > http://people.redhat.com/mingo/auto-qa-patches/Kconfig-qa.patch
> >
> >these are just pragmatic local hacks to get things going. (There are
> >more per machine quirks as well.)
> >
> >i have not used a BROKEN annotation because CONFIG_BROKEN is
> >impractical: it just kills code altogether, indiscriminately. There's no
> >way for users to enable CONFIG_BROKEN in the upstream kernel - nothing
> >selects it and it's not an interactive option either.
> >
> >So by all means if we mark a driver or a kernel feature as
> >CONFIG_BROKEN, it's killed altogether for all practical purposes.
> >
> >What we'd need is some more gradual approach: for example a way to mark
> >"drivers that are not expected to boot on a whitebox PC", without
> >removing them altogether via a CONFIG_BROKEN dependency - often it's
> >hardware that cannot be probed safely.
>
> For real ISA at the least, the best fix I feel is just not go grabbing
> resources without anything (ie, ISAPnP) or anyone (ie, the user) telling

Really old systems don't have isapnp. Neither have smbus devices.

> us that's where the hardware's at.

That would mean the users on these systems would need to add tons
of obscure command line options.

-Andi


\
 
 \ /
  Last update: 2008-08-01 16:51    [W:0.162 / U:0.640 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site