linux-kernel - Re: AW: AW: AW: [PATCH] x86: HPET force enable for Soekris net6501

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]

Date:	Tue, 9 Sep 2014 17:41:33 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Eric Sesterhenn <eric.sesterhenn@...xperts.de>,
	Conrad Kostecki <ck@...rad-kostecki.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"x86@...nel.org" <x86@...nel.org>,
	"mingo@...hat.com" <mingo@...hat.com>
Subject: Re: AW: AW: AW: [PATCH] x86: HPET force enable for Soekris net6501

On Tue, 9 Sep 2014, H. Peter Anvin wrote:

> On 09/09/2014 07:54 AM, Thomas Gleixner wrote:
> > 
> > @hpa: You asked whether this might affect any other e6xx devices.
> > 
> > According to the atom e6xx-series datasheet the HPET is non optional
> > and always memory mapped to 0xfed00000. I don't see how that would
> > harm any machine which has the hpet proper advertised via ACPI.
> > 
> 
> That seems straightforward then.
> 
> I still wish someone would take a cluebat to Soekris.  We keep hearing
> crap like this about their firmware over and over and over again.  It
> isn't like you can't get EDK2 or Coreboot and build a BIOS based mostly
> on Open Source components these days... oh, wait.

You can, but I have a non soekris e6xx platform with a BLDK based BIOS
which lacks ACPI and some other features....

--
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/