On Fri, 2007-11-02 at 16:17 -0700, Javier Cardona wrote:
Andres,
On 11/2/07, Andres Salomon [EMAIL PROTECTED] wrote:
On Fri, 02 Nov 2007 12:54:35 -0700 (PDT)
Ashish Shukla [EMAIL PROTECTED] wrote:
So, uh.. This patch is from Javier, but was originally written by
Ashish? Did I get
On Sat, 03 Nov 2007 17:36:00 -0400
Mary Lou Jepsen [EMAIL PROTECTED] wrote:
Ship.1 are the bits Quanta is currently putting on machines in
the
factory. It is Build 624; Firmware Q2D03.
We are putting build 625 on mass production machines starting Monday,
Once Richard reports back about whether the DCON workaround
succeeded
We need to know before that so that we can make a decision with the DCON
initialization results - tonight china time at 8PM when we see the
results - quanta needs to do testing.
We may NOT be able to build tomorrow - they
I've never done a smoke test before. (and that smoke test is for the
more recent builds, rather than trial3/MP).
Other than having some trouble around activity and library installation,
625 checked out fine.
Upgrading from 623-625 indicated just changes in the kernel, so random
other stuff did
There shouldn't be any problems if 624 is used for MP.
The testing process is there for a reason, and should be strictly
followed.
The DCON bug that 625 fixes (#4479) will only show up on a small
number of machines, and it's frequency is low enough in normal
operation of our current software
John,
It sounds like you recommend that Quanta put 624 on the laptops at the end
of mfg test.
Is that true?
If so, I would support that decision as well; and we don't need to go
through the release testing for 625.
Regards,
Kim
On 11/4/07, John Watlington [EMAIL PROTECTED] wrote:
There
On Nov 4, 2007, at 1:04 AM, John Watlington wrote:
The DCON bug that 625 fixes (#4479) will only show up on a small
number of machines, and it's frequency is low enough in normal
operation of our current software (where we only support sleep,
not automatic suspend) that it will be an extremely
Quanta wants assurance that the software workaround which was broken
in #4479 is fixed.
Richard's testing is necessary to confirm this. It is also
essential that the kernel fix
which is theoretically the only difference between 624 and 625 be
part of the production
test code to further
