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: Fri, 9 Feb 2007 16:28:56 -0500 [thread overview]
Message-ID: <20070209212856.GK7584@csclub.uwaterloo.ca> (raw)
In-Reply-To: <45CCD60D.5050001@8d.com>
On Fri, Feb 09, 2007 at 03:14:05PM -0500, Raphael Assenat wrote:
> This patch adds a PCI device ID (0x8152) for the IT8152F/G
> Advanced RISC-to-PCI Companion Chip.
>
> --
> Raphael Assenat
> 8D Technologies Inc.
> This patch adds a PCI device ID for the IT8152F/G
> Advanced RISC-to-PCI Companion Chip.
>
> Signed-off-by: Raphael Assenat <raph@8d.com>
>
> --- linux-2.6.20/include/linux/pci_ids.h 2007-02-04 13:44:54.000000000 -0500
> +++ linux-2.6.20-8d/include/linux/pci_ids.h 2007-02-09 15:00:38.000000000 -0500
> @@ -1626,6 +1626,7 @@
> #define PCI_VENDOR_ID_ROCKWELL 0x127A
>
> #define PCI_VENDOR_ID_ITE 0x1283
> +#define PCI_DEVICE_ID_ITE_8152 0x8152
> #define PCI_DEVICE_ID_ITE_8211 0x8211
> #define PCI_DEVICE_ID_ITE_8212 0x8212
> #define PCI_DEVICE_ID_ITE_8872 0x8872
Oh that one. Anyone ever have a reliable PCI bus with one of these?
The one system on a board I have worked with in the past had so many
problems with the PCI bus that we have to switch to another board
instead. Too bad since the ARM cpu was much faster and better and
handling network traffic (we switched to a Geode SC1200 based board).
At the time my theory was that the cpu would interrupt DMA transfers
when it wanted access to system memory, which would break the PCI
transfers. But that was just my theory.
--
Len Sorensen
next prev parent reply other threads:[~2007-02-09 21:28 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 [this message]
2007-02-13 14:45 ` Raphael Assenat
2007-02-13 15:16 ` Lennart Sorensen
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=20070209212856.GK7584@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®