linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Hendricks" <ra6353@email.sps.mot.com>
To: "Clayton, Mark" <mclayton@hjinc.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'" 
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: OT - Motorola 8260 driver's pdf unreadable
Date: Thu, 16 Dec 1999 13:08:24 -0600	[thread overview]
Message-ID: <385938A8.45D0E176@email.sps.mot.com> (raw)
In-Reply-To: BF2D59E60824D311A5F800A0C9AC13F32DC348@xover.hjinc.com


MPC860 and MPC8260 support is handled by the Netcomm group.  They're
not as warm and cuddly as the MPC821/MPC823 group, and prefer their
customers to contact them through the local sales office.

"Clayton, Mark" wrote:
> 
> I downloaded the example drivers tarball from Mot's 8260
> web pages, but the pdf files aren't readable.  The table
> of contents is there, but the text doesn't show up.  I
> couldn't find any kind of tech support email address to
> report this.  Anyone know how I can get in touch with
> someone to see if I can get new pdf files?
> 
> BTW, the topics discussed here have been very informative.
> 
> Thanks,
> Mark
> --
> ==========================================================
> Mark Clayton                  voice:  781-329-3200 x1155
> Harris & Jeffries             fax:    781-329-4148
> 888 Washington Street         e-mail: mclayton@hjinc.com
> Dedham MA 02026 USA           web:    http://www.hjinc.com
> ==========================================================

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-12-16 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-16 14:47 OT - Motorola 8260 driver's pdf unreadable Clayton, Mark
1999-12-16 19:08 ` Richard Hendricks [this message]
1999-12-16 20:17   ` Alan Mimms

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=385938A8.45D0E176@email.sps.mot.com \
    --to=ra6353@email.sps.mot.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mclayton@hjinc.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).