All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: mod+linuxppc-dev@missioncriticallinux.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Status of linuxppc support for Galileo GT64260
Date: Tue, 04 Dec 2001 18:45:56 -0700	[thread overview]
Message-ID: <3C0D7C54.A28FA732@mvista.com> (raw)
In-Reply-To: 200112042332.SAA17067@missioncriticallinux.com


mod+linuxppc-dev@missioncriticallinux.com wrote:

> I'm asking because I recall seeing
> messages on these lists saying that
> code had been checked in with interrupt
> problems, PCI problems, no integrated-Enet
> driver and generally in "needs work"
> condition.  I notice that there is now a
> (strangely familiar) driver included for
> the integrated Enet,

Yes, its the same driver the galileo originally wrote that mclx, your
company, moved to 2.4 AFAICT.  If you wrote it, fine, change the
copyright and author.  BTW, its *still* needs work so feel free.


> but (except for the
> recent exchange about how the GT64260 and
> VT82C686B don't play so nice together) I
> don't find much 64260-related discussion
> here except one terse followup message
> stating that PCI works.

There have been a few pushes to 64260 related code since the original
push.  If you want to keep up on it, do regular pulls and look at the
code and/or get on the linuxppc-commit mailing list and look for pushes
that touch files you care about.

> So, is anybody using the current code?

Yes, me--at least the code of a week or so ago.  Others are to if they
wish to speak up.

> Would I be wrong to interpret the fact
> that it wouldn't compile when I tried it
> today as indication that not much has

> happened since the initial checkin by
> MontaVista?

My src tree is a week or so out of date but it compiles just fine.
Not compiling is news to me.  Why don't you fix it and send a patch? ;)

> Are the interrupt problems
> alluded to at the time of that initial
> checkin (could somebody characterize
> them for me?) still an issue?

You can still lose PCI interrupts with the 64260 (see errata) which is a
real problem if you have an nfs-mounted root filesystem.  The 64260A is
stable for me except after a while something happens and my bdi can no
longer talk to the processor and the system appears to hang.

>  Does
> the PCI support seem solid?

It was last time I tested.

> Anything
> in particular I need to watch out for?

No mpsc/uart driver yet.  That's being worked on but if you have one that
works well with the 64260A's errata, feel free to pass it along.  I know
there is at least one person working on a dual 7450 + 64260A combo.
Don't think its up with both cpu's yet.

Mark


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

  reply	other threads:[~2001-12-05  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 23:32 Status of linuxppc support for Galileo GT64260 mod+linuxppc-dev
2001-12-05  1:45 ` Mark A. Greer [this message]
2001-12-05  4:32 ` Tom Rini

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=3C0D7C54.A28FA732@mvista.com \
    --to=mgreer@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mod+linuxppc-dev@missioncriticallinux.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 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.