Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Harald Koerfgen <hkoerfg@web.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Dave Airlie <airlied@csn.ul.ie>,
	Ralf Baechle <ralf@uni-koblenz.de>,
	linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: [patch] linux: declance multicast filter fixes
Date: Fri, 29 Mar 2002 08:57:50 +0100	[thread overview]
Message-ID: <E16qrGh-0004Vu-00@smtp.web.de> (raw)
In-Reply-To: <Pine.GSO.3.96.1020328134253.11187B-100000@delta.ds2.pg.gda.pl>

On Thursday 28 March 2002 14:01, Maciej W. Rozycki wrote:
>  But the I/O ASIC chip is smart enough to merge data from the 8-bit ROM
> device without problems and present four consecutive bytes as 32-bit
> quantities to the host CPU.

A simple 4 to 1 mapping is easy, even for the average hardware developer :-)

> Why couldn't it do the same for the LANCE?
> Host memory addresses are generated on behalf of the LANCE by the I/O ASIC
> anyway.

Probably because this would have made the IOASIC 0.0034 cents more expensive?

> Of course not all designers have a clue, sigh...  A brief study of
> available documentation suggests no merging mode was implemented for the
> LANCE and bit 0 of addresses generated is simply hardwired to 0. :-(

That's my interpretation as well.

Greetings,
Harald

      reply	other threads:[~2002-03-29  7:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 18:04 [patch] linux: declance multicast filter fixes Maciej W. Rozycki
2002-03-22 11:08 ` Dave Airlie
2002-03-22 11:08   ` Dave Airlie
2002-03-23 14:01   ` Maciej W. Rozycki
2002-03-24 13:51     ` Dave Airlie
2002-03-24 13:51       ` Dave Airlie
2002-03-25 11:40       ` Maciej W. Rozycki
2002-03-27 21:20         ` Harald Koerfgen
2002-03-28 13:01           ` Maciej W. Rozycki
2002-03-29  7:57             ` Harald Koerfgen [this message]

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=E16qrGh-0004Vu-00@smtp.web.de \
    --to=hkoerfg@web.de \
    --cc=airlied@csn.ul.ie \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@uni-koblenz.de \
    /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