Maybe not exactly "running", but at the very least, ACPICA must be initialized.
All of this of course depends on how early the table needs to be loaded. > -----Original Message----- > From: Thomas Renninger [mailto:tr...@suse.de] > Sent: Tuesday, February 18, 2014 10:53 AM > To: Moore, Robert > Cc: x...@kernel.org; c...@conrad-kostecki.de; linux-kernel@vger.kernel.org; > mi...@redhat.com; h...@zytor.com; t...@linutronix.de; de...@acpica.org > Subject: Re: [Devel] ACPI: Also allow ACPI table adding via initrd not > only overriding > > On Tuesday, February 18, 2014 06:38:45 PM Moore, Robert wrote: > > acpi_load_table won't work? > > I guess not, there is: > /* Must acquire the interpreter lock during this operation */ > status = acpi_ut_acquire_mutex(ACPI_MTX_INTERPRETER); > > So the interpreter must be running already? > That would mean the adding can only happen much later. > This probably would eleminate most use cases for adding arbitrary ACPI > tables. Most tables (beside DSDT and SSDT) are needed really early, > otherwise the info could have been added as AML as well. > > Thomas > > > > -----Original Message----- > > > From: Devel [mailto:devel-boun...@acpica.org] On Behalf Of Thomas > > > Renninger > > > Sent: Tuesday, February 18, 2014 10:23 AM > > > Cc: x...@kernel.org; c...@conrad-kostecki.de; > > > linux-kernel@vger.kernel.org; mi...@redhat.com; h...@zytor.com; > > > t...@linutronix.de; de...@acpica.org > > > Subject: [Devel] ACPI: Also allow ACPI table adding via initrd not > > > only overriding > > > > > > The ACPICA patches have to go into separate acpica repository first. > > > It should also be checked in acpica whether the table signature the > > > OS likes to add already exists (from BIOS). In this case the table > > > must not be added. > > > > > > Worked here by trying to override a DSDT and addind a BGRT table. > > > > > > Thomas > > > > > > _______________________________________________ > > > Devel mailing list > > > de...@acpica.org > > > https://lists.acpica.org/mailman/listinfo/devel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
