Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758961Ab2EON5b (ORCPT ); Tue, 15 May 2012 09:57:31 -0400 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:45072 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752402Ab2EON5a (ORCPT ); Tue, 15 May 2012 09:57:30 -0400 Date: Tue, 15 May 2012 15:00:15 +0100 From: Alan Cox To: Gleb Natapov Cc: Hannes Reinecke , LKML , "H. Peter Anvin" Subject: Re: [PATCH] EDD: Check for correct EDD 3.0 length Message-ID: <20120515150015.5bf17aea@pyramind.ukuu.org.uk> In-Reply-To: <20120515115917.GK32036@redhat.com> References: <1337079889-62380-1-git-send-email-hare@suse.de> <20120515111255.GJ32036@redhat.com> <4FB23C09.7060300@suse.de> <20120515115917.GK32036@redhat.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1296 Lines: 26 > T13 EDD4.0 actually supply enough information to link edd entry to actual > device (another spec does not), I do not see support for other spec to > be important, but you are welcome to write support for it if you need > it. The only way I see to check what spec edd info corresponds to is to > calculate checksum according to both specs and see which one succeeds. I also think you are confused on this: EDD 3.0 provides enough information to link most types of hardware to the device. It provides the PCI or Legacy path to the interface and the device LUN, or for 1394 etc the WWID which can be used to cross match. It doesn't address port multipliers. EDD 1.1 provides sufficient information for old systems too via the FDPT as they only have to deal with MFM/IDE/ATA controllers at the legacy mappings and these are described by the FDPT. Prior to that it gets a bit more interesting and you have to go poking in BIOS magic and have the required spellbooks to hand. However right back to the original 386 era PCs the data is available. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/