linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: iida <iida@ztec.com.br>
To: linuxppc <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: how to use the i2c in mpc5200
Date: Thu, 27 May 2004 16:32:36 -0300	[thread overview]
Message-ID: <40B64254.5040004@ztec.com.br> (raw)
In-Reply-To: <Pine.LNX.4.60.0405270900480.32475@xmission.xmission.com>


i2s is anoter i/o , but i read the source of i2c and
i think that the minor number is correct
Thanks for help

linuxppc-embedded@2nerds.com wrote:

> On Thu, 27 May 2004, iida wrote:
>
>> i created the i2c with
>> mknod /dev/i2c c 89 1
>
>
> This is just a hunch, but is that the proper minor device number?  In my
> copy of the kernel sources, in the file arch/ppc/5xxx_io/i2s.c, I see
> this
> definition:
>
> #define I2S_MINOR 242
>
> ...which makes me wonder if "mknod /dev/i2c c 89 242" would work any
> better.  Does your source tree include that same definition?  Is that
> "minor number" the one you need to use with mknod?
>
> I'm a novice at this Linux-on-embedded-PPC stuff, so please forgive me if
> this is useless advice--and please let me know how you resolved the
> problem when you find the "right" answer. :-)
>
> Chris


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-05-27 19:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 13:47 how to use the i2c in mpc5200 iida
     [not found] ` <Pine.LNX.4.60.0405270900480.32475@xmission.xmission.com>
2004-05-27 19:32   ` iida [this message]
2004-05-27 23:56 ` Wolfgang Denk
2004-05-28 11:48   ` iida
     [not found] <20040528203540.5383EC109F@atlas.denx.de>
2004-05-31 17:19 ` iida
  -- strict thread matches above, loose matches on Subject: below --
2004-05-31 18:49 Wolfgang Denk

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=40B64254.5040004@ztec.com.br \
    --to=iida@ztec.com.br \
    --cc=linuxppc-embedded@lists.linuxppc.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).