[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1d47715-482c-f598-a958-499d9fde21e0@flygoat.com>
Date: Sat, 14 Nov 2020 17:47:47 +0800
From: Jiaxun Yang <jiaxun.yang@...goat.com>
To: Greg KH <gregkh@...uxfoundation.org>,
陈华才 <chenhc@...ote.com>
Cc: Roman Kiryanov <rkir@...gle.com>,
Huacai Chen <chenhuacai@...il.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
LKML <linux-kernel@...r.kernel.org>,
Lingfeng Yang <lfy@...gle.com>, Rob Herring <robh@...nel.org>,
anup.patel@....com, Alistair.Francis@....com, qemu-riscv@...gnu.org
Subject: Re: Re: [PATCH] drivers: rtc: retire RTC_DRV_GOLDFISH
在 2020/11/14 下午4:15, Greg KH 写道:
+ qemu-riscv list and QEMU device maintainers of goldfish_rtc
> On Sat, Nov 14, 2020 at 04:06:24PM +0800, 陈华才 wrote:
>> Hi, All,
>>
>> Goldfish RTC works well on MIPS, and QEMU RISC-V emulator use Goldfish
>> as well, so I think we should keep it in kernel.
> But does anyone actually use it for anything? Having something in qemu
> is nice, but not required if it doesn't provide something that is
> already there for other virtual devices, right?
Hi all,
Both QEMU MIPS loongson3-virt and riscv virt machine are using
goldfish_rtc as sole RTC
device, it have been hardcoded in QEMU for a long while and sudden drop
in kernel would
break these machines.
RTC is essential for virt machines to keep time synchronized with host.
Given that it is the simplest RTC implementation for now, it won't give
us much maintenance
overhead.
Thus I do think it shouldn't be retired as for now. If nobody comes in
I'd also willing to maintain
it.
Thanks
- Jiaxun
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists