Subject: RE: Pegasos port status
To: =?iso-8859-1?Q?'Jorge_Acereda_Maci=E1'?= <email@example.com>
From: Matt Sealey <firstname.lastname@example.org>
Date: 07/17/2006 04:09:45
> -----Original Message-----
> From: Jorge Acereda Maci=E1 [mailto:email@example.com]=20
> Sent: Sunday, July 16, 2006 3:50 PM
> To: firstname.lastname@example.org
> Cc: 'Raquel Velasco and Bill Buck'; 'Allen Briggs';=20
> 'DataZap'; 'Tim Rightnour'; email@example.com;=20
> firstname.lastname@example.org; email@example.com
> Subject: Re: Pegasos port status
> Hi Matt,
> Matt Sealey wrote:
> > than you are going to see the source code to the Award or American=20
> > Megatrends BIOS. The whole point is, you don't need the=20
> > source code to have a compliant Open Firmware.
> So, are you stating that SmartFirmware is finally OF-compliant?
> Can you check this?
> here 1 , 0 , 2@ .
> (should print 1)
> If so, where can I get the new firmware?
It says 0, we know about this bug already.
Can you really say that a Forth bug like this really destroys all
hope of it ever working, and the only solution is to Open Source it
as Allen wants?
I disagree wholeheartedly. We can fix that bug ourselves (in fact you
already told us about it, it just happens to be at the bottom of a
list, as most operations performed on the drivers and device tree are
accessed via the client interface and not interpreted Forth. Our
(and the CodeGen source we licensed and based it on) firmware is written
in C, so a Forth stack bug doesn't truly affect it in a way it might =
Please don't waste your time petitioning. It would be more useful if
you collated these bugs, presented your ideas on why they are broken,
and submitted them here. You have, and we appreciate that. We're working
Matt Sealey <firstname.lastname@example.org>
Manager, Genesi, Developer Relations