From: priya <priya@procsys.com>
To: Brad Larson <Brad_Larson@pmc-sierra.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Porting davicom driver to pmon
Date: Tue, 05 Apr 2005 10:05:20 +0530 [thread overview]
Message-ID: <42521588.D671F6EE@procsys.com> (raw)
In-Reply-To: 04781D450CFF604A9628C8107A62FCCF013DDE1D@sjc1exm01.pmc_nt.nt.pmc-sierra.bc.ca
Hi Brad,
Its a davicom chip. I tried porting the linux driver to pmon - but still iam facing
problems sending the set up frame - actually in the linux the set up frame is sent 5
times. Iam doing the same thing out here too. But while trying to send the setup frame
for the second time the network status report register(cr5) value is 0xfc200007 (which
indicates - move setup frame from host memory, transmit buffer un-available, and transmit
process complete)
Also the network operation mode (register cr6) gets set to hash filtering, while i have
enabled perfect filtering mode in the transmit descriptor. Any idea why this corruption
is happening?
regards
priya
Brad Larson wrote:
> It's a DEC Tulip type chip handled by the dc driver. Should work with "dc* at pci ?".
> Should because I have no own experience with that particular chip.
>
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org]On Behalf Of priya
> Sent: Monday, April 04, 2005 7:55 AM
> To: linux-mips@linux-mips.org
> Subject: Porting davicom driver to pmon
>
> Hi,
> I am using a custom board which has mips
> processor and davicom ethernet chip. Iam
> using pmon bootloader. Has anyone ported
> davicom driver for pmon. Iam facing a
> lot of problem in sending even a set up
> frame
>
> regards
> priya
next prev parent reply other threads:[~2005-04-05 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 17:38 Porting davicom driver to pmon Brad Larson
2005-04-05 4:35 ` priya [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 14:55 priya
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=42521588.D671F6EE@procsys.com \
--to=priya@procsys.com \
--cc=Brad_Larson@pmc-sierra.com \
--cc=linux-mips@linux-mips.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.