coreboot September 2007

coreboot@coreboot.org

81 participants
367 discussions

[LinuxBIOS] MSI MS-6337 (i815 based)
by Jouni Mettälä 17 Sep '07

17 Sep '07

I tried to flash. MS-6337 with recently added MS-6178. It was needed to put WP# and TBL# pins to high but since another chip is in use it is ok. With filo as payload, post card gave 10 ... pause... 80, f8, fe ..short pause and ff. (+ some other codes between them) So at least ram is ok I think. With very small kernel as payload post card gave just ff. I didn't do any modifications to MS6178. Probably some is needed. Any suggestions?

3 2

[LinuxBIOS] r2780 - trunk/util/superiotool
by svn＠openbios.org 17 Sep '07

17 Sep '07

Author: uwe Date: 2007-09-18 02:01:27 +0200 (Tue, 18 Sep 2007) New Revision: 2780 Added: trunk/util/superiotool/README Log: Add a README for superiotool (trivial). Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Added: trunk/util/superiotool/README =================================================================== --- trunk/util/superiotool/README (rev 0) +++ trunk/util/superiotool/README 2007-09-18 00:01:27 UTC (rev 2780) @@ -0,0 +1,61 @@ +------------------------------------------------------------------------------- +Superiotool README +------------------------------------------------------------------------------- + +Superiotool is a user-space utility which can + + - detect which Super I/O chip is soldered onto your mainboard, + + - at which configuration port it's located (usually 0x2e or 0x4e), and + + - dump all register contents of the Super I/O chip, together with the + default values as per datasheet (to make comparing the values easy). + +It is mainly used for LinuxBIOS development purposes (see linuxbios.org +for details on LinuxBIOS), but it may also be useful for other things. + + +Installation +------------ + + $ svn co svn://linuxbios.org/repos/trunk/util/superiotool + + $ make + + $ sudo make install + + +Usage +----- + + $ superiotool + +Currently the tool will automatically try to detect which Super I/O you +have, and also dump the register contents. + + +Supported Super I/O Chips +------------------------- + +Please see http://linuxbios.org/Superiotool#Supported_devices. + + +Website and Mailing List +------------------------ + +The main website is http://linuxbios.org/Superiotool. + +For additional information, patches, and discussions, please join the +LinuxBIOS mailing list at http://linuxbios.org/Mailinglist, where most +superiotool developers are subscribed. + + +Copyright and License +--------------------- + +Superiotool is copyrighted by a number of individual developers. Please +refer to the respective source code files for details. + +It is licensed under the terms of the GNU General Public License (GPL), +either version 2 of the License, or (at your option) any later version. +

1 0

Re: [LinuxBIOS] [RFC] Initial attempt at supporting MSI K9N Neo ( MS-7260)
by Uwe Hermann 17 Sep '07

17 Sep '07

Hi Marc, (CC to list) On Thu, Sep 13, 2007 at 06:33:17PM -0600, Marc Jones wrote: > Uwe Hermann wrote: >> Hi, >> >> here's my first try with the K9N. It took me a while to figure out how >> to make serial work (the Super I/O is at 0x4e on this board, and you >> need a small hack to switch to 24MHz, see patch), but that part >> works fine now. >> >> > 0x4e is not unusual for the SIO decode. Yep, but it seems that's what the BIOS does. I verified with superiotool (I added W83627EHG support, patch pending). > You should check and see if the > pcbios sets 24Mhz or 48Mhz. I would set it up the same as they do. There > should be a bit for half clock divisor on the serial port instead of > changing the clock. Ah, yes, CR 0xF0 (page 102 in the datasheet) looks like the register I need. I'll try that. However, the BIOS indeed sets the clock speed to 24MHz (CR 0x24, bit 6 was set to zero when I checked). > I suspect that this is the SPD address is different. How do I find out the correct one? i2cdetect/i2cdump? Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

2 2

[LinuxBIOS] #86: filo sata boot delay patch
by LinuxBIOS 17 Sep '07

17 Sep '07

#86: filo sata boot delay patch --------------------------------+------------------------------------------- Reporter: ward | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: code | Version: v2 Keywords: | Dependencies: Patchstatus: patch needs work | --------------------------------+------------------------------------------- I've been using the attached patch to filo on machines that need to boot from SATA disks. It's only necessary on cold boot, as the problem is the physical spin-up of the drives. The patch is very crude, and there have been reports that a shorter delay is sufficient. I have not had time to test a shorter delay, and I suspect that the length of the delay might depend somewhat on the drives used. Ideally there would be a way for FILO to see if the boot was cold or warm so that it could apply the delay in the cold-boot case only. Also, this delay should be configurable in FILO's Config file. -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/86> LinuxBIOS <http://www.linuxbios.org/>

1 2

Re: [LinuxBIOS] #65: Unify SuperIO code?
by LinuxBIOS 17 Sep '07

17 Sep '07

#65: Unify SuperIO code? ----------------------------+----------------------------------------------- Reporter: stepan | Owner: somebody Type: enhancement | Status: new Priority: minor | Milestone: Cosmetic fixes Component: code | Version: v2 Resolution: | Keywords: Dependencies: | Patchstatus: there is no patch ----------------------------+----------------------------------------------- Comment (by uwe): Yes, the Super I/O code should definately be unified. Ideally one "driver" per Super I/O vendor should handle all the various chips of that vendor. An example of how this can work is the 'smscsuperio' driver in v2, which should support almost all recent SMSC Super I/O chips. At least for v3 we should only accept this kind of generalized Super I/O drivers in the repository. -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/65#comment:1> LinuxBIOS <http://www.linuxbios.org/>

1 0

[LinuxBIOS] ADLO on a real machine
by Myles Watson 17 Sep '07

17 Sep '07

With some fiddling I booted into the Windows install CD and installed Windows XP on a hard drive. It took fiddling because the BIOS is so old that it doesn't conform to the ATA-3 specifications. I haven't been able to boot using a hard drive from ADLO yet because it doesn't recognize my hard drives (same age related problems of the Bochs BIOS.) I've looked at porting the FILO drivers into the Bochs BIOS, but it doesn't appear trivial. Any questions, suggestions, or comments besides "Why would you want to do this?" Thanks, Myles

4 7

Re: [LinuxBIOS] [PATCH] Reimplementation/fixing of CS5530/CS5530A southbridge code
by Jonathan Sturges 17 Sep '07

17 Sep '07

Thanks Uwe, As you might've guessed from my other mails about IRQ_SLOT_COUNT, the CS5530 code seems to work fine as of r2776. In particular, the IDE interfaces are getting initialized properly. thanks! Jonathan ----- Original Message ---- From: Uwe Hermann <uwe(a)hermann-uwe.de> To: Jonathan Sturges <jonathansturges(a)yahoo.com> Cc: linuxbios(a)linuxbios.org Sent: Thursday, September 13, 2007 8:14:14 PM Subject: Re: [LinuxBIOS] [PATCH] Reimplementation/fixing of CS5530/CS5530A southbridge code On Wed, Aug 29, 2007 at 08:16:52PM -0700, Jonathan Sturges wrote: > I'm still having problems. The ideX_enable register values are within the "chip southbridge/amd/cs5530" context in my Config.lb, which matches the ASI mb-5blmp you cited. > This is grasping at straws, but my Config.lb inconsistently uses tabs and spaces... any issues there, beyond aesthetics? No, whitespace should not matter there. > Anyway, FWIW, I attached the Config.lb I'm working from. Any hints appreciated. Please retry with the latest svn revision, I just committed a rewrite of the CS5530 code. I verified that it works on the ASI MB-5BLMP. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org ____________________________________________________________________________________ Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469

1 0

Re: [LinuxBIOS] Tyan S2885 interrupt problem...
by Richard Wei 17 Sep '07

17 Sep '07

Ha~ it works now after changed to 64bit kernel. Thanks ^_^ But still wondering why it only support 64bit kernel. What should we do to make the 32bit kernel support possible? ----- Original Message ---- From: yhlu <yinghailu(a)gmail.com> To: Richard Wei <outlander_wei(a)yahoo.com> Cc: linuxbios(a)linuxbios.org Sent: Thursday, September 13, 2007 12:33:49 AM Subject: Re: [LinuxBIOS] Tyan S2885 interrupt problem... please use 64 bit kernel... YH -- linuxbios mailing list linuxbios(a)linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios ____________________________________________________________________________________ Check out the hottest 2008 models today at Yahoo! Autos. http://autos.yahoo.com/new_cars.html

2 1

[LinuxBIOS] buildrom
by Ward Vandewege 17 Sep '07

17 Sep '07

I've been working on adding support for the m57sli to buildrom. I'm almost there - particularly I've got filo and linux-as-a-bootloader (lab) going. Lab has a stripped down 2.6.22.2 kernel and a tiny initrd in a 1MB rom chip (25K to spare :), configured to kexec another kernel from disk. I need to do a bit more testing but I intend to have filo and lab fully functional, and hopefully I'll also have time to look at other payloads. Now; before I post my patches to the list for review, I'd like to know what the current thinking is on the future of buildrom. There are a couple of issues with buildrom as it stands today: a) it's v2 only b) there is no standardized way to use a different initrd 'skeleton' for a specific board c) there is no standardized way to have different LinuxBIOS Config.lb files for a particular board, based on the payload It looks like the kconfig setup for v3 will take over much (everything?) of what buildrom does now. If that is true, I think I might just add a few patches to fix b) and c) before I submit the m57sli patches. Thoughts? Does that sound reasonable? Thanks, Ward. -- Ward Vandewege <ward(a)fsf.org> Free Software Foundation - Senior System Administrator

7 10

[LinuxBIOS] r2779 build service
by LinuxBIOS information 16 Sep '07

16 Sep '07

Dear LinuxBIOS readers! This is the automated build check service of LinuxBIOS. The developer "uwe" checked in revision 2779 to the LinuxBIOS source repository and caused the following changes: Change Log: Split out a dump_superio() function from ite.c, and make it slightly more generic, so that we can use it for other Super I/Os, too. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Build Log: Compilation of arima:hdama is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=hdama&vendor=… Compilation of ibm:e325 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=e325&vendor=i… Compilation of ibm:e326 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=e326&vendor=i… Compilation of iei:juki-511p is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=juki-511p&ven… Compilation of iwill:dk8s2 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=dk8s2&vendor=… Compilation of iwill:dk8x is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=dk8x&vendor=i… Compilation of newisys:khepri is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=2779&device=khepri&vendor… If something broke during this checkin please be a pain in uwe's neck until the issue is fixed. If this issue is not fixed within 24h the revision should be backed out. Best regards, LinuxBIOS automatic build system

1 0

← Newer
1
...
17
18
19
20
21
22
23
...
37
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot September 2007