mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: The (unnecessary) overhead of initramfs
Date: Wed, 29 Jul 2009 12:19:53 -0400	[thread overview]
Message-ID: <4A7076A9.2000608@redhat.com> (raw)
In-Reply-To: <20090729161655.GG20210-26w3C0LaAnFg9hUCZPvPmw@public.gmane.org>

On 07/29/2009 12:16 PM, Andy Whitcroft wrote:
> 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?
>

Why is this being discussed on this list when this has nothing to do 
with dracut?

Warren
--
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

  parent reply	other threads:[~2009-07-29 16:19 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
     [not found]   ` <20090729161655.GG20210-26w3C0LaAnFg9hUCZPvPmw@public.gmane.org>
2009-07-29 16:19     ` Warren Togami [this message]
     [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=4A7076A9.2000608@redhat.com \
    --to=wtogami-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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