From: Florian Lohoff <flo@rfc822.org>
To: SGI MIPS list <linux-mips@oss.sgi.com>,
Debian MIPS list <debian-mips@lists.debian.org>,
engel@unix-ag.org
Subject: Re: [long] Lance on DS5k/200
Date: Sun, 29 Jul 2001 02:14:00 +0200 [thread overview]
Message-ID: <20010729021400.C6113@paradigm.rfc822.org> (raw)
In-Reply-To: <20010728214114.C27316@lug-owl.de>; from jbglaw@lug-owl.de on Sat, Jul 28, 2001 at 09:41:14PM +0200
On Sat, Jul 28, 2001 at 09:41:14PM +0200, Jan-Benedict Glaw wrote:
> However, the chip actually does not transmit the frame. Please look
> at it because I don't have a clue about the lance chip. Especially,
> I see there problems:
> - lp->tx_buf_ptr_lnc[i] and lp->rx_buf_ptr_lnc[i] are
> quite low addresses. Is this correct? Are they relative
> to some other address (TC slot address?)
If its a TC base address all addresses must be below 128*1024 as
a TC Slot IIRC has a 128K Window.
> - while kernel's bootp tries to send the packet, only
> buffers [0] to [5] are used. Why are not all 16 buffers
> used?
Split between TX and RX ?
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-07-29 0:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 19:41 [long] Lance on DS5k/200 Jan-Benedict Glaw
2001-07-29 0:14 ` Florian Lohoff [this message]
2001-07-30 20:04 ` Maciej W. Rozycki
2001-07-29 13:16 ` Dave Airlie
2001-07-29 13:16 ` Dave Airlie
2001-07-30 20:06 ` Maciej W. Rozycki
2001-07-30 22:24 ` Jan-Benedict Glaw
2001-07-30 22:45 ` Maciej W. Rozycki
2001-07-30 22:45 ` Jan-Benedict Glaw
2001-07-29 21:26 ` Alan Cox
2001-07-29 21:26 ` Alan Cox
2001-07-30 23:00 ` Maciej W. Rozycki
2001-07-31 0:32 ` Thomas Bogendoerfer
2001-07-31 7:08 ` Geert Uytterhoeven
2001-08-02 13:45 ` Dave Airlie
2001-08-02 13:45 ` Dave Airlie
2001-07-31 7:03 ` Geert Uytterhoeven
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=20010729021400.C6113@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=debian-mips@lists.debian.org \
--cc=engel@unix-ag.org \
--cc=linux-mips@oss.sgi.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