From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] pci command does not show Wifi card
Date: Mon, 11 Aug 2014 23:39:46 +0200 [thread overview]
Message-ID: <201408112339.46465.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5C0g3CXZ4wYuDZvhfFjQh+oA-Oqoi4C38MwOinvVBaz+g@mail.gmail.com>
On Monday, August 11, 2014 at 11:16:28 PM, Fabio Estevam wrote:
> On Mon, Aug 11, 2014 at 5:55 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi,
> >
> > On a mx6qsabresd I can see U-boot to detect my Wifi card on boot:
> >
> > U-Boot 2014.07-16451-g7496820-dirty (Aug 11 2014 - 17:43:44)
> >
> > CPU: Freescale i.MX6Q rev1.2 at 792 MHz
> > Reset cause: POR
> > Board: MX6-SabreSD
> > I2C: ready
> > DRAM: 1 GiB
> > MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
> >
> > 00:01.0 - 16c3:abcd - Bridge device
> >
> > 01:00.0 - 8086:08b1 - Network controller
> >
> > However when the 'pci' command is used I get:
> >
> > => pci
> > Scanning PCI devices on bus 0
> > BusDevFun VendorId DeviceId Device Class Sub-Class
> > _____________________________________________________________
> > 00.00.00 0x16c3 0xabcd Bridge device 0x04
> > 00.01.00 0x16c3 0xabcd Bridge device 0x04
> >
> > Bridge device is listed twice and the network controller does not show
> > up.
> >
> > Is this is a bug within common/cmd_pci.c ?
>
> Looks like I need to pass the bus number to the pci command to see the
> wifi card:
>
> => pci 1
> Scanning PCI devices on bus 1
> BusDevFun VendorId DeviceId Device Class Sub-Class
> _____________________________________________________________
> 01.00.00 0x8086 0x08b1 Network controller 0x80
Right, RTFM ;-)
Best regards,
Marek Vasut
prev parent reply other threads:[~2014-08-11 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 20:55 [U-Boot] pci command does not show Wifi card Fabio Estevam
2014-08-11 21:16 ` Fabio Estevam
2014-08-11 21:39 ` Marek Vasut [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=201408112339.46465.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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