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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150617131841.GI13393@katana>
Date:	Wed, 17 Jun 2015 15:18:42 +0200
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	Boaz Harrosh <boaz@...xistor.com>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Rui Wang <ruiv.wang@...il.com>,
	Jean Delvare <jdelvare@...e.de>,
	Alun Evans <alun@...gerous.net>,
	Robert Elliott <Elliott@...com>,
	"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	Paul Bolle <pebolle@...cali.nl>,
	Tony Luck <tony.luck@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] i2c_imc: New driver for Intel's iMC, found on
 LGA2011 chips


> > Having said that, I am still not convinced that the driver should be in the kernel
> > to start with. Browsing through Intel's datasheets, the registers are supported
> > in E5-2600 v1, v2, and v3. However, in v3 Intel added a note saying that the registers
> > should not be accessed by the OS directly, but only through the bios. Given that,
> > and if that is possible, it might make more sense to rely on ACPI. It would then
> > be up to the board and/or BIOS vendor to decide if the information should be available
> > to the OS or not.
> 
> I think the plan is to add something to ACPI to tell us when we can
> use these registers.  Unfortunately I'm not privy to whatever the ACPI
> committee is doing.

Coming from the embedded world and not knowing much about this, I tend
to wait until the above issue is clear, meaning when and how this driver
is safe to be used. I hope you don't mind. Keeping your code up to date
and sharing it is much appreciated, though! As well as Guenter's comments.

Thanks!


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ