May 2008 - openfirmware - mail.coreboot.org

PCI devices: IRQ table and vendor/device ID

by Andrea

Dear OFW developers, I'm going to a "new" PCI device on our custom (Geode LX based) board. I already add standard PCI support to our build (${BP}/dev/pcibus.fth), plus enabling some debugging stuff: true value pcimsg? true value probemsg? Is it possible to see its vendor/device ID from OFW? (we are going to create a custom OFW driver soon, but it will be enough to see it IDs for debugging purpose) AFAIK I also have to add "something" on PCI IRQ table to let the OS (in our case Linux) to attach its driver to the right IRQ. I found something like that inside vsapci.fth source (cpu/x86/pc/*/vsapci.fth) but it seems that this is used only for Geode companion chip devices. Any clue in how enumerate and assign IRQ to PCI devices with OFW? Thanks in advance and best regards, -- Andrea DAVE Srl - Electronics System House e-mail address: r&d4(a)dave-tech.it

12 years

2
1
0 0

LPC Flash programming

by Andrea

Dear OFW developers, I've found that inside dev/geode/lpcflash.fth it seem there is the Forth code to program an LPC Flash. I try to use it (like on OLPC) but I have the following undefines: ./build neptune.rom --- ${BP}/cpu/x86/pc/neptune/devices.fth is newer than the target file fw.img --- Rebuilding fw.img --- Cmd: /home/shared/devel/neptune/sw/ofw/openfirmware.git/cpu/x86/Linux/x86forth /home/shared/devel/neptune/sw/ofw/openfirmware.git/cpu/x86/build/basefw.dic ../fw.bth ${BP}/dev/geode/lpcflash.fth:57: ?file ? ${BP}/dev/geode/lpcflash.fth:68: /flash ? ${BP}/dev/geode/lpcflash.fth:70: flash-buf ? ${BP}/dev/geode/lpcflash.fth:74: get-file ? --- Saving fw.dic ... --- Saving fw.img ... --- fw.img is newer than the target file neptune.rom --- Rebuilding neptune.rom --- Cmd: /home/shared/devel/neptune/sw/ofw/openfirmware.git/cpu/x86/Linux/forth /home/shared/devel/neptune/sw/ofw/openfirmware.git/cpu/x86/Linux/../build/builder.dic ../neptune.bth --- Saving as neptune.rom - Direct ROM format As far as I understand this are dependency that are declared inside: dev/olpc/spiflash (due the fact that on OLPC LPC flash is an SPI flash connected via KB3700, correct me if I'm wrong) Can this lpcflash.fth device be used for a "standard" LPC flash too? or it's only some kind of "wrapper" for the OLPC's SPI flash? Thanks in advance and best regards, -- Andrea DAVE Srl - Electronics System House e-mail address: r&d4(a)dave-tech.it

12 years

2
1
0 0

Building ofw for Geode LX DB800 evaluation board

by llandre

We tried to build openfirmware for the DB800 board but it did not work: ------------------------------------------------------------- cd cpu/x86/pc/lxdevel make ... ./build lxdevel.rom --- Rebuilding romreset.di --- Cmd: ${HOSTDIR}/forth ${HOSTDIR}/../build/builder.dic ../romreset.bth --- Rebuilding rmstart.img --- Cmd: ${HOSTDIR}/forth ${HOSTDIR}/../build/builder.dic ../rmstart.bth ROM loader: version# 8 , format# 2 --- Rebuilding paging.di --- Cmd: ${HOSTDIR}/forth ${HOSTDIR}/../build/builder.dic ../../paging.bth --- Rebuilding fw.dic --- Cmd: ${HOSTDIR}/x86forth ${BP}/cpu/x86/build/basefw.dic ../fw.bth ${BP}/ofw/fs/ext2fs/dir.fth:54: >unix-seconds ? ${BP}/ofw/fs/ext2fs/dir.fth:220: >unix-seconds ? ${BP}/ofw/fs/ext2fs/dir.fth:256: unix-seconds> ? ${BP}/ofw/fs/ext2fs/methods.fth:74: >unix-seconds ? ${BP}/ofw/fs/jffs2/jffs2.fth:1605: unix-seconds> ? assign-pci-addr isn't unique ${BP}/cpu/x86/pc/olpc/mfgdata.fth:51: flash-base ? ${BP}/cpu/x86/pc/olpc/mfgdata.fth:52: flash-base ? ${BP}/dev/geode/display/gxfb.fth:121: tft-mode? ? ${BP}/dev/geode/display/gxfb.fth:159: gx? ? ${BP}/dev/geode/display/gxfb.fth:183: gx? ? ${BP}/dev/geode/display/gxfb.fth:221: gx? ? ${BP}/dev/geode/display/gxfb.fth:403: gx? ? ${BP}/dev/geode/display/gxfb.fth:407: gx? ? ${BP}/cpu/x86/pc/olpc/linux.fth:263: unfreeze ? --- Saving fw.dic ... --- Saving fw.img ... --- Rebuilding nandflash.fc --- Cmd: ${HOSTDIR}/forth ${HOSTDIR}/../build/builder.dic ../nandflash.bth ${BP}/dev/olpc/cafenand/badblock.fth:21: partition-start ? make: *** [lxdevel.rom] Error 1 ------------------------------------------------------------- Attached is a patch that allows to build it. As you can see we basically removed some stuff to make it to build. Do you think this is safe? We are going to download the binary image to the board but we would like to know we are trying to run something that makes sense first (typical newbie concern) ... Regards, llandre DAVE Electronics System House - R&D Department web: http://www.dave.eu email: r&d2(a)dave-tech.it diff --git a/cpu/x86/pc/lxdevel/fw.bth b/cpu/x86/pc/lxdevel/fw.bth index f9032e3..ac9162b 100644 --- a/cpu/x86/pc/lxdevel/fw.bth +++ b/cpu/x86/pc/lxdevel/fw.bth @@ -117,12 +117,14 @@ end-support-package [then] [ifdef] linux-support +\needs unix-seconds> fload ${BP}/ofw/fs/unixtime.fth \ Unix time calculation support-package: ext2-file-system fload ${BP}/ofw/fs/ext2fs/ext2fs.fth \ Linux file system end-support-package [then] [ifdef] jffs2-support +\needs unix-seconds> fload ${BP}/ofw/fs/unixtime.fth \ Unix time calculation support-package: jffs2-file-system fload ${BP}/ofw/fs/jffs2/jffs2.fth \ Journaling flash file system 2 end-support-package diff --git a/cpu/x86/pc/lxdevel/lxdevel.bth b/cpu/x86/pc/lxdevel/lxdevel.bth index ffb3467..2c68bd9 100644 --- a/cpu/x86/pc/lxdevel/lxdevel.bth +++ b/cpu/x86/pc/lxdevel/lxdevel.bth @@ -6,7 +6,7 @@ in: ${BP}/cpu/x86/pc/lxdevel/build/romreset.di in: ${BP}/cpu/x86/pc/lxdevel/build/rmstart.img in: ${BP}/cpu/x86/pc/lxdevel/build/paging.di in: ${BP}/cpu/x86/pc/lxdevel/build/fw.dic -in: ${BP}/dev/geode/nandflash/build/nandflash.fc +\ in: ${BP}/dev/geode/nandflash/build/nandflash.fc in: ${BP}/dev/mmc/sdhci/build/sdhci.fc in: ${BP}/dev/mmc/sdhci/build/sdmmc.fc in: ${BP}/dev/geode/ac97/build/ac97.fc @@ -18,10 +18,10 @@ in: ${BP}/dev/usb2/device/serial/build/usbserial.fc in: ${BP}/dev/usb2/device/storage/build/usbstorage.fc in: ${BP}/dev/usb2/device/keyboard/build/usbkbd.fc in: ${BP}/dev/usb2/device/wlan/build/usb8388.fc -in: ${BP}/dev/olpc/cafenand/build/cafenand.fc -in: ${BP}/dev/olpc/cafecamera/build/cafecamera.fc +\ in: ${BP}/dev/olpc/cafenand/build/cafenand.fc +\ in: ${BP}/dev/olpc/cafecamera/build/cafecamera.fc in: ${BP}/dev/pci/build/pcibridg.fc -in: usb8388.bin +\ in: usb8388.bin build-now @@ -48,7 +48,7 @@ writing lxdevel.rom " romreset.di" $add-file \ " resume.di" $add-file - fload ${BP}/cpu/x86/pc/olpc/loaddropins.fth +\ fload ${BP}/cpu/x86/pc/olpc/loaddropins.fth " ${BP}/dev/pci/build/pcibridg.fc" " class060400" $add-deflated-dropin /rom h# 400 - pad-file \ rmstart image must start 0x400 from end diff --git a/cpu/x86/pc/lxdevel/rmstart.bth b/cpu/x86/pc/lxdevel/rmstart.bth index 57cccd3..94f7673 100644 --- a/cpu/x86/pc/lxdevel/rmstart.bth +++ b/cpu/x86/pc/lxdevel/rmstart.bth @@ -5,7 +5,7 @@ command: &builder &this build-now \ To do this on the geode, extra init may be necessary -\ create debug-reset +create debug-reset fload ${BP}/cpu/x86/pc/lxdevel/config.fth fload ${BP}/cpu/x86/pc/olpc/rmstart.fth

12 years

4
10
0 0

[administrative] openfirmware commit messages

by Stefan Reinauer

Dear OpenFirmware enthusiasts, we recently created a new mailing list around Firmworks' OpenFirmware implementation (the one that is used on OLPC for example): https://www.openfirmware.info/mailman/listinfo/openfirmware Due to this new mailing list, commit messages to Mitch's OpenFirmware repository will go to the new mailing list from now on. Best regards, Stefan Reinauer -- 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

12 years

1
0
0 0

[Fwd: Re: Porting OFW to custom hardware]

by Mitch Bradley

(Copying reply to list for reference)

12 years

1
0
0 0

Welcome to Open Firmware!

by Stefan Reinauer

Dear Readers, welcome to the Open Firmware IEEE 1275-1994 list running as openfirmware(a)openfirmware.info Best regards, Stefan Reinauer -- 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

12 years

1
0
0 0

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

openfirmware May 2008