* [PATCHv2] edd: support original Phoenix EDD 3.0 information
@ 2015-05-21 7:39 Hannes Reinecke
2015-05-21 7:40 ` Hannes Reinecke
0 siblings, 1 reply; 2+ messages in thread
From: Hannes Reinecke @ 2015-05-21 7:39 UTC (permalink / raw)
To: H. Peter Anvin
Cc: linux-kernel, Johannes Thumshirn, Hannes Reinecke, Paul Bolle
The original Phoenix EDD 3.0 specification (as found in
eg http://mbldr.sourceforge.net/specsedd30.pdf) has a
device path length of 36, not 44.
All the other fields are identical, so we can trivially support
both formats.
Cc: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Hannes Reinecke <hare@suse.de>
---
drivers/firmware/edd.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/firmware/edd.c b/drivers/firmware/edd.c
index e229576..92bc0e8 100644
--- a/drivers/firmware/edd.c
+++ b/drivers/firmware/edd.c
@@ -8,6 +8,8 @@
* BIOS Enhanced Disk Drive Services (EDD)
* conformant to T13 Committee www.t13.org
* projects 1572D, 1484D, 1386D, 1226DT
+ * and the original Phoenix BIOS EDD 3.0 spec from
+ * <http://mbldr.sourceforge.net/specsedd30.pdf>
*
* This code takes information provided by BIOS EDD calls
* fn41 - Check Extensions Present and
@@ -545,8 +547,9 @@ edd_has_edd30(struct edd_device *edev)
}
- /* We support only T13 spec */
- if (info->params.device_path_info_length != 44)
+ /* We support T13 d1572 and the original Phoenix spec */
+ if (info->params.device_path_info_length != 44 &&
+ info->params.device_path_info_lenght != 36)
return 0;
for (i = 30; i < info->params.device_path_info_length + 30; i++)
--
1.8.5.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCHv2] edd: support original Phoenix EDD 3.0 information
2015-05-21 7:39 [PATCHv2] edd: support original Phoenix EDD 3.0 information Hannes Reinecke
@ 2015-05-21 7:40 ` Hannes Reinecke
0 siblings, 0 replies; 2+ messages in thread
From: Hannes Reinecke @ 2015-05-21 7:40 UTC (permalink / raw)
To: H. Peter Anvin; +Cc: linux-kernel, Johannes Thumshirn, Paul Bolle
On 05/21/2015 09:39 AM, Hannes Reinecke wrote:
> The original Phoenix EDD 3.0 specification (as found in
> eg http://mbldr.sourceforge.net/specsedd30.pdf) has a
> device path length of 36, not 44.
> All the other fields are identical, so we can trivially support
> both formats.
>
> Cc: Paul Bolle <pebolle@tiscali.nl>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
> drivers/firmware/edd.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/edd.c b/drivers/firmware/edd.c
> index e229576..92bc0e8 100644
> --- a/drivers/firmware/edd.c
> +++ b/drivers/firmware/edd.c
> @@ -8,6 +8,8 @@
> * BIOS Enhanced Disk Drive Services (EDD)
> * conformant to T13 Committee www.t13.org
> * projects 1572D, 1484D, 1386D, 1226DT
> + * and the original Phoenix BIOS EDD 3.0 spec from
> + * <http://mbldr.sourceforge.net/specsedd30.pdf>
> *
> * This code takes information provided by BIOS EDD calls
> * fn41 - Check Extensions Present and
> @@ -545,8 +547,9 @@ edd_has_edd30(struct edd_device *edev)
> }
>
>
> - /* We support only T13 spec */
> - if (info->params.device_path_info_length != 44)
> + /* We support T13 d1572 and the original Phoenix spec */
> + if (info->params.device_path_info_length != 44 &&
> + info->params.device_path_info_lenght != 36)
> return 0;
>
> for (i = 30; i < info->params.device_path_info_length + 30; i++)
>
No for gods sake.
My mailer must really hate me.
Next try will follow ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-05-21 7:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-21 7:39 [PATCHv2] edd: support original Phoenix EDD 3.0 information Hannes Reinecke
2015-05-21 7:40 ` Hannes Reinecke
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox