xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andrew Jones <drjones@redhat.com>,
	xen-devel@lists.xensource.com,
	stefano stabellini <stefano.stabellini@eu.citrix.com>,
	jeremy@goop.org, virtualization@lists.linux-foundation.org,
	konrad@darnok.org
Subject: Re: [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin
Date: Thu, 12 Jan 2012 16:42:06 +0100	[thread overview]
Message-ID: <20120112154206.GA9722@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20120112143745.GE7685@phenom.dumpdata.com>

On Thu, Jan 12, 2012 at 09:37:45AM -0500, Konrad Rzeszutek Wilk wrote:
> Or is it possible to make the modules (fb) try to load xenbus frontend
> automatically? Preferrably one would do this:

Which modules?

> modprobe xen_fbfront
> which would then automatically load xenbus_module, xen_kbdfront

I think you are missing something.

| video/xen-fbfront.c:      return xenbus_register_frontend(&xenfb_driver);
| xen/xenbus/xenbus_probe_frontend.c:EXPORT_SYMBOL_GPL(xenbus_register_frontend);

xen-fbfront already pulls in the module, at least in Linus' tree.

> Better yet if udev/kudzu figured out this automtically and loaded
> the modules.

No workarounds for kernel problems if not absolutely necessary.

Bastian

-- 
Military secrets are the most fleeting of all.
		-- Spock, "The Enterprise Incident", stardate 5027.4

  reply	other threads:[~2012-01-12 15:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 16:39 [PATCH] xen: remove CONFIG_XEN_DOM0 compile option Andrew Jones
2012-01-06 16:59 ` Stefano Stabellini
2012-01-09 10:37   ` [Xen-devel] " Andrew Jones
2012-01-09 11:39     ` Stefano Stabellini
2012-01-09 14:56       ` Konrad Rzeszutek Wilk
2012-01-09 16:12         ` Stefano Stabellini
2012-01-09 17:04           ` Konrad Rzeszutek Wilk
2012-01-09 17:38             ` Andrew Jones
2012-01-09 18:44               ` Stefano Stabellini
2012-01-10  0:57                 ` Jeremy Fitzhardinge
2012-01-11 15:37                   ` [Xen-devel] " Andrew Jones
2012-01-11 16:19                     ` Konrad Rzeszutek Wilk
2012-01-11 16:36                       ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Andrew Jones
2012-01-11 16:36                         ` [PATCH 2/4 v2] xen kconfig: relax INPUT_XEN_KBDDEV_FRONTEND deps Andrew Jones
2012-01-11 17:30                           ` Konrad Rzeszutek Wilk
2012-01-12 10:59                             ` Andrew Jones
2012-01-11 16:36                         ` [PATCH 3/4 v2] xen kconfig: add dom0 support help text Andrew Jones
2012-01-11 16:36                         ` [PATCH 4/4] xen kconfig: describe xen tmem in the config menu Andrew Jones
2012-01-11 17:35                           ` Konrad Rzeszutek Wilk
2012-01-12 10:54                             ` Andrew Jones
2012-01-11 17:28                         ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Konrad Rzeszutek Wilk
2012-01-12 10:49                           ` [Xen-devel] " Andrew Jones
2012-01-12 14:37                             ` Konrad Rzeszutek Wilk
2012-01-12 15:42                               ` Bastian Blank [this message]
2012-01-12 17:46                                 ` Andrew Jones
2012-01-11 17:27                       ` [PATCH] xen: remove CONFIG_XEN_DOM0 compile option Konrad Rzeszutek Wilk
2012-01-12 10:53                         ` [Xen-devel] " Andrew Jones
2012-01-09 18:12             ` Stefano Stabellini
2012-01-09 17:26           ` Andrew Jones
2012-01-06 17:16 ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2012-01-06  9:43 [PATCH 0/4] xen kconfig tweaks Andrew Jones
2012-01-06  9:43 ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Andrew Jones
2012-01-06  8:57 [PATCH 0/4] xen kconfig tweaks Andrew Jones
2012-01-06  8:57 ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Andrew Jones

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=20120112154206.GA9722@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=drjones@redhat.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@darnok.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=virtualization@lists.linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).