Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1596266 > unrolled thread
| Started by | Arjan van de Ven <arjan@linux.intel.com> |
|---|---|
| First post | 2017-03-09 19:00 +0100 |
| Last post | 2017-03-09 19:20 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Arjan van de Ven <arjan@linux.intel.com> |
|---|---|
| Date | 2017-03-09 19:00 +0100 |
| Subject | Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache |
| Message-ID | <tjaw2-8vb-13@gated-at.bofh.it> |
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?
[toc] | [next] | [standalone]
| From | Julian Brost <julian.brost@fau.de> |
|---|---|
| Date | 2017-03-09 19:10 +0100 |
| Message-ID | <tjaFI-ma-25@gated-at.bofh.it> |
| In reply to | #1596266 |
[Multipart message — attachments visible in raw view] — view raw
On 09.03.2017 18:51, Arjan van de Ven 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? > We don't have any third-party modules loaded. The hp-health package from https://downloads.linux.hpe.com/SDR/repo/mcp/debian/ does not include any kernel modules either. Regards, Julian
[toc] | [prev] | [next] | [standalone]
| From | Andy Lutomirski <luto@amacapital.net> |
|---|---|
| Date | 2017-03-09 19:20 +0100 |
| Message-ID | <tjaPo-rT-11@gated-at.bofh.it> |
| In reply to | #1596266 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web