From: Paul Kasper <paul@patton.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: ellis@spinics.net, linux-mips@oss.sgi.com
Subject: Re: Galileo 64240
Date: Wed, 09 Jan 2002 12:52:48 -0500 [thread overview]
Message-ID: <3C3C8370.2B1F1C54@patton.com> (raw)
In-Reply-To: NEBBLJGMNKKEEMNLHGAIGELHCEAA.mdharm@momenco.com
Matthew Dharm wrote:
>
> I would love a copy of that, personally. Could you send it to me (or
> the list)?
>
> Matt
>
> --
> Matthew D. Dharm Senior Software Designer
> Momentum Computer Inc. 1815 Aston Ave. Suite 107
> (760) 431-8663 X-115 Carlsbad, CA 92008-7310
> Momentum Works For You www.momenco.com
>
> > I also have a hacked-up port of MontaVista's HHLinux gt96100eth code
> > that is functional on 64240 and 64240A in little-endian mode and
> > untested in BE. It still lacks support for any "advanced"
> > features of
> > the Galileo chips.
> >
> > --
> > /"\ . . . . . . . . . . . . . . . /"\
> > \ / ASCII Ribbon Campaign \ / Paul R. Kasper
> > X - NO HTML/RTF in e-mail X Patton Electronics Co.
> > / \ - NO MSWord docs in e-mail / \ 301-975-1000 x173
> >
Matt:
I'll zip up a copy of the gt64240eth driver as soon as I can track down
the relvant include files, and send it to you. I should mention that
I'm still running it on a 2.4.0-test9 kernel.
Maybe after you verify that it is complete, we can post it to the list.
Our board configuration is a QED RM5261A with GT64240A, Intel Flash,
STK1744 RTC/NVRAM, 16C2550 DUART, and a bunch of Conexant HDLC I/O --
not all of which is coded yet.
I do have the basic arch/mips/patton/{generic,dsl3224} board support
trees which were based on mips/atlas and ev96100 ports but,
unfortunately, I still reference some Galileo/VxWorks sample code in the
interrupt handler. This needs to be cleaned up. I originally used
their code only because I did not have a working 64240 board to test
with and the Galileo datasheets are so ambiguous that I thought that
their sample code programmers might have had some hidden insight into
the chips. I since have learned that the opposite is true and need to
clean all of that stuff out.
--
Paul K.
--
/"\ . . . . . . . . . . . . . . . /"\
\ / ASCII Ribbon Campaign \ / Paul R. Kasper
X - NO HTML/RTF in e-mail X Patton Electronics Co.
/ \ - NO MSWord docs in e-mail / \ 301-975-1000 x173
next prev parent reply other threads:[~2002-01-09 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 22:17 Galileo 64240 ellis
2002-01-07 22:49 ` Matthew Dharm
2002-01-07 22:49 ` Matthew Dharm
2002-01-08 12:19 ` Paul Kasper
2002-01-08 12:45 ` Paul Kasper
2002-01-08 21:28 ` Matthew Dharm
2002-01-08 21:28 ` Matthew Dharm
2002-01-09 17:52 ` Paul Kasper [this message]
2002-01-10 4:16 ` Pete Popov
[not found] <no.id>
2002-01-08 23:04 ` ellis
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=3C3C8370.2B1F1C54@patton.com \
--to=paul@patton.com \
--cc=ellis@spinics.net \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.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