Re: v2 via/epia target broken [PMX:#]
Rom Minnich wrote: >I just mailed Dave the file for now. I figured out the file needed to go in src/mainboard/via/epia/Config.lb since diffing that one was a lot less different than targets/via/epia/Config.lb. However it still errors out with: dave.root% ./buildtarget via/epia build_dir=via/epia/epia No linuxbios config script found. Rebuilding it.. Input Grammar: /code/freebios2/util/newconfig/config.g Output File: via/epia/epia/config.py Configuring TARGET epia Will place Makefile, crt0.S, etc. in via/epia/epia Configuring ROMIMAGE normal Configuring DIR /config/Config.lb Configuring DIR /lib/Config.lb Configuring DIR /console/Config.lb Configuring DIR /stream/Config.lb Configuring DIR /devices/Config.lb Configuring DIR /pc80/Config.lb Configuring DIR /boot/Config.lb Configuring PART mainboard, path via/epia ===> WARNING: Changing default value of ROM_SIZE ===> ERROR: Options may only be set in target configuration file via/epia/Config.lb:0 mainboard/via/epia/Config.lb:0 -Dave ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: v2 via/epia target broken [PMX:#]
On Mon, 17 Nov 2003, Stefan Reinauer wrote: > > What is the procedure for the elite cvs server that the royalty use? > > Looks like Sourceforge is getting worse again.. Check > http://snapshots.linuxbios.org/ I just mailed Dave the file for now. Everyone, the change in the new config language is to the default keywork. You can tell I'm not a real language designer, as my syntax was: default name value option name=value stupid. changed to default name=value option name=value thanks ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: v2 via/epia target broken [PMX:#]
* Dave Ashley <[EMAIL PROTECTED]> [031117 18:50]: > Ron Minnich wrote: > >fixed, our fault, please cvs update. > > This reminds me of the Simpson's episode where they give homer the > correct number to call for emergencies--912. > > When I cvs update nothing changes. I'm using the common pondscum cvs server > as described in this document: > http://www.linuxbios.org/developer/download/index.html > > What is the procedure for the elite cvs server that the royalty use? Looks like Sourceforge is getting worse again.. Check http://snapshots.linuxbios.org/ Stefan -- Stefan Reinauer, SUSE LINUX AG Teamleader Architecture Development ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: v2 via/epia target broken [PMX:#]
Ron Minnich wrote: >fixed, our fault, please cvs update. This reminds me of the Simpson's episode where they give homer the correct number to call for emergencies--912. When I cvs update nothing changes. I'm using the common pondscum cvs server as described in this document: http://www.linuxbios.org/developer/download/index.html What is the procedure for the elite cvs server that the royalty use? -Dave ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
v2 via/epia target broken
dave.root% ./buildtarget via/epia build_dir=via/epia/epia No linuxbios config script found. Rebuilding it.. Input Grammar: /ram/freebios2/util/newconfig/config.g Output File: via/epia/epia/config.py Configuring TARGET epia Will place Makefile, crt0.S, etc. in via/epia/epia Configuring ROMIMAGE normal Configuring DIR /config/Config.lb Configuring DIR /lib/Config.lb Configuring DIR /console/Config.lb Configuring DIR /stream/Config.lb Configuring DIR /devices/Config.lb Configuring DIR /pc80/Config.lb Configuring DIR /boot/Config.lb Configuring PART mainboard, path via/epia Trying to find one of EQ on line 20: > default ROM_SIZE 256*1024 >^ List of nearby tokens: (@257) USES = 'uses' (@262) ID = '_ROMBASE' (@271) USES = 'uses' (@276) ID = 'XIP_ROM_SIZE' (@289) USES = 'uses' (@294) ID = 'XIP_ROM_BASE' (@307) USES = 'uses' (@312) ID = 'HAVE_MP_TABLE' (@389) DEFAULT = 'default' (@397) ID = 'ROM_SIZE' ===> ERROR: Could not parse file via/epia/Config.lb:0 mainboard/via/epia/Config.lb:0 dave.root% This broke as of a change 2003/10/13 -> 2003/10/14 in targets/buildtarget. -Dave ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: v2 via/epia target broken [PMX:#]
On Mon, 17 Nov 2003, Dave Ashley wrote: > Configuring PART mainboard, path via/epia > Trying to find one of EQ on line 20: > > default ROM_SIZE 256*1024 > >^ fixed, our fault, please cvs update. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA -- SPD.
On 2 Oct 2003, Eric W. Biederman wrote: > I see. Any chance that could be linux-kernel style indented? > Right now the indentation is not consistent. sure, indentation is one of those things that I never worry about one way or another, due to the indent wars. I switch projects too often to get too attached to one or the other. The indentation in there now is Stallman-default-style, from an indent-region. Anybody wants to linux-kernel-style indent it go for it :-) ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
On Thu, 2 Oct 2003, YhLu wrote: > Any plan on moving other to V2? > > Intel chipset? > Serverworks chipset? > Sis chipset? > Other?? Yes. I did this port in part to encourage people to look at doing other ports. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA -- SPD.
ron minnich <[EMAIL PROTECTED]> writes: > OK, the first SPD work is in. Ram size is now set from SPD. > > The next line of attack are the MA registers. > > The code is walking a tight line between code space size and register > allocation; see > northbridge/via/vt8601/raminit.c > for some details. These old pentiums are tight on registers! I see. Any chance that could be linux-kernel style indented? Right now the indentation is not consistent. > That said, doing this in C is even better than having an ICE. Cool. :) Eric ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
Any plan on moving other to V2? Intel chipset? Serverworks chipset? Sis chipset? Other?? Regards YH -邮件原件- 发件人: ron minnich [mailto:[EMAIL PROTECTED] 发送时间: 2003年10月2日 16:37 收件人: [EMAIL PROTECTED] 主题: V2 VIA EPIA OK, I'm done for a while. This thing is working well enough, I have some other things to do, and I think it is an ok example (criticism is welcome and appreciated, as long as it comes with suggestions for how to improve things). I did put some timing test and control in raminit.c, and it computes what looks like OK timing numbers, but if I use those numbers the machine locks up. You can see the code if interested in CVS. That's what i remember about this north bridge -- it's tricky to get it right. I think we should just leave it at the most conservative timings for now. I would like to know if there are other SPD parameters we ought to try to compute besides MA. Size was an important one to figure out, and it works now, but there are others we might want. Note that right now, due to space limitations, only the first two DRAM slots are getting configured. Please let me know if this is an issue for anyone. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 VIA EPIA
OK, I'm done for a while. This thing is working well enough, I have some other things to do, and I think it is an ok example (criticism is welcome and appreciated, as long as it comes with suggestions for how to improve things). I did put some timing test and control in raminit.c, and it computes what looks like OK timing numbers, but if I use those numbers the machine locks up. You can see the code if interested in CVS. That's what i remember about this north bridge -- it's tricky to get it right. I think we should just leave it at the most conservative timings for now. I would like to know if there are other SPD parameters we ought to try to compute besides MA. Size was an important one to figure out, and it works now, but there are others we might want. Note that right now, due to space limitations, only the first two DRAM slots are getting configured. Please let me know if this is an issue for anyone. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 VIA EPIA testing
I just tested the node with different memory dimms of different size and they're fine. We're going to be glad we made it to V2, and that we finally did SPD for this platform. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 VIA EPIA -- SPD.
OK, the first SPD work is in. Ram size is now set from SPD. The next line of attack are the MA registers. The code is walking a tight line between code space size and register allocation; see northbridge/via/vt8601/raminit.c for some details. These old pentiums are tight on registers! That said, doing this in C is even better than having an ICE. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
ron minnich <[EMAIL PROTECTED]> writes: > On 1 Oct 2003, Eric W. Biederman wrote: > > > Adam Agnew has pointed me at a frame buffer driver for the ATI Rage XL > > that should be capable of initializing the card without bios support. If > > that works we have an even better solution. > > That's been my hope all along -- that we could do this. But nvdia has made > it clear, again and again, that they won't play, and nvidia is too > important to ignore. Right. However I think we can start setting the precedent that onboard video is handled via open source code. Plug in video cards are an entirely different problem. Eric ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
Andrew, you should be able to build a working linuxbios image for EPIA by: cd targets ./buildtarget via/epia etc. If you can try to figure out why the IRQ table is not working, that would help. I'm stuck. It's the same table as on V1, it checks out when copied to ram, but Linux is just unhappy with it. Not sure why. If anyone wants to take a look that would help. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
On 1 Oct 2003, Eric W. Biederman wrote: > Right. However I think we can start setting the precedent > that onboard video is handled via open source code. Plug in > video cards are an entirely different problem. We can set this precedent, and we can try to cleave to it as best we can. But the market in this case will control our actions more than we might like. I don't like it; you know my feelings on this going back four years ago: I wanted to figure out those VGA registers and do all open source. But that didn't quite work out. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
Oh, I can see what is going to happen to buildrom now that Ron has discovered it... :-) Greg At 11:44 PM -0600 30/9/03, ron minnich wrote: Changes: new epia target for 512k: targets/via/epia/Config.512kflash.lb epia defaults to 256k flash buildtarget now takes either a directory, and uses directory/Config.lb, or takes a file e.g. buildtarget via/epia will use via/epia/Config.lb, and buildtarget via/epia/Config.512kflash.lb will use that file. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
On 1 Oct 2003, Eric W. Biederman wrote: > Adam Agnew has pointed me at a frame buffer driver for the ATI Rage XL > that should be capable of initializing the card without bios support. If > that works we have an even better solution. That's been my hope all along -- that we could do this. But nvdia has made it clear, again and again, that they won't play, and nvidia is too important to ignore. thanks ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA Build Errors
I have via-rhine etherboot and if anyone need it, I can mail it to him. - Original Message - From: "ron minnich" <[EMAIL PROTECTED]> To: "Randall H. Craig" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 01, 2003 1:03 PM Subject: Re: V2 VIA EPIA Build Errors > On Tue, 30 Sep 2003, Randall H. Craig wrote: > > > At the end of the compilation, I get this. > > > > gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o > > nm -n linuxbios | sort > linuxbios.map > > objcopy -O binary linuxbios linuxbios.strip > > gcc -o buildrom /home/randall/src/linuxbios/freebios2/util/buildrom/buildrom.c > > ./buildrom linuxbios.strip linuxbios.rom ../../../../tg3--ide_disk.zelf > > 0x1 0x2 > > ../../../../tg3--ide_disk.zelf: No such file or directory > > make[1]: *** [linuxbios.rom] Error 2 > > make[1]: Leaving directory > > `/home/randall/src/linuxbios/freebios2/targets/via/epia/epia/fallback' > > make: *** [fallback-rom] Error 1 > > > > tg3--ide-disk.zelf was never built. Is this missing: > > > > from the buildrom output, tg3--ide-disk.zelf is supposed to be the payload. > > I'll send you that payload under a seperate note. > > but it's only useful for loading an elfimage from an ide-flash. I have no > via-rhine etherboot, which is what you need. > > ron > > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios > ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
ron minnich <[EMAIL PROTECTED]> writes: > OK, for VGA, here we go again. > > Here is my plan. > > I will combine vgabios + idt into one file, put it in pc80, make it a > standard device, have it turn itself on with the standard static > configuration techniques, and we'll have vga. > > The understanding here is that this is code that we hope to deprecate in > favor of the emulation that Stefan is working on. But the pressure to do > something in the short term is getting irresistable, this code works, so I > think we take a short term focus to help the user community. > > I'll try to get this in this week. Ok. That sounds like a plan. As long as it does not require special cases in the configuration it should impose no extra support burden. Adam Agnew has pointed me at a frame buffer driver for the ATI Rage XL that should be capable of initializing the card without bios support. If that works we have an even better solution. So that would make an even more elegant driver for the cards that have on board VGA support. And given that the ATI Rage XL is the most common chip I have seen on motherboards with LinuxBIOS it should be a big help. Eric ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
On Wed, 1 Oct 2003, Andrew Ip wrote: > > > ZKERNEL_START is not really needed any more. I don't think. Am I wrong? > Is it changed to CONFIG_ROM_STREAM_START? Think so. Those names are terrible (we need to fix them) but I think that's it. yes. You may need to get the latest cvs ... I have a few important fixes in there. I just put them in tonight, not tested (I can't) but should work. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
OK, for VGA, here we go again. I just found out that a well-known linuxbios company ships their boards in some cases with the old bios in it because the field engineers want vga. Here is my plan. I will combine vgabios + idt into one file, put it in pc80, make it a standard device, have it turn itself on with the standard static configuration techniques, and we'll have vga. The understanding here is that this is code that we hope to deprecate in favor of the emulation that Stefan is working on. But the pressure to do something in the short term is getting irresistable, this code works, so I think we take a short term focus to help the user community. I'll try to get this in this week. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
don't commit! I fixed that for you already. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
Changes: new epia target for 512k: targets/via/epia/Config.512kflash.lb epia defaults to 256k flash buildtarget now takes either a directory, and uses directory/Config.lb, or takes a file e.g. buildtarget via/epia will use via/epia/Config.lb, and buildtarget via/epia/Config.512kflash.lb will use that file. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
Hi Ron, Are you able to use etherboot as payload? > ZKERNEL_START is not really needed any more. I don't think. Am I wrong? Is it changed to CONFIG_ROM_STREAM_START? > send me the tweaks, although they should not have been needed. It is just the size. I can commit it now. We can say LinuxBIOS is a 24x7 project. :) -Andrew Here is the part of the log. Copying IRQ routing tables to 0xf...done. Verifing priq routing tables copy at 0xf...failed Wrote linuxbios table at: 0500 - 0aec checksum 7d48 Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3 23:stream_init() - rom_stream: 0xfffe - 0xfffe Found ELF candiate at offset 0 header_offset is 0 Try to load at offset 0x0 malloc Enter, size 32, free_mem_ptr 0001432c malloc 0x0001432c New segment addr 0x40 size 0xaec0 offset 0x60 filesize 0x6fa1 (cleaned up) New segment addr 0x40 size 0xaec0 offset 0x60 filesize 0x6fa1 lb: [0x4000, 0x00017b4c) Loading Segment: addr: 0x0040 memsz: 0xaec0 filesz: 0x01[ 0x0040, 00406fa1, 0x0040aec0) <- 0060 Clearing Segment: addr: 0x00406fa1 memsz: 0x3f1f Loaded segments verified segments closed down stream Jumping to boot code at 0x40 entry= 0x0040 lb_start = 0x4000 lb_size = 0x00013b4c adjust = 0x03fe84b4 buffer = 0x03fd8968 elf_boot_notes = 0xd400 adjusted_boot_notes = 0x03ff58b4 ROM segment 0x length 0x reloc 0x Etherboot 5.0.6 (GPL) ELF for [VIA 86C100] Boot from (N)etwork or from (L)ocal? clocks_per_tick = 504240 N I am now initializing the ide system On Tue, Sep 30, 2003 at 11:36:25PM -0600, ron minnich wrote: > On Wed, 1 Oct 2003, Andrew Ip wrote: > > > I'm able to build and run LinuxBIOS on EPIA with some treaking on Config.lb. > > > > > However, it fails to jump to payload(etherboot). I suspect LinuxBIOS is > > jumping to a wrong location. Is it possible to set ZKERNEL_START in v2? > > ZKERNEL_START is not really needed any more. I don't think. Am I wrong? > > > BTW, ROM_SIZE for default setup should be 262144 instead of 512k, since > > most EPIA doesn't come with 512k flash. > > OK, I will try to commit that tomorrow. > > please send me output. > > ron > > -- Andrew Ip Email: [EMAIL PROTECTED] Tel:(852) 2542 2046 Fax:(852) 2542 2036 Mobile: (852) 9201 9866 Cwlinux Limited Unit 202B 2/F Lai Cheong Factory Building, 479-479A Castle Peak Road, Lai Chi Kok, Kowloon, Hong Kong. For public pgp key, please obtain it from http://www.keyserver.net/en. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
On Wed, 1 Oct 2003, Andrew Ip wrote: > I'm able to build and run LinuxBIOS on EPIA with some treaking on Config.lb. send me the tweaks, although they should not have been needed. > However, it fails to jump to payload(etherboot). I suspect LinuxBIOS is > jumping to a wrong location. Is it possible to set ZKERNEL_START in v2? ZKERNEL_START is not really needed any more. I don't think. Am I wrong? > BTW, ROM_SIZE for default setup should be 262144 instead of 512k, since > most EPIA doesn't come with 512k flash. OK, I will try to commit that tomorrow. please send me output. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA
Hi Ron, I'm able to build and run LinuxBIOS on EPIA with some treaking on Config.lb. However, it fails to jump to payload(etherboot). I suspect LinuxBIOS is jumping to a wrong location. Is it possible to set ZKERNEL_START in v2? BTW, ROM_SIZE for default setup should be 262144 instead of 512k, since most EPIA doesn't come with 512k flash. -Andrew On Tue, Sep 30, 2003 at 08:08:09PM -0600, ron minnich wrote: > > OK, I've committed code that turns on shadow dram in F segment, so PIRQ > will work; also committed what should be working SMBUS code in > vt8231_early_smbus.c; now the fun begins. I could use advice on: > - what SMBUS bytes we need to care about > - what we should program the north with using those bytes. > - how to do it. > > Which is to say, I think I know, but let's get this done in a speedy > fashion. Momentum is on our side here. > > The EPIA will be a good demo platform. > > Why this sudden burst of EPIA work from me? Two reasons: > - I want to encourage people to look at V2, so we need a demo system > less complex than the K8 systems. > - We are teaching a tutorial on linuxbios, bproc, etc. and will be > doing it hands-on with a roomful of EPIAs, 2 or 3 per tutorial > attendee. See: http://lacsi.lanl.gov/symposium/agenda.shtml > Come if you want. You can see how we build clusters that boot in > seconds. The software we're showing is the same stuff that is running > on our 1024-node Pink cluster, and will run on our 1408-node K8 > cluster. > > ron > > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios -- Andrew Ip Email: [EMAIL PROTECTED] Tel:(852) 2542 2046 Fax:(852) 2542 2036 Mobile: (852) 9201 9866 Cwlinux Limited Unit 202B 2/F Lai Cheong Factory Building, 479-479A Castle Peak Road, Lai Chi Kok, Kowloon, Hong Kong. For public pgp key, please obtain it from http://www.keyserver.net/en. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA Build Errors
On Tue, 30 Sep 2003, Randall H. Craig wrote: > At the end of the compilation, I get this. > > gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o > nm -n linuxbios | sort > linuxbios.map > objcopy -O binary linuxbios linuxbios.strip > gcc -o buildrom /home/randall/src/linuxbios/freebios2/util/buildrom/buildrom.c > ./buildrom linuxbios.strip linuxbios.rom ../../../../tg3--ide_disk.zelf > 0x1 0x2 > ../../../../tg3--ide_disk.zelf: No such file or directory > make[1]: *** [linuxbios.rom] Error 2 > make[1]: Leaving directory > `/home/randall/src/linuxbios/freebios2/targets/via/epia/epia/fallback' > make: *** [fallback-rom] Error 1 > > tg3--ide-disk.zelf was never built. Is this missing: > > from the buildrom output, tg3--ide-disk.zelf is supposed to be the payload. I'll send you that payload under a seperate note. but it's only useful for loading an elfimage from an ide-flash. I have no via-rhine etherboot, which is what you need. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: V2 VIA EPIA Build Errors
On Tue September 30 2003 8:52 pm, Randall H. Craig wrote: > > tg3--ide-disk.zelf was never built. Is this missing: > > from the buildrom output, tg3--ide-disk.zelf is supposed to be the payload. > > Any ideas? I am guessing that this is an etherboot image. What is the pci.ids for the ethernet device? Cheers, Randall ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 VIA EPIA Build Errors
At the end of the compilation, I get this. gcc -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o nm -n linuxbios | sort > linuxbios.map objcopy -O binary linuxbios linuxbios.strip gcc -o buildrom /home/randall/src/linuxbios/freebios2/util/buildrom/buildrom.c ./buildrom linuxbios.strip linuxbios.rom ../../../../tg3--ide_disk.zelf 0x1 0x2 ../../../../tg3--ide_disk.zelf: No such file or directory make[1]: *** [linuxbios.rom] Error 2 make[1]: Leaving directory `/home/randall/src/linuxbios/freebios2/targets/via/epia/epia/fallback' make: *** [fallback-rom] Error 1 tg3--ide-disk.zelf was never built. Is this missing: from the buildrom output, tg3--ide-disk.zelf is supposed to be the payload. Any ideas? ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 VIA EPIA
OK, I've committed code that turns on shadow dram in F segment, so PIRQ will work; also committed what should be working SMBUS code in vt8231_early_smbus.c; now the fun begins. I could use advice on: - what SMBUS bytes we need to care about - what we should program the north with using those bytes. - how to do it. Which is to say, I think I know, but let's get this done in a speedy fashion. Momentum is on our side here. The EPIA will be a good demo platform. Why this sudden burst of EPIA work from me? Two reasons: - I want to encourage people to look at V2, so we need a demo system less complex than the K8 systems. - We are teaching a tutorial on linuxbios, bproc, etc. and will be doing it hands-on with a roomful of EPIAs, 2 or 3 per tutorial attendee. See: http://lacsi.lanl.gov/symposium/agenda.shtml Come if you want. You can see how we build clusters that boot in seconds. The software we're showing is the same stuff that is running on our 1024-node Pink cluster, and will run on our 1408-node K8 cluster. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 via/epia
I think I've got the last kinks out on 8601; we'll find out monday. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 via epia
Closer. I'm getting through all of the 8601 setup. But the values are bogus: Good VIA! 00: 06 11 01 06 06 00 90 a2 05 00 00 06 00 40 00 00 10: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: ac 08 80 00 00 00 20 20 80 00 10 20 20 20 20 20 60: 3f ff ff f0 e4 e4 e4 00 42 ac 65 0d 08 7f 00 00 70: c0 88 ec 0c 0e 81 52 00 01 f0 00 00 00 00 00 00 80: 00 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 02 00 20 00 03 02 00 07 00 00 00 00 08 02 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 01 01 00 42 00 b0 00 00 00 00 Bad VIA! Bad! Bad doggy! 00:06 11 01 06 06 00 90 22 05 00 00 06 00 00 00 00 10:08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30:00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50:ac 08 80 00 00 00 ff ff 00 00 ff ff ff ff ff ff 60:3f 00 00 00 e4 e4 e4 00 42 ac 65 0d 08 7f 00 00 70:00 00 00 00 00 00 00 00 01 f0 00 00 00 00 00 00 80:00 c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0:02 00 20 00 03 02 00 07 00 00 00 00 08 02 00 00 b0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0:00 00 00 00 00 00 01 01 00 00 00 00 00 00 00 00 ah well. I can ship my tree to those of you who want it again. We're working on a solution to the CVS problem, and unlike the sourceforge solutions, we think this one will actually work. So hang in there, we hope next week. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 via/epia: stuck on north bridge.
OK, here is where I am.
Here is the start of the key function
in src/northbridge/via/vt8601/raminit.c
static void sdram_set_registers(const struct mem_controller *ctrl) {
static const uint16_t raminit_ma_reg_table[] = {
/* Values for MA type register to try */
0x, 0x8088, 0xe0ee,
0x // end mark
};
device_t north = 0;
uint8_t c, r;
print_err("vt8601 init starting\n");
north = pci_locate_device(PCI_ID(0x1106, 0x8601), 0);
print_err_hex32(north);
print_err(" is the north\n");
print_err_hex16(pci_read_config16(north, 0));
print_err(" ");
print_err_hex16(pci_read_config16(north, 2));
print_err("\r\n");
// memory clk enable. We are not using ECC
pci_write_config8(north,0x78, 0x01);
print_err_hex8(pci_read_config8(north, 0x78));
.
.
.
Here's what is going wrong.
LinuxBIOS-1.1.4.0Fallback Fri Sep 26 16:44:17 MDT 2003 starting...
SMBus controller enabled
vt8601 init starting
0800 is the north
1106 8601
00
That 00 is the result of reading register 78. Note that I tried to set it
to 1.
Somehow, none of my config writes to any register are working. Not one.
The reads read back fine. That 1106/8601 you see is the result of a config
read from the north bridge. But the writes all fail.
Any idea why this would be? Seems like something is locked somehow. I've
looked at the assembly code and it actually looks ok. This is pretty odd.
The sequence of writes is taken directly from the V1 code.
here's a dump of the north bridge after ALL the writes have been tried.
00:06 11 01 86 07 00 30 02 00 00 04 06 00 00 01 00
10:00 00 00 00 00 00 00 00 00 00 00 00 f0 00 00 00
20:f0 ff 00 00 f0 ff 00 00 00 00 00 00 00 00 00 00
30:00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00
40:00 00 00 22 00 00 00 00 00 00 00 00 00 00 00 00
50:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80:01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
90:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
One thing I definitely don't understand: why is the north 0800? I
would have expected it to be 0. But it works: reads from 'north' return
sensible values. Still ...
thanks
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
V2 VIA EPIA output
here is what I get: 0 LinuxBIOS-1.1.4.0Fallback Fri Sep 26 16:04:07 MDT 2003 starting... SMBus controller enabled vt8601 init starting 0800 is the north vt8601 done LinuxBIOS-1.1.4.0Fallback Fri Sep 26 16:04:07 MDT 2003 starting... Copying LinuxBIOS to ram. Jumping to LinuxBIOS. That first '0' is just the early setup code for the southbridge serial. Then you can see the smbus controller, then the various 8601 gyrations (which don't actually do any good, it seems :0) ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
