Welcome, Guest. Please login or register.

Author Topic: 10 Questions for MAI, developers of AmigaOne/Teron.  (Read 7799 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: 10 Questions for MAI, developers of AmigaOne/Teron.
« on: May 27, 2003, 06:16:40 PM »
@YttriumOx

Oh no not another one you can't understand the
difference between a evaluation board with full
dev-support and a consumer board.

Ever wondered why the price drops by 1560$
with the 2nd ordered board, or why they don't
give prices for more than 5 boards ?

Hint, everybody who wants to buy a larger quantity
off those boards, can do it under the same terms
as Eyetechs buys them, and can most probraly resell
them somewhat cheaper (no fee for the A1-licence).

But to answer Rodneys question:
The PX uses the same south and northbrigde as the CX,
and therefore has the same limitations, like
only SDR. Slapping a 970 on such a board would
most likely be quite dissapointing
performance-wise, and quite hard to achieve due
to different bus-protocolls.

This would need an ArticiaP with fitting mobo,
but since the P is allready delayed by over
6 months, and there is (logically) no sign of an
enduser-ready mobo for it, I wouldn't hold my
breath for it ...
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: 10 Questions for MAI, developers of AmigaOne/Teron.
« Reply #1 on: May 27, 2003, 08:14:11 PM »
@The_editor

Because the 686A (used in the original Teron)
doesn't have those bugs (but also only UDMA66),
is/was cheap and easy to connect to the NB ?

Because back than noone at MAI even thought about
turning that design into a consumer-product, and
such minor troubles didn't hurt much on a eval-board ?

Maybe becaues Eyetech have neither the cash nor
the knowledge to design a mobo with another NB from
ground, to avoid those toubles ?
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: 10 Questions for MAI, developers of AmigaOne/Teron.
« Reply #2 on: May 27, 2003, 08:41:11 PM »
@Henning

The VT8231 in it's current (latest) revision
does not have any critical bugs, perfoms just
as good (if not better) than the 686B (with a
SW-based bugfix), offers more features and uses
less power.

But no no no, that is not the true path and
most therefore be wrong  :-P
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: 10 Questions for MAI, developers of AmigaOne/Teron.
« Reply #3 on: May 28, 2003, 02:18:19 PM »
@hnl_dk

Yeap the 1st revision had the same probs as the
686B, but since the the 8231 was brand new and
targeted for high-price-devices (laptops) while the
686 was allready on its way out they fixed the 8231.

You won't find a "VIA_DMA_bug" in any Pegasos.

It may also be that the 8231 is a bit harder use
for the HW-engineer, but that isn't "our" prob.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else