linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matt@console-pimps.org (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] efi_rtc: probe function error out in case no efi runtime enabled
Date: Fri, 3 Oct 2014 13:11:19 +0100	[thread overview]
Message-ID: <20141003121119.GH14343@console-pimps.org> (raw)
In-Reply-To: <1411681130.25340.101.camel@deneb.redhat.com>

(Argh, this was sat in my outbox for over a week)

On Thu, 25 Sep, at 05:38:50PM, Mark Salter wrote:
> On Thu, 2014-09-25 at 22:18 +0100, Matt Fleming wrote:
> > On Mon, 22 Sep, at 12:33:29PM, Mark Salter wrote:
> > > 
> > > Is this still needed after commit da167ad7638759:
> > > 
> > >   rtc: ia64: allow other architectures to use EFI RTC
> > 
> > Umm... we should really look at disabling this for x86, since the EFI
> > time functions don't work on a bunch of machines I've got here.
> > 
> > And it looks like someone enabled this driver and triggered an oops on
> > their 32-bit EFI tablet,
> > 
> >   https://bugzilla.kernel.org/show_bug.cgi?id=84241#c21
> 
> Previously, it depended on IA64. If it's not worth the trouble for
> x86 then I'd say have it depend on !X86 also. Newer EFI-supporting
> architectures are unlikely to have the same legacy issues as x86
> so I don't think it'll end up being an ever growing list.
 
Yeah that's what I was thinking. For x86, it's the age old "Windows
doesn't use it, so it was never validated" issue.

I'll send an update.

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2014-10-03 12:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14  9:15 [PATCH 1/7] efi: move noefi early param code out of x86 arch code Dave Young
2014-08-14  9:15 ` [PATCH 2/7] Add a generic cmdline parse function parse_option_str Dave Young
2014-08-14  9:15 ` [PATCH 3/7] efi: add kernel param efi=noruntime Dave Young
2014-08-14  9:15 ` [PATCH 4/7] arm64/efi: uefi_init error handling fix Dave Young
2014-08-14 13:55   ` Mark Salter
2014-08-15 15:05   ` Will Deacon
2014-08-14  9:15 ` [PATCH 5/7] arm64/efi: do not enter virtual mode in case booting with efi=noruntime or noefi Dave Young
2014-08-15 15:09   ` Will Deacon
2014-08-18  1:24     ` Dave Young
2014-08-18  1:30     ` [PATCH 5/7 update] " Dave Young
2014-08-22 15:10       ` Will Deacon
2014-08-22 15:47         ` Matt Fleming
2014-08-22 16:25           ` Will Deacon
2014-08-14  9:15 ` [PATCH 6/7] x86/efi: clear EFI_RUNTIME_SERVICES bit in case failures while entering virtual mode Dave Young
2014-08-14  9:19 ` [PATCH 7/7] efi_rtc: probe function error out in case no efi runtime enabled Dave Young
2014-09-22 16:33   ` Mark Salter
2014-09-23  7:24     ` Dave Young
2014-09-28 16:41       ` Matt Fleming
2014-09-25 21:18     ` Matt Fleming
2014-09-25 21:38       ` Mark Salter
2014-10-03 12:11         ` Matt Fleming [this message]
2014-08-14  9:26 ` [PATCH 1/7] efi: move noefi early param code out of x86 arch code Dave Young
2014-08-25 10:24   ` Matt Fleming

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=20141003121119.GH14343@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).