mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karel Kulhavy <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: /proc/bus/i2c is missing
Date: Fri, 12 Nov 2004 14:12:02 +0000	[thread overview]
Message-ID: <20041112141202.GA19781@beton.cybernet.src> (raw)

Hello

linux 2.6.8.1

I insmoded i2c-parport and pcf8591 modules and i2c-1 appeared in my /dev
(previously, only i2c-0 was there):

	clock@oberon:~$ ls /dev/i2* 
	/dev/i2c-0  /dev/i2c-1
	
	/dev/i2c:
	0  1

/usr/src/linux/Documentation/i2c says "You can
examine /proc/bus/i2c to see what number corresponds to which adapter."
I don't have any /proc/i2c:

	clock@oberon:~$ ls /proc/i2c
	ls: /proc/i2c: No such file or directory

However, I have /proc:
	clock@oberon:~$ ls /proc
	             devices      mtrr
	             diskstats    net
	             dma          partitions
	             driver       pci
	             execdomains  scsi
	             filesystems  self
	             fs           slabinfo
	             ide          stat
	             interrupts   swaps
	  [...]      iomem        sys
	             ioports      sysrq-trigger
	             irq          sysvipc
	             kallsyms     tty
	             kcore        uptime
	             kmsg         version
	             loadavg      vmstat
	             locks
	  buddyinfo  mdstat
	  bus        meminfo
	  cmdline    misc
	  config.gz  modules
	  cpuinfo    mounts

How can I make /proc/i2c appear?

Cl<

             reply	other threads:[~2004-11-12 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 14:12 Karel Kulhavy [this message]
2004-11-12 19:14 ` Greg KH
2004-11-12 14:22 Piszcz, Justin Michael
2004-11-12 14:37 ` Karel Kulhavy
2004-11-12 14:41 Piszcz, Justin Michael
2004-11-12 14:54 ` Karel Kulhavy

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=20041112141202.GA19781@beton.cybernet.src \
    --to=clock@twibright.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

Powered by JetHome