lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Sep 2015 11:56:43 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	"Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>,
	Kefeng Wang <wangkefeng.wang@...wei.com>,
	Hanjun Guo <guohanjun@...wei.com>,
	Catalin Marinas <catalin.marinas@....com>,
	Tianhong Ding <dingtianhong@...wei.com>,
	Will Deacon <will.deacon@....com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Xinwei Hu <huxinwei@...wei.com>, Zefan Li <lizefan@...wei.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 2/2] arm64: to allow EFI_RTC can be selected on ARM64

On Monday 28 September 2015 17:44:40 Leizhen wrote:
> >> No, on non-EFI platforms, they can still use RTC as before. As I mentioned above,
> >> RTC_LIB only controls whether to display some configs when run "make menuconfig".
> >> On ARM64, (in this patch) I only allowed EFI_RTC can be showed when RTC_LIB was
> >> not selected.
> >>
> > 
> > but that is the wrong driver that uses the legacy API, we cannot have that
> > on ARM because it conflicts with the normal RTC_CLASS drivers.
> 
> Yes, RTC_CLASS will automatically select RTC_LIB, and will not display EFI_RTC, because
> RTC_LIB=y now.
> 
> We can select EFI_RTC only when RTC_CLASS is not selected(meanwhile RTC_LIB=n)

I understood that, and my initial point was that we cannot allow
such a situation, all drivers that we might use must be able to coexist
in one kernel.

If you have any applications that are ported from Itanium and that rely on
specific behavior of the ia64 rtc driver, we should either enable those in the
normal rtc-efi driver, or you need to change your application to use the
portable RTC interfaces.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ