Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp616501ybi; Fri, 14 Jun 2019 00:03:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqwpc0XvayaZArQkKQTkt9Z7x/1TPpGQdxs0NGJHtRArBtU37Lg3c1gJNBnth+j8GTQEBF8Q X-Received: by 2002:aa7:914e:: with SMTP id 14mr45686827pfi.136.1560495791346; Fri, 14 Jun 2019 00:03:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560495791; cv=none; d=google.com; s=arc-20160816; b=efP+suPU2aiB1SrYfj3koqSYaXiNl069Fj/M6wWalDF7/ga+Mhm7MG8uGfJVLCYs0I 7IUh1zdGXnu54EOfyyR36N8m9JdxeyxFQ9JIuPa7ulDLWYh8lCp8Zg9xg1XRvEYSQ8em 1ZMmhjOznfJa8uIaX0ACsYV7Tbph/+ju0k6OO6QMSAiGIanaz7jOSdbLg2qVgbBKoNUw qBufOrLN26iX960du+iHbRFy5wTQ49GoY+JXGCsPFxBMQFv9d0BKFCllPlFTAwEI6NE0 33mMXhEO23pRkfoxiP7cia+c/iGaJ7oOnCx6lEika3B8b604umMlbJNMX3v+O2OAw3lC QiKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date:dkim-signature; bh=CL9TguztKtV2o3ivNkFUSAfdpXkC0b7RTHVi2QXvc2Y=; b=XZr27fZxfJ7EYBFhUGTCiezXFRg2IKCB14So9pxH8VbJK6HyCOYNilY6vdmlR8SnsU wRD90rdOTedZAAR0TNOofcr/pA5hYxZVi9H287XxcRT/+XtM7NWdz/SlsCP4RxsvM8US qkxs1xAQ8T6zD72dTUyy5eMbzHbcQS7HXQO5OV63WZXOpU4si87CG+UYstHBivp1uLNI zvpRiy6FcDWBzLs4DH7gaK7lT9vgAFwlOJxkr9CVpynjfC3gwpsmeDcZIVZozhIgKWOD XxLbWpsCFGPUN5rQ2irHCvqGsouutnm4oM3atjbXbB8Ac8z9rLY5TP0wecXrYyGcChYS aOMQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@xen0n.name header.s=mail header.b=gMVMFGjQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k193si1787507pgc.473.2019.06.14.00.02.52; Fri, 14 Jun 2019 00:03:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail (test mode) header.i=@xen0n.name header.s=mail header.b=gMVMFGjQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726126AbfFNHCV (ORCPT + 99 others); Fri, 14 Jun 2019 03:02:21 -0400 Received: from [115.28.160.31] ([115.28.160.31]:33790 "EHLO mailbox.box.xen0n.name" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1725780AbfFNHCV (ORCPT ); Fri, 14 Jun 2019 03:02:21 -0400 X-Greylist: delayed 414 seconds by postgrey-1.27 at vger.kernel.org; Fri, 14 Jun 2019 03:02:19 EDT Received: from ld50 (unknown [116.227.76.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailbox.box.xen0n.name (Postfix) with ESMTPSA id 49A406011D; Fri, 14 Jun 2019 14:55:23 +0800 (CST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=xen0n.name; s=mail; t=1560495323; bh=KIsjpnrc1kWTp5mngPR3Kyeg7MjoHz37JvngBJKfgLc=; h=Date:From:To:Cc:Subject:From; b=gMVMFGjQp+7oPQFpt+QkMFgKOYBR7sQOKe1S/hD3ZFWtuwUqQrMOHH5TTZIThER98 rcwnX4kWid+KtKsLH6btPuQ0HU+NInL7eFyQM32DRDT+gLdrKa/yeyS2M9MaoMLd9z AXUy1bgNk7f3AWGkjJ/XgYhiupgXhdG4amz84lzQ= Date: Fri, 14 Jun 2019 14:55:18 +0800 From: WANG Xuerui To: linux-kernel@vger.kernel.org Cc: linux-mips@vger.kernel.org Subject: DMI: support for non-EFI platforms with non-standard SMBIOS entrypoint? Message-ID: <20190614065518.GA53855@ld50> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, There are several MIPS platforms floating around with firmware SMBIOS support, primarily Loongson 3-series, but their SMBIOS entrypoint is non-standard. According to the SMBIOS spec the non-EFI platforms should have the tables in the 000F_0000h-000F_FFFFh physical range, however these boards put the table at 0FFF_E000h. How do we enable DMI for these non-EFI yet non-standard-compliant systems without resorting to firmware fixing, which is not always feasible? It is possible to move the address definition to arch realm with the standard value as default, but I would like to first ask for suggestions, as I am fairly new to kernel development (personal hobby for now). Regards, Xuerui