linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Reeve Yang" <yang.reeve@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Q about i2c controller on mpc8245
Date: Fri, 23 Jun 2006 01:06:00 +0000	[thread overview]
Message-ID: <198592450606221806yfe1e489wf29ebefd3bc264b@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

Hello,

I'm new to this list and wish to get help from it since I'm currently
developing a switch box based on mpc8245, the kernel I'm using is 2.6.14.

Now I'm trying to bring up the I2C controller then I2C devices. Is fsl-i2c
the driver for I2C controller of MPC8245? I enabled that driver and it was
installed, but there is no any device found. Why is it like that? Following
are the dump from sysfs.

/ # systool -b platform -d
Bus = "platform"

  Device = "serial8250"
  Device = "serial8250.0"
  Device = "serial8250.1"

/ # systool -b platform -D
Bus = "platform"

  Driver = "fsl-i2c"

  Driver = "serial8250"
    Devices using "serial8250" are:
      Device = "serial8250"

      Device = "serial8250.0"

      Device = "serial8250.1"

In the booting sequence, I got following error message:

PCI: Probing PCI hardware
PCI: Cannot allocate resource region 1 of device 0000:00:00.0
fsl-i2c.1: failed to claim resource 0
unable to register device 0
fsl-dma.0: failed to claim resource 0
unable to register device 1
fsl-dma.1: failed to claim resource 0
unable to register device 2

Does this error make device undetected? What might be the reason for above
errors? I'd appreciate if you could shed some lights.

Regards,

- Reeve

[-- Attachment #2: Type: text/html, Size: 1630 bytes --]

                 reply	other threads:[~2006-06-23  1:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=198592450606221806yfe1e489wf29ebefd3bc264b@mail.gmail.com \
    --to=yang.reeve@gmail.com \
    --cc=linuxppc-dev@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).