From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: hadi@cyberus.ca
Cc: netdev@oss.sgi.com
Subject: Re: TOE brain dump
Date: Mon, 04 Aug 2003 22:06:34 +0200 [thread overview]
Message-ID: <3F2EBCCA.5060708@softhome.net> (raw)
In-Reply-To: <1060026149.1102.411.camel@jzny.localdomain>
jamal wrote:
>
>> It just takes only 3k. And it handles some special (read -
>>proprietary) functions too - some bugs of some other pieces of hardware.
>>NPU does all stuff by itself, but sometimes we need to extract
>>configuration information which is direct to us, for example.
>
>
> Please provide me a pointer if you can - I am very interested in the 2G
> code space you mention.
>
I'm not sure - actually as I wrote - immediately gone checking specs.
try:
http://www.vitesse.com/products/categories.cfm?family_id=5&category_id=16
...
[ Okay I got to docs server. ] You are right - It has limit of 4K
insns == 16k of executable memory.
Sorry for confusion :(
We really can address a lot of memory - we have 32MB for routing info
and configuration - but for execution only 16kB of memory is available...
next prev parent reply other threads:[~2003-08-04 20:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:45 TOE brain dump jamal
2003-08-04 18:48 ` Ihar 'Philips' Filipau
2003-08-04 19:42 ` jamal
2003-08-04 20:06 ` Ihar 'Philips' Filipau [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-04 18:36 Perez-Gonzalez, Inaky
2003-08-04 19:03 ` Alan Cox
2003-08-02 17:04 Werner Almesberger
2003-08-02 17:32 ` Nivedita Singhvi
2003-08-02 18:06 ` Werner Almesberger
2003-08-02 19:08 ` Jeff Garzik
2003-08-02 21:49 ` Werner Almesberger
2003-08-03 6:40 ` Jeff Garzik
2003-08-03 17:57 ` Werner Almesberger
2003-08-03 18:27 ` Erik Andersen
2003-08-03 19:40 ` Larry McVoy
2003-08-03 20:13 ` David Lang
2003-08-03 20:30 ` Larry McVoy
2003-08-03 21:21 ` David Lang
2003-08-03 23:44 ` Larry McVoy
2003-08-03 21:58 ` Jeff Garzik
2003-08-05 19:28 ` Timothy Miller
2003-08-03 20:34 ` jamal
[not found] ` <3F2DBB2B.9050803@aarnet.edu.au>
2003-08-04 5:25 ` David S. Miller
2003-08-06 7:12 ` Andre Hedrick
[not found] ` <Pine.LNX.4.10.10308060009130.25045-100000@master.linux-ide .org>
2003-08-06 8:20 ` Lincoln Dale
2003-08-06 8:22 ` David S. Miller
2003-08-06 13:07 ` Jesse Pollard
2003-08-03 19:21 ` Eric W. Biederman
2003-08-04 19:24 ` Werner Almesberger
2003-08-04 19:26 ` David S. Miller
2003-08-05 17:25 ` Eric W. Biederman
2003-08-05 17:19 ` Eric W. Biederman
2003-08-06 5:13 ` Werner Almesberger
2003-08-06 7:58 ` Eric W. Biederman
2003-08-06 13:37 ` Werner Almesberger
2003-08-06 12:46 ` Jesse Pollard
2003-08-06 16:25 ` Andy Isaacson
2003-08-06 18:58 ` Jesse Pollard
2003-08-06 19:39 ` Andy Isaacson
2003-08-06 21:13 ` David Schwartz
2003-08-03 4:01 ` Ben Greear
2003-08-03 6:22 ` Alan Shih
2003-08-03 6:41 ` Jeff Garzik
2003-08-03 8:25 ` David Lang
2003-08-03 18:05 ` Werner Almesberger
2003-08-03 22:02 ` Alan Shih
2003-08-03 20:52 ` Alan Cox
2003-08-04 14:36 ` Ingo Oeser
2003-08-04 17:19 ` Alan Shih
2003-08-05 8:15 ` Ingo Oeser
2003-08-02 20:57 ` Alan Cox
2003-08-02 22:14 ` Werner Almesberger
2003-08-03 20:51 ` Alan Cox
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=3F2EBCCA.5060708@softhome.net \
--to=filia@softhome.net \
--cc=hadi@cyberus.ca \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).