From: Andy Whitcroft <apw-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Scott James Remnant <scott-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: ubuntu-boot-oU9gvf+ajcQ97yFScArB1dHuzzzSOjJt@public.gmane.org,
kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
maximilian attems <max-U9r9yeDMy7A@public.gmane.org>,
debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org
Subject: Re: The (unnecessary) overhead of initramfs
Date: Wed, 29 Jul 2009 17:16:55 +0100 [thread overview]
Message-ID: <20090729161655.GG20210@shadowen.org> (raw)
In-Reply-To: <1248871245.23840.46.camel@quest>
On Wed, Jul 29, 2009 at 01:40:45PM +0100, Scott James Remnant wrote:
> The initramfs scripts spend a lot of wasted time and effort doing things
> that really don't need to be done:
>
> In the "framebuffer" init-top script:
>
> modprobe -q intel_agp
> modprobe -q i915
> modprobe -q ${FB} ${OPTS}
These may be the source of an issue we are seeing with radeon drivers.
That when using a pure AMD system you get the i915 driver loaded for
no apparent reason. I presume these should be -b even if they were
not redundant?
-apw
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-29 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 12:40 The (unnecessary) overhead of initramfs Scott James Remnant
2009-07-29 16:16 ` Andy Whitcroft [this message]
[not found] ` <20090729161655.GG20210-26w3C0LaAnFg9hUCZPvPmw@public.gmane.org>
2009-07-29 16:19 ` Warren Togami
[not found] ` <4A7076A9.2000608-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-29 16:25 ` maximilian attems
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=20090729161655.GG20210@shadowen.org \
--to=apw-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org \
--cc=max-U9r9yeDMy7A@public.gmane.org \
--cc=scott-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=ubuntu-boot-oU9gvf+ajcQ97yFScArB1dHuzzzSOjJt@public.gmane.org \
/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