| 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
| ||
|
Message-ID: <20131114210130.0a25733a@alan.etchedpixels.co.uk> Date: Thu, 14 Nov 2013 21:01:30 +0000 From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk> To: David Cohen <david.a.cohen@...ux.intel.com> Cc: matthew.garrett@...ula.com, platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org, eric.ernst@...ux.intel.com, Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com> Subject: Re: [PATCH 2/3] ipc: Enabled ipc support for additional intel platforms On Thu, 14 Nov 2013 09:31:38 -0800 David Cohen <david.a.cohen@...ux.intel.com> wrote: > On 11/14/2013 05:43 AM, One Thousand Gnomes wrote: > > On Wed, 13 Nov 2013 12:14:30 -0800 > > David Cohen <david.a.cohen@...ux.intel.com> wrote: > > > >> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com> > >> > >> Enabled ipc support for penwell, clovertrail & tangier platforms. > > > > At some point this really ought to be discoverable in your SFI, ACPI or > > similar data tables not continually hard coded. > > Agreed. But it depends on fw changes, which I believe to happen on > newer platforms only. On driver side we need to fill the missing > resource info with hardcoded values :/ Oh agreed entirely, but please twist the arms of those responsible and make sure they are very keen to get it into the firmware ACPI tables ASAP.. 8) -- 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/
Powered by blists - more mailing lists