public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ian Molton <imolton@ad-holdings.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.mx6q PCIE
Date: Tue, 06 Jan 2015 09:50:05 +0000	[thread overview]
Message-ID: <54ABAFCD.8090905@ad-holdings.co.uk> (raw)
In-Reply-To: <54AAF473.4080502@freescale.com>

This commit is already in my branch, I'm afraid.

On 05/01/15 20:30, York Sun wrote:
> On 01/05/2015 12:27 PM, Fabio Estevam wrote:
>> [Adding more folks on Cc]
>>
>> On Mon, Jan 5, 2015 at 3:35 PM, Ian Molton <imolton@ad-holdings.co.uk> wrote:
>>> Hi folks,
>>>
>>> I'm attempting to bring up a custom board with an i.mx6q on it.
>>>
>>> I've added support for PCIe and E1000 ethernet, and the PCI bus scans,
>>> showing my card (Intel i210 chip)
>>>
>>> The E1000 driver bombs out during init, however.
>>>
>>> I've tried inserting code to repeatedly read the BAR for 4k (and print a
>>> ".") after bus mastering is enabled, and this manages about 70 cycles
>>> before I no longer see serial output.
>>>
>>> if I reset the board, I may or may not get any "." printed, and
>>> sometimes I get completely other characters printed (perhaps serial is
>>> losing sync?).
>>>
>>> Anyone have any ideas ?
>> York Sun has also reported issues with this driver:
>> http://lists.denx.de/pipermail/u-boot/2014-October/190602.html
>>
> To clarify, the issue I had was solved by fixing the driver, commit
> 76f8cdb2036bf86ec7193ed13129797f0a32d13d.
>
> York
>

      reply	other threads:[~2015-01-06  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 17:35 [U-Boot] i.mx6q PCIE Ian Molton
2015-01-05 20:27 ` Fabio Estevam
2015-01-05 20:30   ` York Sun
2015-01-06  9:50     ` Ian Molton [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=54ABAFCD.8090905@ad-holdings.co.uk \
    --to=imolton@ad-holdings.co.uk \
    --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