From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Winkler, Tomas" <tomas.winkler-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Sakkinen,
Jarkko" <jarkko.sakkinen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Davide Guerri
<davide.guerri-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Intel NUC and fTPM issue on 4.9.2
Date: Fri, 17 Feb 2017 09:43:32 -0700 [thread overview]
Message-ID: <20170217164332.GB30677@obsidianresearch.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B54395CD5-Jy8z56yoSI8MvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, Feb 16, 2017 at 10:36:40PM +0000, Winkler, Tomas wrote:
> This is a BIOS issue + kernel ACPI platform driver refusing to handle
> overlapping memory space. The issue here is that the ACPI platform
> driver is not created, however this should not prevent the tpm_crb
> driver from working as it registers directly the ACPI device. For now
> you can suppress the message by adding the device in forbidden_id_list
> in drivers/acpi/acpi_platform.c
>
>
> I'm already testing a fixed BIOS, not sure whether and when it will be
> available for your particular device.
Do you think we should go ahead with the patch I sent? Or should we
tell users they need a BIOS update?
Jason
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-02-17 16:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 11:15 Intel NUC and fTPM issue on 4.9.2 Davide Guerri
[not found] ` <CAH=yMtLydrTfn3_RkzZFpRL-sASUsHPdxX9m-HJUTyjv=D3ksg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-16 18:01 ` Jason Gunthorpe
[not found] ` <20170216180116.GA7145-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-16 18:10 ` Davide Guerri
[not found] ` <CAH=yMtJkmxxm6sn=1DmakXW+P=E7rsBd3iwqsSwaVBvxazE29w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-16 18:19 ` Jason Gunthorpe
[not found] ` <20170216181905.GA7257-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-16 18:26 ` Davide Guerri
[not found] ` <CAH=yMt+tWWDMban86H53Or+KngYLUw5hN0aB=+DaJ+MQOK4=4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-16 18:39 ` Davide Guerri
[not found] ` <CAH=yMtJ7qWq=YpRaUPh2zzOECjFGiwV3jfBc+4HuvW3wOYt_Vg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-16 18:40 ` Davide Guerri
[not found] ` <CAH=yMtLLrsyqLr9tOm+D2qvcCDNRO3P36hp8hCdJFVtDyJPWGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-16 19:03 ` Jason Gunthorpe
[not found] ` <20170216190329.GC7257-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-16 19:11 ` Davide Guerri
2017-02-16 20:00 ` Jarkko Sakkinen
2017-02-16 22:36 ` Winkler, Tomas
[not found] ` <5B8DA87D05A7694D9FA63FD143655C1B54395CD5-Jy8z56yoSI8MvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-02-17 16:43 ` Jason Gunthorpe [this message]
[not found] ` <20170217164332.GB30677-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-17 18:28 ` Sakkinen, Jarkko
[not found] ` <1487356105.6424.1.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-02-17 19:01 ` Jason Gunthorpe
[not found] ` <20170217190125.GA5984-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-17 21:14 ` Davide Guerri
[not found] ` <0FB78E3E-1E73-46EC-9ABD-FD05E1E8B0E2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-19 22:28 ` Winkler, Tomas
[not found] ` <5B8DA87D05A7694D9FA63FD143655C1B54398ADC-Jy8z56yoSI8MvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-02-20 10:36 ` Jarkko Sakkinen
2017-02-20 10:47 ` Jarkko Sakkinen
2017-04-18 14:49 ` [tpmdd-devel] " Winkler, Tomas
2017-04-18 14:49 ` Winkler, Tomas
2017-02-16 20:27 ` Jarkko Sakkinen
[not found] ` <20170216202754.zokzcn6l4pd7hvbm-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-02-16 21:01 ` Davide Guerri
2017-02-16 19:59 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170217164332.GB30677@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=davide.guerri-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jarkko.sakkinen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tomas.winkler-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.