On Wed, Dec 19, 2012 at 11:47:00PM +0100, Igor Mammedov wrote:
On Wed, 19 Dec 2012 15:38:09 -0200
Eduardo Habkost ehabk...@redhat.com wrote:
On Mon, Dec 17, 2012 at 05:01:23PM +0100, Igor Mammedov wrote:
commit d480e1af which introduced vendor property was setting
On Mon, Dec 17, 2012 at 05:01:23PM +0100, Igor Mammedov wrote:
commit d480e1af which introduced vendor property was setting
env-cpuid_vendor_override = 1, which prevents using vendor property
on its own without triggering vendor override.
Fix it by removing setting cpuid_vendor_override in
Am 19.12.2012 18:38, schrieb Eduardo Habkost:
On Mon, Dec 17, 2012 at 05:01:23PM +0100, Igor Mammedov wrote:
commit d480e1af which introduced vendor property was setting
env-cpuid_vendor_override = 1, which prevents using vendor property
on its own without triggering vendor override.
Fix it
On Wed, 19 Dec 2012 15:38:09 -0200
Eduardo Habkost ehabk...@redhat.com wrote:
On Mon, Dec 17, 2012 at 05:01:23PM +0100, Igor Mammedov wrote:
commit d480e1af which introduced vendor property was setting
env-cpuid_vendor_override = 1, which prevents using vendor property
on its own without
commit d480e1af which introduced vendor property was setting
env-cpuid_vendor_override = 1, which prevents using vendor property
on its own without triggering vendor override.
Fix it by removing setting cpuid_vendor_override in x86_cpuid_set_vendor()
to allow to use vendor property in other places
