From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Question: why pvops seldom build modules drivers
Date: Thu, 08 Jul 2010 11:37:35 -0700 [thread overview]
Message-ID: <4C361AEF.30009@goop.org> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E089DD93825@shsmsx502.ccr.corp.intel.com>
On 07/08/2010 04:10 AM, Liu, Jinsong wrote:
> Recently I install pvops/xen at a new platform,
> However, I meet troubles, it need manually enable&install some driver like Lsi scsi controller (to find root device which is a SAS disk connect to Lsi controller) & Intel 82576 nic to access network.
> I check pvops .config, it seldom build module driver.
> Just curious why pvops does so? it make trouble when install pvops at various platform ..., while at native linux it config most device driver as module.
>
I usually build modular kernels without problem. The tricky part is
making sure all the right drivers end up in your initrd. What distro
are you using?
J
next prev parent reply other threads:[~2010-07-08 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 11:10 Question: why pvops seldom build modules drivers Liu, Jinsong
2010-07-08 18:37 ` Jeremy Fitzhardinge [this message]
2010-07-09 5:04 ` Pasi Kärkkäinen
2010-07-12 6:52 ` Liu, Jinsong
2010-07-12 9:41 ` Ian Campbell
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=4C361AEF.30009@goop.org \
--to=jeremy@goop.org \
--cc=jinsong.liu@intel.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.