OK, I just committed the earlymtrr patch for faster boots.
I think at this point we stop taking patches to the core stuff, with one remaining issue: we need the ecc patch so K7s won't blow up. So, once that's in, I think we should try to declare 1.0.1 closed.
People who own various mainboards, please test with the latest cvs, save for those of you with K7 boards.
ron
ron minnich wrote:
I think at this point we stop taking patches to the core stuff, with one remaining issue: we need the ecc patch so K7s won't blow up. So, once that's in, I think we should try to declare 1.0.1 closed.
I have a core change for 440bx that adds a mouse option into the superio structure. Too late?
People who own various mainboards, please test with the latest cvs, save
Well looks like I'm just in time. I now have full operation of our board under linuxbios+ADLO. Everything works just like it did under the old COTS bios. Yah!
I'll send in a patch today vs the latest CVS.
What does the freeze mean for work on the 1.x tree? Is there going to be a 1.1.x? I still have a few things I would like to work on like getting the video bios to work without ADLO. Last I checked myself and at least one other person were having problems getting that to compile.
On Tue, 24 Jun 2003, Richard Smith wrote:
I have a core change for 440bx that adds a mouse option into the superio structure. Too late?
no, I guess not. It's too important and I doubt will cause trouble.
Send patch.
What does the freeze mean for work on the 1.x tree? Is there going to be a 1.1.x? I still have a few things I would like to work on like getting the video bios to work without ADLO. Last I checked myself and at least one other person were having problems getting that to compile.
I think there will have to be. 2.x is a big change for people and I think 1.x will continue for a while.
ron
ron minnich wrote:
I have a core change for 440bx that adds a mouse option into the superio structure. Too late?
no, I guess not. It's too important and I doubt will cause trouble.
Send patch.
I'm doing a cvs update now. Sourceforge is _slow_ today.
On Tue, 24 Jun 2003, Richard Smith wrote:
I'm doing a cvs update now. Sourceforge is _slow_ today.
broken too.
ron
ron minnich wrote:
On Tue, 24 Jun 2003, Richard Smith wrote:
I'm doing a cvs update now. Sourceforge is _slow_ today.
broken too.
Are you refering to all the EOF's you get when trying to update or check out? If so then its a try-try-again thing. I suspect sf is reaching the limit on the number of concurrent CVS sessions it can handle.
I just continued to do a 'cvs update' until it finally took. Took about 20 re-tries or so.
Big time slow though... It's _still_ updateing.
-
Richard Smith -
ron minnich