linux-kernel - Re: [PATCH 1/4] x86: base support for the TS-5500 platform

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] [day] [month] [year] [list]

Message-ID: <20110826200040.2025eb0b@v0nbox>
Date:	Fri, 26 Aug 2011 20:00:40 -0400
From:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 1/4] x86: base support for the TS-5500 platform

On Wed, 24 Aug 2011 16:04:13 -0700,
"H. Peter Anvin" <hpa@...or.com> wrote:

> On 08/24/2011 03:38 PM, Vivien Didelot wrote:
> > 
> > I agree with you. The platform does not provide many identification
> > points. We have specific hardware such as the CPU, Ethernet, Cardbus
> > and USB controllers; there is no DMI available; no PCI bridge
> > subvendor info, only the BIOS provides a 16-bit identification
> > call... We discussed that point in
> > https://lkml.org/lkml/2011/5/4/437 without success.
> > 
> > What would be the proper way in your opinion?
> > 
> > Vivien.
> 
> First of all, given that these clowns seem to be selling a product
> specifically targeting Linux support, they really need to be given a
> clue transfusion.  It is *NOT* acceptable to not provide DMI, and
> *NOT* acceptable not to set the subvendor information.
> 
> We should arguably push for them to fix that in their BIOSes, but that
> is as usual too little, too late.
> 
> Probably the best option we have is to look for some kind of magic
> string in their BIOS -- i.e. the classic way to detect things before
> DMI existed.
> 
> If not, you're going to have an explicit switch on the kernel command
> line, but that is an absolute last resort.
> 
> 	-hpa

Hi,

The initialization function is now reading the BIOS to find this magic
string, thanks for the tip. I've sent the updated version. The
corresponding thread is here: https://lkml.org/lkml/2011/8/26/425.

Regards,
Vivien.
--
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/