All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202735] New: CONFIG_DRM_TTM does not have name in Kconfig, so it is invisble for menuconfig
Date: Sat, 02 Mar 2019 23:15:27 +0000	[thread overview]
Message-ID: <bug-202735-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=202735

            Bug ID: 202735
           Summary: CONFIG_DRM_TTM does not have name in Kconfig, so it is
                    invisble for menuconfig
           Product: Drivers
           Version: 2.5
    Kernel Version: latest
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: kazakevichilya@gmail.com
        Regression: No

CONFIG_DRM_TTM is used by many DRM drivers. It is now does not have name in
Kconfig, so it only could be autoselected by other drivers. User can't select
it with "menu menuconfig"

Virtualbox driver (vboxvideo) uses it, so when I compile new kernel I can't
enable this option unless I enable any other driver that I do not need.

I suggest to give it a  name, for example "GPU TTM".

I can create patch for that:)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-03-02 23:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 23:15 bugzilla-daemon [this message]
2019-03-04  9:36 ` [Bug 202735] CONFIG_DRM_TTM does not have name in Kconfig, so it is invisble for menuconfig bugzilla-daemon
2019-03-04  9:53 ` bugzilla-daemon
2019-03-04 12:57 ` bugzilla-daemon
2019-03-04 13:42 ` bugzilla-daemon

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=bug-202735-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 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.