On 08/02/2012 04:05 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 08/02/2012 01:32 PM, Anthony Liguori wrote:
Corey Minyard tcminy...@gmail.com writes:
On 08/01/2012 09:40 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 08/01/2012 08:15
On 08/01/2012 09:40 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 08/01/2012 08:15 PM, Kevin O'Connor wrote:
Well, I should also probably add the ACPI name space definition for this
information, too, and the SMBIOS information is not capable of passing
all the
Corey Minyard tcminy...@gmail.com writes:
On 08/01/2012 09:40 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 08/01/2012 08:15 PM, Kevin O'Connor wrote:
Well, I should also probably add the ACPI name space definition for this
information, too, and the SMBIOS
On 08/02/2012 01:32 PM, Anthony Liguori wrote:
Corey Minyard tcminy...@gmail.com writes:
On 08/01/2012 09:40 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 08/01/2012 08:15 PM, Kevin O'Connor wrote:
Well, I should also probably add the ACPI name space definition for
Corey Minyard cminy...@mvista.com writes:
On 08/02/2012 01:32 PM, Anthony Liguori wrote:
Corey Minyard tcminy...@gmail.com writes:
On 08/01/2012 09:40 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 08/01/2012 08:15 PM, Kevin O'Connor wrote:
Well, I should also
On Mon, Jul 30, 2012 at 12:25:16PM -0500, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 07/30/2012 10:37 AM, Anthony Liguori wrote:
miny...@acm.org writes:
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS supports this. So add
On 08/01/2012 08:15 PM, Kevin O'Connor wrote:
This approach, unfortunately, leads to extra code and double
handling of infomation.
The ultimate consumer of the data wants a binary struct which looks
like:
struct smbios_type_38 {
struct smbios_structure_header header;
u8
Corey Minyard cminy...@mvista.com writes:
On 08/01/2012 08:15 PM, Kevin O'Connor wrote:
This approach, unfortunately, leads to extra code and double
handling of infomation.
The ultimate consumer of the data wants a binary struct which looks
like:
struct smbios_type_38 {
struct
miny...@acm.org writes:
From: Corey Minyard cminy...@mvista.com
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS supports this. So add a function to do this.
This is in preparation for the IPMI handler adding it's SMBIOS table
entry.
Signed-off-by:
On 07/30/2012 10:37 AM, Anthony Liguori wrote:
miny...@acm.org writes:
From: Corey Minyard cminy...@mvista.com
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS supports this. So add a function to do this.
This is in preparation for the IPMI handler
Corey Minyard cminy...@mvista.com writes:
On 07/30/2012 10:37 AM, Anthony Liguori wrote:
miny...@acm.org writes:
From: Corey Minyard cminy...@mvista.com
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS supports this. So add a function to do this.
On 07/30/2012 12:25 PM, Anthony Liguori wrote:
Corey Minyard cminy...@mvista.com writes:
On 07/30/2012 10:37 AM, Anthony Liguori wrote:
miny...@acm.org writes:
From: Corey Minyard cminy...@mvista.com
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS
From: Corey Minyard cminy...@mvista.com
There was no way to directly add a table entry to the SMBIOS table,
even though the BIOS supports this. So add a function to do this.
This is in preparation for the IPMI handler adding it's SMBIOS table
entry.
Signed-off-by: Corey Minyard
13 matches
Mail list logo
