linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: Andrew Armitage <andrew@varisys.co.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Yosemite/440EP 'issues' as a PCI target
Date: Fri, 10 Feb 2006 09:26:29 -0800	[thread overview]
Message-ID: <43ECCCC5.3000405@ovro.caltech.edu> (raw)
In-Reply-To: <43ECCB4D.9080602@varisys.co.uk>

> We've used the 21555 on a couple of our designs (mated to a 7457/107 
> pair) and have never had too many problems with them.  The messaging 
> unit has been very helpful.
> 
> Just my $0.02,

Hey Andrew,
Thanks!
Dave

  reply	other threads:[~2006-02-10 17:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  9:35 Yosemite/440EP why are readl()/ioread32() setup to readlittle-endian? Jenkins, Clive
2006-02-02  9:46 ` Eugene Surovegin
2006-02-02 14:37   ` Matt Porter
2006-02-02 17:45     ` Eugene Surovegin
2006-02-02 18:16       ` Matt Porter
2006-02-05  4:41         ` Yosemite/440EP PLB4 vs PLB3 DMA to PCI issue David Hawkins
2006-02-05 10:39           ` Wolfgang Denk
2006-02-05 23:47             ` David Hawkins
2006-02-06 18:31               ` Stefan Roese
2006-02-06 19:09                 ` David Hawkins
2006-02-08 15:38                   ` Stefan Roese
2006-02-08 18:43                     ` David Hawkins
2006-02-09  0:34                       ` Wolfgang Denk
2006-02-09 13:25                         ` Mark Chambers
2006-02-09 23:58                         ` Yosemite/440EP 'issues' as a PCI target David Hawkins
2006-02-10  7:47                           ` Stefan Roese
2006-02-10 17:05                             ` David Hawkins
2006-02-10 17:20                               ` Andrew Armitage
2006-02-10 17:26                                 ` David Hawkins [this message]
2006-02-10 17:31                               ` Wolfgang Denk
2006-02-10 17:38                                 ` David Hawkins
2006-02-10 17:58                                   ` David Hawkins
2006-02-11  6:03                                 ` David Hawkins
2006-02-11  8:21                                   ` Stefan Roese
2006-02-11 18:15                                     ` David Hawkins
2006-02-11 13:03                                   ` Wolfgang Denk
2006-02-10 17:59                               ` Stefan Roese
2006-02-10 18:11                                 ` David Hawkins
2006-02-11  8:06                                   ` Stefan Roese
2006-02-11 18:06                                     ` David Hawkins
2006-02-11 19:00                                     ` David Hawkins
     [not found]                               ` <001701c62e6c$09c48ea0$6401a8c0@CHUCK2>
2006-02-10 18:19                                 ` David Hawkins
2006-02-11  6:06                                 ` David Hawkins
     [not found]                               ` <43ECCCA2.1070007@sandburst.com>
     [not found]                                 ` <43ECCE7A.4090507@ovro.caltech.edu>
     [not found]                                   ` <43ECD19E.8010604@sandburst.com>
2006-02-10 19:13                                     ` David Hawkins

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=43ECCCC5.3000405@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=andrew@varisys.co.uk \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).