coreboot February 2008

coreboot@coreboot.org

77 participants
422 discussions

r113 - in buildrom-devel: . packages/busybox packages/coreboot-v2 packages/filo packages/kernel packages/uclibc
by svn＠coreboot.org 11 Feb '08

11 Feb '08

Author: ward Date: 2008-02-11 21:36:54 +0100 (Mon, 11 Feb 2008) New Revision: 113 Modified: buildrom-devel/Config.in buildrom-devel/packages/busybox/busybox.mk buildrom-devel/packages/coreboot-v2/coreboot.inc buildrom-devel/packages/filo/filo.mk buildrom-devel/packages/kernel/kernel.inc buildrom-devel/packages/uclibc/uclibc.mk Log: This patch aims to store as much information about the build environment as possible during the building of a coreboot image, in order to make it easy to recreate coreboot images at a later point in time. It logs a number of things in the new deploy/config directory: * the buildrom .config file * config files used for compiling various packages (filo, kernel, uclibc, busybox) * the output of 'svn diff', 'svn info', 'svn status' * the output of 'uname -a' * a copy of /etc/lsb-release, /etc/debian-version, /etc/redhat-version if they exist * the output of '$(CC) --version', '$(MAKE) --version', '$(LD) --version' The logging of SVN output can be disabled in kconfig because it means internet access must be available on the machine used for building the coreboot image. This setting defaults to on because we already try to download a lot of code if we don't have the necessary source packages in sources/. Signed-off-by: Ward Vandewege <ward(a)gnu.org> Acked-by: Jordan Crouse <jordan.crouse(a)amd.com> Modified: buildrom-devel/Config.in =================================================================== --- buildrom-devel/Config.in 2008-02-11 17:29:40 UTC (rev 112) +++ buildrom-devel/Config.in 2008-02-11 20:36:54 UTC (rev 113) @@ -32,6 +32,16 @@ See the entire build output on stdout. Otherwise, it will be saved off in a series of logs +config STORE_SVN_INFO + bool "Store svn tree information in deployment directory." + default y + help + Store the output of 'svn diff', 'svn status' and 'svn info' in the + deploy/config/svn/ directory. This means the machine used to build + the coreboot image will need to have internet access during the build. + + If you are not sure, say yes. + config MAKE_JOBS int "Number of make jobs to run simultaneously (experimental)" default 1 Modified: buildrom-devel/packages/busybox/busybox.mk =================================================================== --- buildrom-devel/packages/busybox/busybox.mk 2008-02-11 17:29:40 UTC (rev 112) +++ buildrom-devel/packages/busybox/busybox.mk 2008-02-11 20:36:54 UTC (rev 113) @@ -51,7 +51,10 @@ export LDFLAGS="$(LDFLAGS_orig)";\ $(MAKE) -C $(BUSYBOX_SRC_DIR) VERBOSE=y \ LIBRARIES="$(LIBS)" all > $(BUSYBOX_BUILD_LOG) 2>&1) + @ mkdir -p $(OUTPUT_DIR)/config/busybox + @ cp $(BUSYBOX_SRC_DIR)/.config $(OUTPUT_DIR)/config/busybox/ + $(INITRD_DIR)/bin/busybox: $(BUSYBOX_SRC_DIR)/busybox | $(BUSYBOX_LOG_DIR) @ $(MAKE) -C $(BUSYBOX_SRC_DIR) \ PREFIX=$(INITRD_DIR) install > $(BUSYBOX_INSTALL_LOG) 2>&1 Modified: buildrom-devel/packages/coreboot-v2/coreboot.inc =================================================================== --- buildrom-devel/packages/coreboot-v2/coreboot.inc 2008-02-11 17:29:40 UTC (rev 112) +++ buildrom-devel/packages/coreboot-v2/coreboot.inc 2008-02-11 20:36:54 UTC (rev 113) @@ -81,6 +81,30 @@ @ echo "Building coreboot..." @ (export CPU_OPT="$(STACKPROTECT)"; \ make -C $(CBV2_BUILD_DIR) > $(CBV2_BUILD_LOG) 2>&1) + @ mkdir -p $(OUTPUT_DIR)/config/coreboot-v2/ + @ cp $(CBV2_BUILD_DIR)/../$(CBV2_CONFIG) $(OUTPUT_DIR)/config/coreboot-v2/ + @ cp $(BASE_DIR)/.config $(OUTPUT_DIR)/config/ + @ mkdir -p $(OUTPUT_DIR)/config/system/ + @ uname -a >$(OUTPUT_DIR)/config/system/uname-a + @ if [ -f /etc/lsb-release ]; then \ + cp /etc/lsb-release $(OUTPUT_DIR)/config/system/; \ + fi + @ if [ -f /etc/debian-version ]; then \ + cp /etc/debian-version $(OUTPUT_DIR)/config/system/; \ + fi + @ if [ -f /etc/redhat-version ]; then \ + cp /etc/redhat-version $(OUTPUT_DIR)/config/system/; \ + fi + @ mkdir -p $(OUTPUT_DIR)/config/toolchain/ + @ $(MAKE) --version >$(OUTPUT_DIR)/config/toolchain/$(MAKE)-version + @ $(CC) --version >$(OUTPUT_DIR)/config/toolchain/$(CC)-version + @ $(LD) --version >$(OUTPUT_DIR)/config/toolchain/$(LD)-version +ifeq ($(CONFIG_STORE_SVN_INFO),y) + @ mkdir -p $(OUTPUT_DIR)/config/svn/ + @ svn diff > $(OUTPUT_DIR)/config/svn/svn.diff + @ svn info > $(OUTPUT_DIR)/config/svn/svn.info + @ svn status > $(OUTPUT_DIR)/config/svn/svn.status +endif generic-coreboot-clean: @ echo "Cleaning coreboot..." Modified: buildrom-devel/packages/filo/filo.mk =================================================================== --- buildrom-devel/packages/filo/filo.mk 2008-02-11 17:29:40 UTC (rev 112) +++ buildrom-devel/packages/filo/filo.mk 2008-02-11 20:36:54 UTC (rev 113) @@ -56,6 +56,8 @@ @ echo "Using custom config $(PACKAGE_DIR)/filo/conf/$(FILO_CONFIG)" endif @ make -C $(FILO_SRC_DIR) filo.elf > $(FILO_BUILD_LOG) 2>&1 + @ mkdir -p $(OUTPUT_DIR)/config/filo + @ cp $(FILO_SRC_DIR)/Config $(OUTPUT_DIR)/config/filo/ $(FILO_STAMP_DIR) $(FILO_LOG_DIR): @ mkdir -p $@ Modified: buildrom-devel/packages/kernel/kernel.inc =================================================================== --- buildrom-devel/packages/kernel/kernel.inc 2008-02-11 17:29:40 UTC (rev 112) +++ buildrom-devel/packages/kernel/kernel.inc 2008-02-11 20:36:54 UTC (rev 113) @@ -63,6 +63,8 @@ endif @ $(MAKE) $(PARALLEL_MAKE) -C $(KERNEL_SRC_DIR) ARCH=$(KERNEL_BUILD_ARCH) \ KERNEL_CC="$(CC)" KERNEL_LD="$(LD)" > $(KERNEL_BUILD_LOG) 2>&1 + @ mkdir -p $(OUTPUT_DIR)/config/kernel + @ cp $(KERNEL_SRC_DIR)/.config $(OUTPUT_DIR)/config/kernel/ $(OUTPUT_DIR)/bzImage: $(KERNEL_BZIMAGE) @ install -d $(OUTPUT_DIR) Modified: buildrom-devel/packages/uclibc/uclibc.mk =================================================================== --- buildrom-devel/packages/uclibc/uclibc.mk 2008-02-11 17:29:40 UTC (rev 112) +++ buildrom-devel/packages/uclibc/uclibc.mk 2008-02-11 20:36:54 UTC (rev 113) @@ -56,6 +56,8 @@ SHARED_LIB_LOADER_PATH="/lib" \ SHARED_LIB_LOADER_PREFIX="/lib" \ all > $(UCLIBC_BUILD_LOG) 2>&1) + @ mkdir -p $(OUTPUT_DIR)/config/uclibc + @ cp $(UCLIBC_SRC_DIR)/.config $(OUTPUT_DIR)/config/uclibc/ $(STAGING_DIR)/lib/libc.a: $(UCLIBC_SRC_DIR)/lib/libc.a @ $(MAKE) -C $(UCLIBC_SRC_DIR) \

1 0

r112 - buildrom-devel/config/platforms
by svn＠coreboot.org 11 Feb '08

11 Feb '08

Author: ward Date: 2008-02-11 18:29:40 +0100 (Mon, 11 Feb 2008) New Revision: 112 Modified: buildrom-devel/config/platforms/m57sli.conf Log: Bump up coreboot-v2 svn version used for the m57sli to 3096, to make sure that we always use a non-broken Config.lb file. This is a trivial patch. Signed-off-by: Ward Vandewege <ward(a)gnu.org> Acked-by: Ward Vandewege <ward(a)gnu.org> Modified: buildrom-devel/config/platforms/m57sli.conf =================================================================== --- buildrom-devel/config/platforms/m57sli.conf 2008-02-07 21:26:29 UTC (rev 111) +++ buildrom-devel/config/platforms/m57sli.conf 2008-02-11 17:29:40 UTC (rev 112) @@ -41,7 +41,7 @@ CBV2_CONFIG=Config.lb CBV2_PAYLOAD_FILE_EXT=elf CBV2_TDIR=m57sli -CBV2_TAG=3092 +CBV2_TAG=3096 # FILO configuration

1 0

Re: [coreboot] r2 - trunk/openvsa/sysmgr
by Peter Stuge 11 Feb '08

11 Feb '08

On Sat, Feb 09, 2008 at 09:55:32PM +0100, svn(a)coreboot.org wrote: > Author: kilgour > Date: 2008-02-09 21:55:31 +0100 (Sat, 09 Feb 2008) > New Revision: 2 > > Removed: > trunk/openvsa/sysmgr/delme > trunk/openvsa/sysmgr/delme.c > Log: > remove files accidentally added to SVN Should the Signed-off-by: procedure be used also for the openvsa repo? //Peter

4 4

Re: [coreboot] Advantech Product Support - TPC-1261
by Carl-Daniel Hailfinger 11 Feb '08

11 Feb '08

Dear Tomasz, On 11.02.2008 14:57, Tomasz.Malewski wrote: > Currently I think about > > TPC-1261 > http://taiwan.advantech.com.tw/unzipfunc/Unzip/1-1VSUA1/TPC-1261H_DS.pdf > > http://taiwan.advantech.com.tw/unzipfunc/Unzip/1-2JV146/Advantech%20Linux%2… > > Inside are: > IC SMD CS5536AD PBGA 208P AMD > CPU LX800 500MHz BGU 481P ALXD800EEXJ2VD > I think this will be a really nice target. We can support it with coreboot v2 or coreboot v3. Coreboot v3 is still in development, but it is much easier to adapt to a system. Do you want to port coreboot yourself or do you want to hire somebody to do this for you? Regards, Carl-Daniel

1 0

r3101 build service
by coreboot information 11 Feb '08

11 Feb '08

Dear coreboot readers! This is the automated build check service of coreboot. The developer "uwe" checked in revision 3101 to the coreboot source repository and caused the following changes: Change Log: flashrom: further cleanups to enable_flash_cs5536 - Remove the "enable write to flash" message, as the caller appears to already report that. - Move the 'modprobe msr' suggestions to the first lseek64 error handling, as we get an error there already. - Rename a perror string from "read" to "read msr", as we use the latter already in this function for another read. Signed-off-by: Mart Raudsepp <mart.raudsepp(a)artecdesign.ee> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Build Log: Compilation of a-trend:atc-6220 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=atc-6220&vendo… Compilation of abit:be6-ii_v2_0 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=be6-ii_v2_0&ve… Compilation of advantech:pcm-5820 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=pcm-5820&vendo… Compilation of agami:aruma has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=aruma&vendor=a… Compilation of amd:db800 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=db800&vendor=a… Compilation of amd:norwich has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=norwich&vendor… Compilation of amd:rumba has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=rumba&vendor=a… Compilation of amd:serengeti_cheetah has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=serengeti_chee… Compilation of amd:serengeti_cheetah_fam10 is still broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=serengeti_chee… Compilation of arima:hdama has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=hdama&vendor=a… Compilation of artecgroup:dbe61 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=dbe61&vendor=a… Compilation of asi:mb_5blmp has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=mb_5blmp&vendo… Compilation of asus:a8n_e has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=a8n_e&vendor=a… Compilation of asus:a8v-e_se has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=a8v-e_se&vendo… Compilation of asus:mew-am has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=mew-am&vendor=… Compilation of asus:mew-vm has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=mew-vm&vendor=… Compilation of asus:p2b has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=p2b&vendor=asus Compilation of asus:p2b-f has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=p2b-f&vendor=a… Compilation of asus:p3b-f has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=p3b-f&vendor=a… Compilation of axus:tc320 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=tc320&vendor=a… Compilation of azza:pt-6ibd has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=pt-6ibd&vendor… Compilation of bcom:winnet100 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=winnet100&vend… Compilation of biostar:m6tba has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=m6tba&vendor=b… Compilation of broadcom:blast has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=blast&vendor=b… Compilation of compaq:deskpro_en_sff_p600 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=deskpro_en_sff… Compilation of dell:s1850 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s1850&vendor=d… Compilation of digitallogic:adl855pc has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=adl855pc&vendo… Compilation of digitallogic:msm586seg has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=msm586seg&vend… Compilation of digitallogic:msm800sev has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=msm800sev&vend… Compilation of eaglelion:5bcm has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=5bcm&vendor=ea… Compilation of emulation:qemu-x86 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=qemu-x86&vendo… Compilation of gigabyte:ga-6bxc has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ga-6bxc&vendor… Compilation of gigabyte:ga_2761gxdk has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ga_2761gxdk&ve… Compilation of gigabyte:m57sli has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=m57sli&vendor=… Compilation of ibm:e325 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=e325&vendor=ibm Compilation of ibm:e326 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=e326&vendor=ibm Compilation of iei:juki-511p has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=juki-511p&vend… Compilation of iei:nova4899r has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=nova4899r&vend… Compilation of intel:jarrell has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=jarrell&vendor… Compilation of intel:xe7501devkit has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=xe7501devkit&v… Compilation of iwill:dk8_htx has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=dk8_htx&vendor… Compilation of iwill:dk8s2 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=dk8s2&vendor=i… Compilation of iwill:dk8x has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=dk8x&vendor=iw… Compilation of lippert:frontrunner has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=frontrunner&ve… Compilation of msi:ms6178 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ms6178&vendor=… Compilation of msi:ms7260 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ms7260&vendor=… Compilation of msi:ms9185 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ms9185&vendor=… Compilation of msi:ms9282 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ms9282&vendor=… Compilation of newisys:khepri has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=khepri&vendor=… Compilation of nvidia:l1_2pvv has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=l1_2pvv&vendor… Compilation of olpc:btest has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=btest&vendor=o… Compilation of olpc:rev_a has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=rev_a&vendor=o… Compilation of pcengines:alix1c has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=alix1c&vendor=… Compilation of sunw:ultra40 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ultra40&vendor… Compilation of supermicro:h8dmr has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=h8dmr&vendor=s… Compilation of supermicro:x6dai_g has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=x6dai_g&vendor… Compilation of supermicro:x6dhe_g has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=x6dhe_g&vendor… Compilation of supermicro:x6dhe_g2 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=x6dhe_g2&vendo… Compilation of supermicro:x6dhr_ig has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=x6dhr_ig&vendo… Compilation of supermicro:x6dhr_ig2 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=x6dhr_ig2&vend… Compilation of technologic:ts5300 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=ts5300&vendor=… Compilation of tyan:s1846 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s1846&vendor=t… Compilation of tyan:s2735 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2735&vendor=t… Compilation of tyan:s2850 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2850&vendor=t… Compilation of tyan:s2875 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2875&vendor=t… Compilation of tyan:s2880 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2880&vendor=t… Compilation of tyan:s2881 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2881&vendor=t… Compilation of tyan:s2882 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2882&vendor=t… Compilation of tyan:s2885 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2885&vendor=t… Compilation of tyan:s2891 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2891&vendor=t… Compilation of tyan:s2892 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2892&vendor=t… Compilation of tyan:s2895 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2895&vendor=t… Compilation of tyan:s2912 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s2912&vendor=t… Compilation of tyan:s4880 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s4880&vendor=t… Compilation of tyan:s4882 has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=s4882&vendor=t… Compilation of via:epia has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=epia&vendor=via Compilation of via:epia-m has been broken See the error log at http://qa.coreboot.org/log_buildbrd.php?revision=3101&device=epia-m&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, coreboot automatic build system

1 0

[PATCH] flashrom: further cleanups to enable_flash_cs5536
by Mart Raudsepp 11 Feb '08

11 Feb '08

Hello, Here's a small further cleanup patch to the enable_flash_cs5536 function in chipset_enable.c: flashrom: further cleanups to enable_flash_cs5536 Remove the "enable write to flash" message, as the caller appears to already report that. Move the 'modprobe msr' suggestions to the first lseek64 error handling, as we get an error there already. Rename a perror string from "read" to "read msr", as we use the latter already in this function for another read. Signed-off-by: Mart Raudsepp <mart.raudsepp(a)artecdesign.ee> --- chipset_enable.c | 7 ++----- 1 files changed, 2 insertions(+), 5 deletions(-)

2 1

r3101 - trunk/util/flashrom
by svn＠coreboot.org 11 Feb '08

11 Feb '08

Author: uwe Date: 2008-02-11 15:32:45 +0100 (Mon, 11 Feb 2008) New Revision: 3101 Modified: trunk/util/flashrom/chipset_enable.c Log: flashrom: further cleanups to enable_flash_cs5536 - Remove the "enable write to flash" message, as the caller appears to already report that. - Move the 'modprobe msr' suggestions to the first lseek64 error handling, as we get an error there already. - Rename a perror string from "read" to "read msr", as we use the latter already in this function for another read. Signed-off-by: Mart Raudsepp <mart.raudsepp(a)artecdesign.ee> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/util/flashrom/chipset_enable.c =================================================================== --- trunk/util/flashrom/chipset_enable.c 2008-02-09 13:06:45 UTC (rev 3100) +++ trunk/util/flashrom/chipset_enable.c 2008-02-11 14:32:45 UTC (rev 3101) @@ -259,18 +259,17 @@ if (lseek64(fd_msr, (off64_t) MSR_RCONF_DEFAULT, SEEK_SET) == -1) { perror("lseek64"); + printf("Cannot operate on MSR. Did you run 'modprobe msr'?\n"); close(fd_msr); return -1; } if (read(fd_msr, buf, 8) != 8) { - perror("read"); + perror("read msr"); close(fd_msr); return -1; } - printf("Enabling Geode MSR to write to flash.\n"); - if (buf[7] != 0x22) { buf[7] &= 0xfb; if (lseek64(fd_msr, (off64_t) MSR_RCONF_DEFAULT, SEEK_SET) == -1) { @@ -281,7 +280,6 @@ if (write(fd_msr, buf, 8) < 0) { perror("msr write"); - printf("Cannot write to MSR. Did you run 'modprobe msr'?\n"); close(fd_msr); return -1; } @@ -309,7 +307,6 @@ } if (write(fd_msr, buf, 8) < 0) { perror("msr write"); - printf("Cannot write to MSR. Did you run 'modprobe msr'?\n"); close(fd_msr); return -1; }

1 0

Re: [coreboot] Advantech Product Support
by Carl-Daniel Hailfinger 11 Feb '08

11 Feb '08

Dear Tomasz, On 11.02.2008 10:53, Tomasz.Malewski wrote: > We want to test CoreBoot on our products, I think that both sides should be happy :) > Welcome on board! Which processors/chipsets do you use in your products? If we know that, we can help evaluate how easy it is to make coreboot work with your products. I have looked at the AIMB-220 (Geode LX 800, CS5536) and it should be easy to get coreboot running on it. > There is any way to receive Wiki account ? > Yes, but it will need some time. But we can work together via the mailing list. Simply tell us on which products you want to test coreboot and we can then analyze the situation. Regards, Carl-Daniel

2 1

PIRQ tables...
by Stefan Reinauer 11 Feb '08

11 Feb '08

Ron, one question though: how does the information in the DTS relate to the information in the file irq_tables.c below? Do we have to specify polarity and interrupt enables twice now? We need to add all information from irq_tables.c to the mainboard DTS and read it from there. The mainboard DTS is our central data structure. something like eth0 { routing = "C, D, A, B"; polarity="level" }; pci_slot1 { routing = "B, C, D, A"; polarity="edge" }; pci_slot2 { ... }; agp_slot { .... }; I know the only truth is sending patches, but I see we're falling back into an old, overhauled scheme here and we should rethink careful. Two places for defining things is a 100% guarantee for failures to happen. Stefan * svn(a)coreboot.org <svn(a)coreboot.org> [080209 17:33]: > Modified: coreboot-v3/mainboard/pcengines/alix1c/dts > =================================================================== > --- coreboot-v3/mainboard/pcengines/alix1c/dts 2008-02-08 15:57:02 UTC (rev 581) > +++ coreboot-v3/mainboard/pcengines/alix1c/dts 2008-02-09 16:32:59 UTC (rev 582) > @@ -43,6 +43,16 @@ > pcipath = "0xf,0"; > enabled; > enable_ide = "1"; > + /* Interrupt enables for LPC bus. > + * Each bit is an IRQ 0-15. */ > + lpc_serirq_enable = "0x000010da"; > + /* LPC IRQ polarity. Each bit is an IRQ 0-15. */ > + lpc_serirq_polarity = "0x0000EF25"; > + /* 0:continuous 1:quiet */ > + lpc_serirq_mode = "1"; > + /* GPIO(0-0x20) for INT D:C:B:A, 0xFF=none. > + * See virtual PIC spec. */ > + enable_gpio_int_route = "0x0D0C0700"; > }; > superio { > /config/("superio/winbond/w83627hf/dts"); > > Added: coreboot-v3/mainboard/pcengines/alix1c/irq_tables.c > =================================================================== > --- coreboot-v3/mainboard/pcengines/alix1c/irq_tables.c (rev 0) > +++ coreboot-v3/mainboard/pcengines/alix1c/irq_tables.c 2008-02-09 16:32:59 UTC (rev 582) > + > +/* Platform IRQs */ > +#define PIRQA 11 > +#define PIRQB 10 > +#define PIRQC 11 > +#define PIRQD 9 > + > + * What Device IRQ PIN PIN WIRED TO > + * ------------------------------------------------- > + * AES 00:01.2 0a 01 A A > + * 3VPCI 00:0c.0 0a 01 A A > + * eth0 00:0d.0 0b 01 A B > + * mpci 00:0e.0 0a 01 A A > + * usb 00:0f.3 0b 02 B B > + * usb 00:0f.4 0b 04 D D > + * usb 00:0f.5 0b 04 D D > + > + /* CPU */ > + {0x00, (0x01 << 3) | 0x0, {{L_PIRQA, M_PIRQA}, {0x00, 0x00}, {0x00, 0x00}, {0x00, 0x00}}, 0x0, 0x0}, > + > + /* PCI (slot 1) */ > + {0x00, (0x0C << 3) | 0x0, {{L_PIRQC, M_PIRQC}, {L_PIRQD, M_PIRQD}, {L_PIRQA, M_PIRQA}, {L_PIRQB, M_PIRQB}}, 0x4, 0x0}, > + > + /* On-board ethernet */ > + {0x00, (0x0D << 3) | 0x0, {{L_PIRQB, M_PIRQB}, {0x00, 0x00}, {0x00, 0x00}, {0x00, 0x00}}, 0x0, 0x0}, > + > + /* Mini PCI (slot 2) */ > + {0x00, (0x0E << 3) | 0x0, {{L_PIRQA, M_PIRQA}, {L_PIRQB, M_PIRQB}, {L_PIRQC, M_PIRQC}, {L_PIRQD, M_PIRQD}}, 0x1, 0x0}, > + > + /* Chipset slots -- f.3 wires to B, and f.4 and f.5 wires to D. */ > + {0x00, (0x0F << 3) | 0x0, {{L_PIRQA, M_PIRQA}, {L_PIRQB, M_PIRQB}, {L_PIRQC, M_PIRQC}, {L_PIRQD, M_PIRQD}}, 0x0, 0x0}, > + } > +}; -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

6 8

Advantech Product Support
by Tomasz.Malewski 11 Feb '08

11 Feb '08

Dear All, We want to test CoreBoot on our products, I think that both sides should be happy :) There is any way to receive Wiki account ? Best Regards ---------------------------------------------------------------- Advantech Poland Sp. z o.o. Regional Service Center Europe ul. Matuszewska 14, 03-876 Warszawa phone: 48(0)22-332-37-30, 48(0)22-332-37-37 fax: 48(0)22-332-37-32, eMail: tomasz.malewski(a)advantech.pl<mailto:tomasz.malewski@advantech.pl> Web: http://www.advantech.pl Kapitał zakładowy 1 250 000, NIP: 952-19-82-861, Regon: 140265365 KRS: 0000246051, XX Wydział Gospodarczy Warszawa

1 0

← Newer
1
...
25
26
27
28
29
30
31
...
43
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot February 2008