Hi,
On 22 Mar 2018, at 13:35, Adam Borowski <kilob...@angband.pl> wrote:
> On Thu, Mar 22, 2018 at 12:09:45PM +0100, René Rebe wrote:
>> Should this currently just work without any arch change on e.g.
>> ppc64, sparc64 et al.? I could do a test build and boot if that is
>> of any value, ...
>
> Initrd: no reason it wouldn't work, although for anything related to the
> boot process testing is a very good idea. If you test, you'd really want to
> apply that printk patch I posted, it's too easy to accidentally get a silent
> fallback to gzip or uncompressed. I wonder, perhaps such a printk could be
> permanently added, at a low message priority?
zstd initrd worked on sparc64/sun4u - Ultra 30:
https://www.youtube.com/watch?v=10q2OxHAzQ4
Any chance we could get this initrd zstd support upstream?
> Kernel itself: needs per-arch porting, but it's not advertised in kconfig
> outside x86 so that's not a problem.
>
> If you are knowledgeful about bootloaders on ppc64, sparc64, etc, such
> information would be great.
--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
http://exactcode.com | http://exactscan.com | http://ocrkit.com |
http://t2-project.org | http://rene.rebe.de
