From: Sergey Podstavin <podstavin@dev.rtsoft.ru>
To: Matthew Dharm <mdharm@momenco.com>
Cc: 'Pavel Kiryukhin' <savl@dev.rtsoft.ru>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: RE: Marvell MV64340 documentation
Date: 27 Jan 2004 22:44:03 +0300 [thread overview]
Message-ID: <1075232643.4058.74.camel@podstavin.dev.rtsoft.ru> (raw)
In-Reply-To: <000d01c3e50d$4a6e8b40$7200a8c0@internal.momenco.com>
It's OK, don't worry.
Sergey.
On Tue, 2004-01-27 at 22:39, Matthew Dharm wrote:
> I can't really answer something that specific without violating the NDA.
> Sorry.
>
> 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
>
>
> > -----Original Message-----
> > From: linux-mips-bounce@linux-mips.org
> > [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Sergey
> > Podstavin
> > Sent: Tuesday, January 27, 2004 10:45 AM
> > To: Matthew Dharm
> > Cc: Pavel Kiryukhin; linux-mips@linux-mips.org
> > Subject: Marvell MV64340 documentation
> >
> >
> > Hello Matthew!
> >
> > Could you write me what do bits mean in the interrupt cause
> > registers for MV64340 Ethernet? I need to handle them in the
> > interrupt handler for the Gigabit Ethernet in the driver.
> >
> > Best wishes,
> > Sergey Podstavin,
> > software engineer.
> >
> >
>
>
next prev parent reply other threads:[~2004-01-27 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 18:44 Marvell MV64340 documentation Sergey Podstavin
2004-01-27 19:39 ` Matthew Dharm
2004-01-27 19:39 ` Matthew Dharm
2004-01-27 19:44 ` Sergey Podstavin [this message]
2004-01-28 13:57 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 12:49 Clock interrupt simulation on sde-gdb navin
2004-01-27 13:47 ` Chris Dearman
2004-01-27 14:45 ` Marvell MV64340 documentation Pavel Kiryukhin
2004-01-27 15:25 ` Ralf Baechle
2004-01-27 18:12 ` Matthew Dharm
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=1075232643.4058.74.camel@podstavin.dev.rtsoft.ru \
--to=podstavin@dev.rtsoft.ru \
--cc=linux-mips@linux-mips.org \
--cc=mdharm@momenco.com \
--cc=savl@dev.rtsoft.ru \
/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.