Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1596284

Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache

From Andy Lutomirski <luto@amacapital.net>
Newsgroups linux.kernel
Subject Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache
Date 2017-03-09 19:20 +0100
Message-ID <tjaPo-rT-11@gated-at.bofh.it> (permalink)
References <qV5Vg-kA-3@gated-at.bofh.it> <tjaw2-8vb-15@gated-at.bofh.it> <tjaw2-8vb-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Mar 9, 2017 at 9:51 AM, Arjan van de Ven <arjan@linux.intel.com> wrote:
> On 3/9/2017 9:48 AM, Julian Brost wrote:
>
>> I'm note entirely sure whether it's actually the kernel or HP to blame,
>> but for now, hp-health is completely broken on 4.9 (probably on
>> everything starting from 4.6), so this patch should be reviewed again.
>
>
> it looks like another kernel driver is doing a conflicting mapping.
> do these HP tools come with their own kernel drivers or are those in the
> upstream kernel nowadays?
>

I assume that the kernel DMI driver itself is now a conflicting
mapping.  I wonder if it could register some kind of resource so that
/dev/mem knows to just map it writeback.

On the other hand, the right answer is to use /sys/firmware/dmi.  I'm
not sure the kernel ABI stability guarantee applies to /dev/mem.

--Andy

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache Arjan van de Ven <arjan@linux.intel.com> - 2017-03-09 19:00 +0100
  Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache Julian Brost <julian.brost@fau.de> - 2017-03-09 19:10 +0100
  Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache Andy Lutomirski <luto@amacapital.net> - 2017-03-09 19:20 +0100

csiph-web