All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Roland Dreier <roland@topspin.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ethernet PHY chip discovery not working on 855T with 971/972 chips
Date: Mon, 14 Jul 2003 13:49:27 -0700	[thread overview]
Message-ID: <20030714134927.A2543@home.com> (raw)
In-Reply-To: <52ptkewfu2.fsf@topspin.com>; from roland@topspin.com on Sun, Jul 13, 2003 at 09:29:09AM -0700


On Sun, Jul 13, 2003 at 09:29:09AM -0700, Roland Dreier wrote:
>
>     Paul> .... It's a bit disappointing that 8xx still doesn't compile
>     Paul> in 2.5.  I don't have any 8xx hardware to test on so I have
>     Paul> been relying on others to update it.
>
> Speaking of 2.5, since our custom boards are in production now, I have
> an Ebony (440GP eval board) that is completely idle, and some free
> hacking time.  Is there any 4xx work that I could help with?  Is

A 44x thing that would be nice is to abstract the PCI-X bridge support
into a common call (or calls) so it can be configured into a variety
of windowing modes...like alternative monarch memory maps or any
non-monarch configurations.  Part of this would work would require that
fixup_bigphys_addr() be made aware of these window changes.  In addition
it would be nice to have a helper function that sets the same values as
the current hardcoded monarch configuration via the new abstracted
interface since that is a common configuration.

Sorry, but you asked. :)

> linuxppc-2.5 the right tree to use?

Yes, nothing 44x-related should be going in without a 2.5 patch.
I've invested considerable time making sure that it was usable
by other developers on 44x...hopefully that still the case after
two weeks of vacation.

Regards,
--
Matt Porter
mporter@kernel.crashing.org

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

  reply	other threads:[~2003-07-14 20:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09  2:17 Ethernet PHY chip discovery not working on 855T with 971/972 chips Dean Matsen
2003-07-09  2:29 ` Dean Matsen
2003-07-09  2:56   ` Eugene Surovegin
2003-07-09  5:21     ` Dan Malek
2003-07-09  5:50       ` Dean Matsen
2003-07-09 14:37         ` Dan Malek
2003-07-09 16:39           ` Dean Matsen
2003-07-09 20:54           ` Dean Matsen
2003-07-09 21:21             ` Wolfgang Denk
     [not found]               ` <20030711151834.GU17433@ip68-0-152-218.tc.ph.cox.net>
2003-07-11 15:43                 ` Wolfgang Denk
2003-07-11 15:52                   ` Tom Rini
2003-07-11 18:29                     ` Wolfgang Denk
2003-07-11 18:50                       ` Tom Rini
2003-07-11 19:18                         ` Wolfgang Denk
2003-07-11 19:34                           ` Tom Rini
2003-07-11 21:04                             ` Wolfgang Denk
2003-07-14  6:21                         ` Pantelis Antoniou
2003-07-14  7:58                           ` Wolfgang Denk
2003-07-14 14:31                             ` Tom Rini
2003-07-14 19:26                               ` Wolfgang Denk
2003-07-15 15:04                                 ` Tom Rini
2003-07-11 23:21                 ` Dean Matsen
2003-07-12  1:01                   ` Paul Mackerras
2003-07-12 21:13                     ` Dean Matsen
2003-07-12 21:54                       ` Wolfgang Denk
2003-07-14 14:52                       ` Tom Rini
2003-07-13 15:48                     ` Dan Malek
2003-07-13 16:29                       ` Roland Dreier
2003-07-14 20:49                         ` Matt Porter [this message]
2003-07-15  5:08                           ` Roland Dreier

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=20030714134927.A2543@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=roland@topspin.com \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.