mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Raphael Assenat <raph@8d.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add PCI device ID for IT8152 RISC-to-PCI chip
Date: Tue, 13 Feb 2007 10:16:33 -0500	[thread overview]
Message-ID: <20070213151633.GL7584@csclub.uwaterloo.ca> (raw)
In-Reply-To: <45D1CF22.6010706@8d.com>

On Tue, Feb 13, 2007 at 09:45:54AM -0500, Raphael Assenat wrote:
> Really? I have no idea if it's possible to get a reliable PCI bus or
> not with this chip. Right now, we only use it for it's built-in OHCI 
> USB host controller and UART. You're making me hope I never have to 
> use it for interfacing a PCI card!

Well on the system on a board we were trying, using the development
baseboard from the same supplier, by simply doing a ping flood through
the onboard rtl8139 I managed to get corrupted ethernet packets fairly
frequently.  The WAN cards (T1/E1) we were trying to make work with it
were much more upset by it.  It could be bad enough corruption to cause
the chip on the card and the driver to get out of sync and just have no
idea what to do anymore.  Given our mainboard works perfectly fine using
a Geode SC1200 instead of the PXA255 board, I can only figure the PCI
bus wasn't implemented correctly on that chip, unless PCI on arm is done
wrong in linux (I sure hope not).  There doesn't seem to be very many
arm systems with PCI, so it's hard to tell.  Now other than PCI the
system was wonderful.  Fast, reliable, ran great even at high
temperatures, etc.  Just couldn't get the stupid PCI bus to work.

--
Len Sorensen

  reply	other threads:[~2007-02-13 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 20:14 Raphael Assenat
2007-02-09 21:28 ` Lennart Sorensen
2007-02-13 14:45   ` Raphael Assenat
2007-02-13 15:16     ` Lennart Sorensen [this message]
2007-02-13 15:30       ` Russell King
2007-02-13 15:47         ` Lennart Sorensen
2007-02-13 16:20           ` Russell King

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=20070213151633.GL7584@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raph@8d.com \
    /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

all inboxes | Powered by JetHome®