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  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:   Fri, 18 Dec 2020 22:41:04 +0100
From:   Arnd Bergmann <>
To:     Sam Ravnborg <>
Cc:     David S Miller <>,
        sparclinux <>,
        Andreas Larsson <>,
        Alexey Dobriyan <>,
        Al Viro <>,
        Andrew Morton <>,
        Anshuman Khandual <>,
        Arvind Sankar <>,
        Christian Brauner <>,
        Denis Efremov <>,
        Dmitry Safonov <>,
        Geert Uytterhoeven <>,
        Greg Kroah-Hartman <>,
        Ira Weiny <>,
        Lorenzo Pieralisi <>,
        Mark Rutland <>,
        Mike Rapoport <>,
        Pekka Enberg <>,
        Peter Zijlstra <>,
        Stephen Rothwell <>,
        Thomas Gleixner <>,
        Will Deacon <>, Willy Tarreau <>,
        "" <>,
Subject: Re: [RFC PATCH 0/13] sparc32: sunset sun4m and sun4d

On Fri, Dec 18, 2020 at 7:43 PM Sam Ravnborg <> wrote:
> The sun4m and sun4d based SPARC machines was very popular in the
> 90'ties and was then replaced by the more powerful sparc64
> class of machines.
> Today there is only Gentoo that to my best knowledge supports
> sparc32 and people have moved on to more capable HW.
> Cobham Gaisler have variants of the LEON processer that
> runs sparc32 - and they are in production today.
> With this patchset I propose to sunset sun4m and sun4d and move
> focus to a more streamlined support for LEON.
> One downside is that qemu supports sun4m - and we may loose
> some testing possibilities when sun4m is dropped. qemu supports
> LEON to some degree - I have not yet tried it out.
> Andreas from Gaisler have indicated that they may be more active
> upstream on sparc32 - and this will only be easier with a kernel
> where the legacy stuff is dropped.
> I decided to divide up the patches to make it possible to review
> the set as some of the patches touches assembler and these parts
> could use some extra eyes if we move forward with this.
> For now it builds with the configurations I have tried.

Thank you for doing this, it looks like a very nice cleanup.

> Looking forward for feedback if sunsetting is a good idea or not.

I have no insight on whether there are any users left that would miss
it, but I'm fairly sure that there are lots of people that would rather
see it gone.

> Note: I dunno why git does not see floppy_64.h=>floppy.h as a rename??

It doesn't do that if the old name existed already.


Powered by blists - more mailing lists