From: benh@kernel.crashing.org
To: Alain RICHARD <alain.richard@equation.fr>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Support for new Dual G4 1 Gig machines?
Date: Wed, 30 Jan 2002 15:55:30 +0100 [thread overview]
Message-ID: <20020130145530.1118@mailhost.mipsys.com> (raw)
In-Reply-To: <F83E36A3-1565-11D6-8E33-0030657D0D7C@equation.fr>
>Just for information, why do you consider sungem better than gmac ? What
>kind of functionnalities is it supposed to better handle than gmac ?
no copy, better perfs (after the latest tuning we did), better management
of link (including fallback to forced speeds if autoneg fails, ...), support
for ethtool ioctls, better power management (especially the chip isn't shut
down immediately on ifconfig down, but only after about 10 seconds which means
a dhcp client will work better).
>Also about the video cards, there is two options :
>
>- ATI Radeon 7500 (32 Mo)
>- NVIDIA GeForce4 MX (64 Mo of RAM)
>
>Is there any clue about the support of each one ?
ATI will probably work properly with 2D accel, end eventually DRI soon,
while nVidia will be problematic since they don't provide us with specs
nor drivers.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-30 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C55A9A8.9B3EB57E@wvi.com>
2002-01-28 20:34 ` Support for new Dual G4 1 Gig machines? Christopher Murtagh
2002-01-29 12:39 ` benh
2002-01-29 14:52 ` Christopher Murtagh
2002-01-29 15:01 ` Holger Bettag
2002-01-29 17:01 ` Edward Swarthout
2002-01-29 19:09 ` benh
2002-01-29 19:08 ` benh
2002-01-30 9:44 ` Alain RICHARD
2002-01-30 14:55 ` benh [this message]
2002-01-29 17:25 ` Derrik Pates
2002-01-29 22:06 ` Tom Rini
2002-01-30 7:00 ` Eric Leblond
2002-01-28 19:40 Kevin B. Hendricks
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=20020130145530.1118@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=alain.richard@equation.fr \
--cc=linuxppc-dev@lists.linuxppc.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 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).