Re: [coreboot] [PATCH] ASUS P2B-LS support, RAM detection for 440BX, add Slot 1 CPU, Microcode for Intel Tualatin CPUs
Hi Keith, On Tue, Mar 02, 2010 at 11:19:24PM -0500, Keith Hui wrote: > This thing is now ready for more exposure. Scratch my previous "patch" - > this is my first real deal. > > - Adds Asus P2B-LS mainboard > - Adds RAM detection for i440bx (based on i82830 code). We're no longer hard > coded for 64MB on one row! > - Adds a proper Slot 1 cpu under src/cpu/intel/slot_1. It's a stub copied > from slot_2 but addresses a few FIXMEs. My P2B-LS code refers to this. > - Adds microcode for Intel Tualatin CPUs, cpuid 6B1 and 6B4.* Actually > loading them is pending. > > Signed-off-by: Keith Hui Great stuff, thanks a lot! I'll review and/or test the individual pieces one by one and commit them as I progress. (small note for the next patch: please split up the stuff in multiple smaller, independent patches, that makes it easier to review and test; no need to re-send this patch though). Uwe. -- http://www.hermann-uwe.de | http://www.randomprojects.org http://www.crazy-hacks.org | http://www.unmaintained-free-software.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Details for choice of motherboard
On Wed, Mar 3, 2010 at 7:02 AM, anand bhagwantrao wrote: > Hello frnds.. > > I want to have coreboot in my motherboard. > pls let me know the same specification motherboard as > > Intel BOXDG43NB LGA 775 Intel G43 ATX Intel Motherboard > > but apart from Intel. > > > Thank you all.. > > > -- > coreboot mailing list: coreboot@coreboot.org > http://www.coreboot.org/mailman/listinfo/coreboot > Hello! More of us will be able to give much more correct answers, but I believe that particular board is not yet supported. There is a place on the Coreboot site which describes what is, and what is not. How new for example is that particular board, do you have the complete documentation on it, and such like. If you already have Linux running on it, we'd need to see the output from a command called lspci, and it would need to be run as lspci -v, followed by running the utilities that further explain what else is needed. Right now I'm just writing as the first responder here, more of the members are more conversant then I with the particulars behind what to do, and what else gets done. - Gregg C Levine gregg.drw...@gmail.com "This signature fought the Time Wars, time and again." -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] HELP: Porting i830 RAM init to 440BX, now it won't compile
Keith, Nice job! I will have to disagree with you about the hockey results though :-) ron -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] YABEL debug broken again
> >> > It compiles for me with 5132, but not 5135. You could look at the > >> changes: > >> > http://tracker.coreboot.org/trac/coreboot/changeset/5135 > >> > > > Yes. It compiles without debug, right? > > > Yes. > > > If I were you I'd comment out the debugging statements that are breaking > > for > > you, unless you are trying to debug the vbe code. It looks like > > framebuffer_address and friends were commented out in 5135. > > > Well I was kind of looking forward to the vbe debug. Hmm. > You'd still get some information from the debugging statements that work, but the statements referencing undefined variables are not likely to give you any good information. Patrick and Stefan: Any hints for Joe? Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] YABEL debug broken again
On Wed, 3 Mar 2010 06:51:34 -0700, "Myles Watson" wrote: > On Tue, 2 Mar 2010 16:14:17 -0700, Myles Watson wrote: >> >> > util/x86emu/yabel/vbe.c:647: error: 'vbe_mode_info_t' has no member >> >> > named 'framebuffer_address' >> >> > make: *** [util/x86emu/yabel/vbe.o] Error 1 >> >> > >> >> > >> >> Appears to be something wrong with the union in structure >> vbe_mode_info_t >> >> in vbe.c. It points to another structure vesa_mode_info_t, but I am > not >> >> sure why it is not working? >> >> >> > It compiles for me with 5132, but not 5135. You could look at the >> changes: >> > http://tracker.coreboot.org/trac/coreboot/changeset/5135 >> > >> Yes it appears that union inside of the vbe_mode_info_t structure is new. >> Is it even ok to put a union inside of a structure? > Yes. It compiles without debug, right? > Yes. > If I were you I'd comment out the debugging statements that are breaking > for > you, unless you are trying to debug the vbe code. It looks like > framebuffer_address and friends were commented out in 5135. > Well I was kind of looking forward to the vbe debug. Hmm. -- Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Re unsuported Motherboard
Myles Watson escribió: >> For programmer it would probably be simplest to use another >> mainboard which is compatible with flashrom. >> >> Can we remove BIOS with the machine turned on? Meaning: We boot with the >> good one, we remove it, we insert the second machine chip and flash it. >> Does it work? >> > Yes. This link has pictures of the pushpin method. It works very well for > PLCC, which are pictured. > > http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools > > The downside is that it will take a long time to try a new design, since you > will have to boot the machine to Linux, flash the new design, and reboot. > Having another machine that is already up will save a lot of time. > I'm using pushpins and a separate machine for reprogramming the chips (PLCC) works awesome no problem so far and I'm sure I did reprogram chips on this board for like 100 times. > >> About the compatibility, I have a motherboard with a socket that has a >> award BIOS, is the chip/socket the same for AMI? Are they compatible? >> > Any BIOS vendor could use any type of chip. Unfortunately, that won't help > you figure it out. > > Thanks, > Myles > > > Have you tried flashrom to see which chip is installed? Bye, Knut Kujat. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Re unsuported Motherboard
> For programmer it would probably be simplest to use another > mainboard which is compatible with flashrom. > > Can we remove BIOS with the machine turned on? Meaning: We boot with the > good one, we remove it, we insert the second machine chip and flash it. > Does it work? Yes. This link has pictures of the pushpin method. It works very well for PLCC, which are pictured. http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools The downside is that it will take a long time to try a new design, since you will have to boot the machine to Linux, flash the new design, and reboot. Having another machine that is already up will save a lot of time. > About the compatibility, I have a motherboard with a socket that has a > award BIOS, is the chip/socket the same for AMI? Are they compatible? Any BIOS vendor could use any type of chip. Unfortunately, that won't help you figure it out. Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Re unsuported Motherboard
Am Mittwoch, den 03.03.2010, 15:00 +0100 schrieb Joao Mamede: […] > Can we remove BIOS with the machine turned on? Meaning: We boot with the > good one, we remove it, we insert the second machine chip and flash it. > Does it work? As far as I know, yes! You can for example use push pins for easier handling[2]. > About the compatibility, I have a motherboard with a socket that has a > award BIOS, is the chip/socket the same for AMI? Are they compatible? As far as I know the BIOS manufacturer has nothing to do with it. It really just depends on the socket and if the flash chip is supported on that other system/motherboard. Thanks, Paul [1] http://www.coreboot.org/Developer_Manual/Tools signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Re unsuported Motherboard
Joao Mamede wrote: > a socket to plug in a BIOS and buy a BIOS external writer. Can I > have recommendations on where to buy? Peter Stuge wrote: What's your budget? farnell.com should have PLCC sockets and maybe even flash chips. bios-repair.co.uk has flash chips, and maybe PLCC sockets. For programmer it would probably be simplest to use another mainboard which is compatible with flashrom. Can we remove BIOS with the machine turned on? Meaning: We boot with the good one, we remove it, we insert the second machine chip and flash it. Does it work? About the compatibility, I have a motherboard with a socket that has a award BIOS, is the chip/socket the same for AMI? Are they compatible? I'm sorry for the "noob" questions, but I don't really know much about BIOS. Check which flash chip is in the system, if it's an SPI chip then your best bet is to order the sockets from bios-repair.co.uk instead, I haven't seen SO-8 sockets easily available anywhere else. //Peter -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] YABEL debug broken again
On Tue, 2 Mar 2010 16:14:17 -0700, Myles Watson wrote: > >> > util/x86emu/yabel/vbe.c:647: error: 'vbe_mode_info_t' has no member > >> > named 'framebuffer_address' > >> > make: *** [util/x86emu/yabel/vbe.o] Error 1 > >> > > >> > > >> Appears to be something wrong with the union in structure > vbe_mode_info_t > >> in vbe.c. It points to another structure vesa_mode_info_t, but I am not > >> sure why it is not working? > >> > > It compiles for me with 5132, but not 5135. You could look at the > changes: > > http://tracker.coreboot.org/trac/coreboot/changeset/5135 > > > Yes it appears that union inside of the vbe_mode_info_t structure is new. > Is it even ok to put a union inside of a structure? Yes. It compiles without debug, right? If I were you I'd comment out the debugging statements that are breaking for you, unless you are trying to debug the vbe code. It looks like framebuffer_address and friends were commented out in 5135. Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] Details for choice of motherboard
Hello frnds.. I want to have coreboot in my motherboard. pls let me know the same specification motherboard as Intel BOXDG43NB LGA 775 Intel G43 ATX Intel Motherboard but apart from Intel. Thank you all.. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
