Subject: RE: Pegasos port status
To: 'Jorge Acereda' <jacereda@gmail.com>
From: Matt Sealey <matt@genesi-usa.com>
List: port-ofppc
Date: 07/16/2006 04:26:26
This is a multi-part message in MIME format.
------=_NextPart_000_0032_01C6A890.0395BE20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Genesi has added SIGNIFICANT functionality to the firmware in order to make it a product we can sell. Not just firmware
functionality, but abstraction, initialization, the x86 emulator for graphics cards etc.
You will not be seeing the source code to it any time soon, any more than you are going to see the source code to the
Award or American Megatrends BIOS. The whole point is, you don't need the source code to have a compliant Open Firmware.
The firmware presents and abstracts the features, and you use them. If something breaks you tell us about it. We have fixed
a lot of things in the last 2 years and it was a lot of work.
--
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
_____
From: Jorge Acereda [mailto:jacereda@gmail.com]
Sent: Saturday, July 15, 2006 3:06 PM
To: Raquel Velasco and Bill Buck
Cc: Allen Briggs; Matt Sealey; DataZap; Tim Rightnour; port-powerpc@netbsd.org; netbsd-ports@netbsd.org; port-ofppc@netbsd.org
Subject: Re: Pegasos port status
On 7/13/06, Raquel Velasco and Bill Buck
<bbrv@genesi.lu> wrote:
Hi Allen. :)
Have you seen this:
http://www.power.org/members/developers/downloads/genesi_pegasosppc
The Pegasos schematics are there for download. You have to join as a
FREE Developer Member first, but they are there and you can get them.
<...>
Ok, hardware specs are really useful for a native port, but for NetBSD/ofppc what we really need is a compliant Open Firmware. Now,
what about my petition to release SmartFirmware sources? Could you setup a repository holding those sources so that the severe
problems could be fixed? Codegen released their sources with a BSD license long ago, so what's the value in keeping those closed?
I'd be glad to do some testing and bug-hunting on that, and once the OF-compliance problems are fixed, booting the ofppc port should
be a piece of cake.
------=_NextPart_000_0032_01C6A890.0395BE20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5450.4" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Genesi has added SIGNIFICANT functionality to =
the firmware=20
in order to make it a product we can sell. Not just firmware =
functionality, but=20
abstraction, initialization, the x86 emulator for graphics cards=20
etc.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>You will not be seeing the source code to it=20
</FONT></SPAN><SPAN class=3D484002209-16072006><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>any time soon, any more than you are going to see the source =
code to=20
the</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Award or American Megatrends BIOS. The whole =
point is, you=20
don't need the source code to have a compliant Open=20
Firmware.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The </FONT></SPAN><SPAN =
class=3D484002209-16072006><FONT=20
face=3DArial color=3D#0000ff size=3D2>firmware presents and abstracts =
the features,=20
and you use them. If something breaks you tell us about it. We have=20
fixed</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>a lot of things in the last 2 years and it was =
a lot of=20
work.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D484002209-16072006><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>--<BR>Matt Sealey =
<matt@genesi-usa.com><BR>Manager,=20
Genesi, Developer Relations<BR></FONT></P></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Jorge Acereda=20
[mailto:jacereda@gmail.com] <BR><B>Sent:</B> Saturday, July 15, 2006 =
3:06=20
PM<BR><B>To:</B> Raquel Velasco and Bill Buck<BR><B>Cc:</B> Allen =
Briggs; Matt=20
Sealey; DataZap; Tim Rightnour; port-powerpc@netbsd.org;=20
netbsd-ports@netbsd.org; port-ofppc@netbsd.org<BR><B>Subject:</B> Re: =
Pegasos=20
port status<BR></FONT><BR></DIV>
<DIV></DIV>On 7/13/06, Raquel Velasco and Bill Buck
<DIV><SPAN class=3Dgmail_quote><B class=3Dgmail_sendername></B><<A=20
href=3D"mailto:bbrv@genesi.lu">bbrv@genesi.lu</A>> wrote:</SPAN>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Hi=20
Allen. :)<BR><BR>Have you seen this:<BR><BR><A=20
=
href=3D"http://www.power.org/members/developers/downloads/genesi_pegasosp=
pc">http://www.power.org/members/developers/downloads/genesi_pegasosppc</=
A><BR><BR>The=20
Pegasos schematics are there for download. You have to =
join as a=20
<BR>FREE Developer Member first, but they are there and you can get=20
them.</BLOCKQUOTE>
<DIV><BR><...><BR><BR> <BR></DIV>Ok, hardware specs are =
really=20
useful for a native port, but for NetBSD/ofppc what we really need is =
a=20
compliant Open Firmware. Now, what about my petition to release =
SmartFirmware=20
sources? Could you setup a repository holding those sources so that =
the severe=20
problems could be fixed? Codegen released their sources with a BSD =
license=20
long ago, so what's the value in keeping those closed?<BR><BR>I'd be =
glad to=20
do some testing and bug-hunting on that, and once the OF-compliance =
problems=20
are fixed, booting the ofppc port should be a piece of=20
cake.<BR><BR></DIV><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0032_01C6A890.0395BE20--