From: Diederik de Haas <didi.debian@cknow.org>
To: Dragan Simic <dsimic@manjaro.org>, Steven Price <steven.price@arm.com>
Cc: dri-devel@lists.freedesktop.org, boris.brezillon@collabora.com,
robh@kernel.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
daniel@ffwll.ch, linux-kernel@vger.kernel.org,
Furkan Kardame <f.kardame@manjaro.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/panfrost: Mark simple_ondemand governor as softdep
Date: Thu, 25 Jul 2024 12:23:13 +0200 [thread overview]
Message-ID: <3863847.7OiSWjA07a@bagend> (raw)
In-Reply-To: <ae62139f-3655-44d0-aeb7-15c6b67eb97c@arm.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Thursday, 25 July 2024 11:20:22 CEST Steven Price wrote:
> [1] Although from my understanding it's firmware which is the real cause
> of bloat in initramfs size. I guess I need to start paying attention to
> this for panthor which adds GPU firmware - although currently tiny in
> comparison to others.
Can confirm that's the case.
When using (f.e.?) plymouth, the gpu drivers and corresponding firmware
gets added to initramfs. If you then have much more and much larger firmware
files (nvidia f.e. added 2 fw files of 23 and 38 MB respectively ...) then you
get a corresponding much larger initramfs.
If you add a (fixed) bug in initramfs-tools where symlinks to directories
weren't preserved, but full copies were made, you could end up with a single
initramfs of 240MB ...
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-25 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 20:17 [PATCH] drm/panfrost: Mark simple_ondemand governor as softdep Dragan Simic
2024-07-03 12:42 ` Dragan Simic
2024-07-03 13:20 ` Steven Price
2024-07-03 14:52 ` Dragan Simic
2024-07-25 8:24 ` Dragan Simic
2024-07-25 9:20 ` Steven Price
2024-07-25 10:23 ` Diederik de Haas [this message]
2024-07-25 11:40 ` Dragan Simic
2024-07-03 13:20 ` Boris Brezillon
2024-07-03 13:29 ` Steven Price
2024-07-03 14:49 ` Dragan Simic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3863847.7OiSWjA07a@bagend \
--to=didi.debian@cknow.org \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=f.kardame@manjaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox