On Friday 09 January 2009 11:59:28 Len Brown wrote:
> > > > In such case the boot option of "acpi=rsdt" is provided so that
> > > > RSDT is tried instead of XSDT table when the system can't work well.
> >
> > Great, now we still need a dmi blacklist with machines which are known
> > broken. Then we are at the patchset I posted about a year ago -> scnr.
> >
> > I am going to post the missing two patches to make R40e and R50e work.
>
> please do not.
>
> this option is just for manual debugging.
> as i wrote when i nacked your original series,
> the object should be to figure out which path to take w/o using dmi.
It's not possible (maybe someone has an idea, there wasn't any yet).
Either you always use it or not, you cannot check for much, because it is
too early.
If it's always used, I expect it's not the RSDT that should be taken, but
the 32 bit addresses of the RSDT/XSDT.
IMO this cannot generally be done, because chances are high that machines
which do not support Windows likely will break.
Chances are high that a machine which does not support Windows uses 64 bit
addresses and leaves the 32 bit ones uninitialized, a spec valid configuration
which will then break.
Also: Until the object (figure out which path to take w/o using dmi) is
achieved, these machines should work properly, right?
This task seem to not be easy and unsuccessfully took several kernel
iterations already,
So why can't these simple patches just be added and the machines be fixed
until eventually at some time this will generally be fixed?
Thomas
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
