linux-kernel - Re: [PATCH 1/2] ibft: Update iBFT handling for v1.03 of the spec.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BEAB683.8040600@redhat.com>
Date:	Wed, 12 May 2010 10:09:07 -0400
From:	Peter Jones <pjones@...hat.com>
To:	Len Brown <lenb@...nel.org>
CC:	Konrad Rzeszutek Wilk <konrad@...nel.org>,
	linux-kernel@...r.kernel.org, gpxe-devel@...erboot.org
Subject: Re: [PATCH 1/2] ibft: Update iBFT handling for v1.03 of the spec.

On 05/12/2010 01:26 AM, Len Brown wrote:
> 
>>  #define IBFT_SIGN "iBFT"
> ...
>> +#ifdef CONFIG_ACPI
>> +	/*
>> +	 * One spec says "IBFT", the other says "iBFT". We have to check
>> +	 * for both.
>> +	 */
> 
> Really?
> Which one do you see in the field?

Well, we haven't seen any ACPI-based hardware yet AFAIK - but I'm supposed to
have some soon.  So it's too early to tell which one is actually going to be
the more common case, or if this is really a non-issue.

> any reason to #define "iBFT" above and not use it below?

Nope, that's just an error.  I'll send a patch.

> 
>> +	if (!ibft_addr)
>> +		acpi_table_parse(ACPI_SIG_IBFT, acpi_find_ibft);
>> +	if (!ibft_addr)
>> +		acpi_table_parse("iBFT", acpi_find_ibft);
>> +#endif /* CONFIG_ACPI */
> 
> Len Brown, Intel Open Source Technology Center


-- 
        Peter

Obviously, a major malfunction has occurred.
		-- Steve Nesbitt, voice of Mission Control, January 28, 1986
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/