linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linux-emb <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mv6360 support in mv64x60.c (was Re: GT64260_eth (Ethernet) Driver)
Date: Thu, 01 Jul 2004 15:13:21 +0100	[thread overview]
Message-ID: <1088691201.14216.2977.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <40E1E94B.9060204@mvista.com>


More progress... the IRQ code works a bit better if it's ic_bh->v_addr
is at offset zero in the chip instead of the 0xc18 which is correct only
for the GT64260. The host bridge itself appears on the bus as device #3,
which is why we couldn't autodetect it by looking at vendor/device of
device #0.

∃ an Ethernet driver for the MV64340 (the MIPS version of the chip). It
doesn't use OCP though -- there's no OCP on MIPS. Can someone explain
why OCP is used instead of the generic platform_device functionality
provided by the kernel? Should we convert MIPS to OCP?

--
dwmw2


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

  parent reply	other threads:[~2004-07-01 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 22:12 mv6360 support in mv64x60.c (was Re: GT64260_eth (Ethernet) Driver) Mark A. Greer
2004-06-30 10:23 ` David Woodhouse
2004-07-01 14:13 ` David Woodhouse [this message]
2004-07-01 15:24   ` Matt Porter
2004-07-01 19:10   ` Mark A. Greer
     [not found]     ` <1088777061.14216.4449.camel@hades.cambridge.redhat.com>
2004-07-02 23:02       ` Mark A. Greer

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=1088691201.14216.2977.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mgreer@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).