public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel I. Applebaum" <danapple@danapple.com>
To: linux-kernel@vger.kernel.org
Subject: built-in USB /proc bug
Date: Tue, 20 Nov 2001 11:50:34 -0600	[thread overview]
Message-ID: <200111201750.fAKHoYa03354@danapple.com> (raw)


I tried building a 2.4.13 kernel with USB support as built-in, instead
of modules.  The system worked, and USB devices worked, but there were
no entries in /proc/bus/usb Yes, I had enabled both /proc filesystem
and USB /proc filesystem support.  When the same kernel was built but
with USB support as modules, the /proc/bus/usb entries appear.

Although no expert in these matters, I suspect that when the USB
subsystem is built-in, it is initialized before /proc is mounted, and
the USB /proc filesystem support either turns itself off or puts the
"files" elsewhere.

A viable solution might be to have make menuconfig warn against this
combination.

Dan.


             reply	other threads:[~2001-11-20 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 17:50 Daniel I. Applebaum [this message]
2001-11-20 18:37 ` built-in USB /proc bug Johannes Erdfelt

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=200111201750.fAKHoYa03354@danapple.com \
    --to=danapple@danapple.com \
    --cc=linux-kernel@vger.kernel.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