linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: linuxppc-embedded@ozlabs.org
Cc: Sachin Rane <SRane@alphion.com>
Subject: Re: Board Bootup and message log
Date: Mon, 18 Sep 2006 09:18:56 +0200	[thread overview]
Message-ID: <200609180918.56987.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <8584FDC94AFF7640B17B8A89B23B19B34F6568@sbsserver.AlphionCorp.local>

On Saturday 16 September 2006 10:19, Sachin Rane wrote:
> Hi,
>  
> I want to access 'EEPROM' I2C device present on AMCC PPC440GX Evaluation 
bard.
> I have loaded following drivers:
> 1. i2c-core.ko
> 2. i2c-dev.ko
> 3. eeprom.ko
> 4. i2c-ibm_iic.ko
> The entry in the 'sysfs' got created for drivers and devices.

> As per the documentation (/usr/src/linux/Documentation/i2c/dev-interface),
> I2C adapter files gets created under "/dev/i2c-X"are with with major device 
number 89.
>  
> But in my case, the device file is not getting created under '/dev/'.
If you do not have some magic daemons running on your board that will do the 
work you have to create the /dev entries by hand.

Please do not post the same message multiple times. Also attachments are often 
not very welcome on mailing lists.

Matthias

      parent reply	other threads:[~2006-09-18  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8584FDC94AFF7640B17B8A89B23B19B34F6564@sbsserver.AlphionCorp.local>
2006-09-16  8:19 ` Board Bootup and message log Sachin Rane
     [not found]   ` <8584FDC94AFF7640B17B8A89B23B19B34F6569@sbsserver.AlphionCorp.local>
2006-09-16  8:29     ` I2C adapter device file problem Sachin Rane
2006-09-18  5:19       ` Sachin Rane
2006-09-18  7:18   ` Matthias Fuchs [this message]

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=200609180918.56987.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.com \
    --cc=SRane@alphion.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).