Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1506984
| From | Mika Westerberg <mika.westerberg@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: pinctrl_cherryview: massive error messages (handle_bad_irq) |
| Date | 2016-10-24 10:20 +0200 |
| Message-ID | <svIEa-50a-5@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <su4IO-5Ai-41@gated-at.bofh.it> <su5Ye-6kK-25@gated-at.bofh.it> <suiC5-6ej-7@gated-at.bofh.it> <sunBL-ZF-7@gated-at.bofh.it> <svAwV-7U6-11@gated-at.bofh.it> |
| Organization | Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo |
On Mon, Oct 24, 2016 at 01:34:05AM +0200, Linus Walleij wrote: > On Thu, Oct 20, 2016 at 5:36 PM, Christian Steiner > <christian.steiner@outlook.de> wrote: > > >>> Currently I am using BIOS v1.22. Recently Acer released v1.23. I could > >>> test if the BIOS update solves the problem. > >> > >> Please try that first. > > > > Updating the BIOS to v1.23 solved the problem. Thank you very much for > > your advice! > > Not that I know how the Intel ecosystem works wrt this. > > Do you detect elder BIOS and display a warning? Are regular > users updating their BIOSes? Or was this some kind of development > Intel in-house BIOS? People do upgrade their BIOSes but for Linux users it has some extra pain if the OEM only provides you a .exe file which you need to run under Windows. It is possible to detect the BIOS version using DMI strings and issue a warning in the driver, if that's what you mean, but currently we don't do that.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
pinctrl_cherryview: massive error messages (handle_bad_irq) Christian Steiner <christian.steiner@outlook.de> - 2016-10-19 20:40 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-19 21:30 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Christian Steiner <christian.steiner@outlook.de> - 2016-10-19 22:50 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-20 12:20 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Linus Walleij <linus.walleij@linaro.org> - 2016-10-20 14:30 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Christian Steiner <christian.steiner@outlook.de> - 2016-10-20 17:40 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-20 20:10 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Linus Walleij <linus.walleij@linaro.org> - 2016-10-24 01:40 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-24 10:20 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Linus Walleij <linus.walleij@linaro.org> - 2016-10-25 11:30 +0200
Re: pinctrl_cherryview: massive error messages (handle_bad_irq) Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-10-25 12:40 +0200
csiph-web