All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Davide Viti <zinosat@tiscali.it>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: PCI device not working
Date: Fri, 21 Sep 2012 08:17:36 -0500	[thread overview]
Message-ID: <89227A80-31E1-4E18-9257-6B60126E5A62@kernel.crashing.org> (raw)
In-Reply-To: <CAKpAL0m2XqzuYsG4-yj3WfZN88PjQXMUxFtXpx-sjsWA_Q4EUQ@mail.gmail.com>


On Sep 21, 2012, at 6:33 AM, Davide Viti wrote:

> Hi,
> I'm working on a custom board based on P1020 with two (identical) PCI =
devices attached;
> The work is derived from another board with a single instance of that =
device.
> The system is based on u-boot-2009.11 and Linux 2.6.34.6
>=20
> The "pci" command on u-boot, shows me both the PCI controllers and
> the attached devices:
>=20
> Scanning PCI devices on bus 0
> BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
> _____________________________________________________________
> 00.00.00   0x1957     0x0100     Processor               0x20
>=20
> Scanning PCI devices on bus 1
> BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
> _____________________________________________________________
> 01.00.00   0x1b65     0xabba     Network controller      0x80
>=20
> Scanning PCI devices on bus 2
> BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
> _____________________________________________________________
> 02.00.00   0x1957     0x0100     Processor               0x20
>=20
> Scanning PCI devices on bus 3
> BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
> _____________________________________________________________
> 03.00.00   0x1b65     0xabba     Network controller      0x80
>=20
> The kernel detects only the first instance of the device.

What do you mean by first instance of the device ?

> Didn't get very far while looking at dts file and kernel logs, so I'm
> asking for some help on narrowing down the problem.
>=20
> I'm wondering if I can assume that the problem is restricted to
> kernel/dts and avoid concentrating on uboot.=20
> I can provide any log (didn't want to post tons of details on the =
first=20
> message)

Probably a dts issue.

What does lspci in linux say?

- k

  reply	other threads:[~2012-09-21 13:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 11:33 PCI device not working Davide Viti
2012-09-21 13:17 ` Kumar Gala [this message]
2012-09-21 14:06   ` Davide Viti
2012-09-24 13:25     ` Davide Viti
2012-09-24 13:27     ` Davide Viti
2012-09-24 20:59       ` Davide Viti
2012-09-26 13:44         ` Kumar Gala
2012-09-26 15:25           ` Davide Viti
2012-09-27  2:30             ` Kumar Gala
2012-09-27 11:43 R: " Davide Viti
2012-09-27 12:27 ` Kumar Gala
2012-09-27 13:14 R: " Davide Viti
2012-09-27 16:06 ` Kumar Gala
2012-10-04 12:24 R: " Davide Viti
2012-10-04 13:14 ` Kumar Gala
     [not found]   ` <CAKpAL0m3YnsbbGxL+ejfyE4zfGE5LD9Qxb7oobHVaAZGE1_Jnw@mail.gmail.com>
2012-10-05  8:54     ` Fwd: " Davide Viti
2012-10-05 12:47       ` Kumar Gala
2012-10-25  8:21         ` Davide
2012-10-31  8:52         ` Davide

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=89227A80-31E1-4E18-9257-6B60126E5A62@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=zinosat@tiscali.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.