From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: mod+linuxppc-dev@mclx.com, mporter@mvista.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC+southbridge designs
Date: Fri, 12 Oct 01 09:00:07 PDT [thread overview]
Message-ID: <0110121600.AA00355@ivan.Harhan.ORG> (raw)
Matt Porter <mporter@mvista.com> wrote:
> A lot of them. Hardware developers for high-end PPC embedded designs
> like them as a way to get UARTs, PIC, and IDE in one dirt-cheap package.
> Software developers hate them because they are evil.
Yes! Nail right on the head!
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-12 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 16:00 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 15:30 PPC+southbridge designs Michael Sokolov
2001-10-12 13:37 mod+linuxppc-dev
2001-10-12 12:09 ` Matt Porter
2001-10-12 16:14 ` Adrian Cox
2001-10-12 19:40 ` Timothy A. Seufert
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=0110121600.AA00355@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mod+linuxppc-dev@mclx.com \
--cc=mporter@mvista.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;
as well as URLs for NNTP newsgroup(s).