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] [day] [month] [year] [list]
Message-ID: <CAAhV-H5uak2Txvj3-yZz5HJxiE8tUKyGEibVa8LkqJOYn2+ACQ@mail.gmail.com>
Date:   Sat, 14 Nov 2020 16:59:37 +0800
From:   Huacai Chen <chenhc@...ote.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Roman Kiryanov <rkir@...gle.com>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Lingfeng Yang <lfy@...gle.com>, Rob Herring <robh@...nel.org>
Subject: Re: [PATCH] drivers: rtc: retire RTC_DRV_GOLDFISH

Hi, Greg,

On Sat, Nov 14, 2020 at 4:16 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> 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.
>
> And more importantly, if you rely on this, are you willing to maintain
> it?
I think it will break the booting of MIPS/RISCV QEMU virtual machines,
because RTC is an necessary device.

For the maintenance, I don't know whether Goldfish RTC depends on the
code under drivers/platform/goldfish. If not, I think I can maintain
it (I think other parts of Goldfish will be removed, I'm able to
maintain RTC but I'm not able to maintain the whole).

Huacai

>
> thanks,
>
> gre gk-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ