linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Cc: rvinson@mvista.com, mgreer@mvista.com
Subject: trying to boot 2.6.6 on new version of Motorola mcpn765
Date: Fri, 11 Jun 2004 11:50:33 -0400	[thread overview]
Message-ID: <40C9D4C9.4030907@nortelnetworks.com> (raw)


We've got some mcpn765 cards that have different hardware and are not being
recognized by the current kernel code.

The differences are that the hawk chip is reporting revision 3, and the VIA
bridge is the VT82C686 [Apollo Super South] rather than the VT82C586/A/B
PCI-to-ISA [Apollo VP.

I'm not sure how different the 686 is from the 586--can I just go ahead and take
the same code path, or do I bypass it completely, or what?

Chris

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

                 reply	other threads:[~2004-06-11 15:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40C9D4C9.4030907@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mgreer@mvista.com \
    --cc=rvinson@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).