https://www.coreboot.org/api.php?action=feedcontributions&user=Bari&feedformat=atomcoreboot - User contributions [en]2024-03-29T14:49:57ZUser contributionsMediaWiki 1.40.0https://www.coreboot.org/index.php?title=Project_Ideas&diff=11055Project Ideas2012-03-09T18:31:49Z<p>Bari: /* coreboot port to Marvell ARM SOC's with PCIe */ removed Marvell since they didn't open the docs</p>
<hr />
<div>The following are some ideas that have come up in the community. Some are more or less suitable for GSoC and prospective students' application should expand on some ideas and pair back others.<br />
<br />
== Linux Firmware Kit, BITS ==<br />
<br />
There are various test suites for firmware aspects, esp. those that interacts with the operating systems. Unfortunately, some of these projects are dead, some seem to be forked and developed semi-publically, and having all that stuff in lots of different places is a big hassle.<br />
<br />
The goal of this project is to pick up the pieces, and create a single tool (most likely a bootable CD/USB drive image) that can be booted on vendor BIOS (for the Red Hat and Canonical developers that work on these) as well as coreboot (preferably seabios and FILO to improve testability - is an issue created/fixed by coreboot or seabios?). This can then be improved in various ways.<br />
<br />
There's also intel-gpu-tools that might have some useful tests (at least for intel-boards): http://article.gmane.org/gmane.comp.video.dri.devel/63948<br />
<br />
When applying for this task, please state in your proposal what you think might be worthy extensions to the existing tests.<br />
<br />
Required knowledge for this task: Not so much coreboot/firmware level, but you should have some idea of the boot process of a Linux system (as these test suites are mostly Linux based). GSoC probably won't provide enough time to learn all that (Linux boot process, firmware interfaces such as ACPI) and still develop the tools in some useful way.<br />
<br />
== Infrastructure for automatic code checking ==<br />
We already have a build bot that builds various configurations of coreboot. It would be nice to extend it with various code validation routines, for example:<br />
* Validate that there's no regression in doxygen documentation (eg. are all arguments to functions still explained in @param tags, eg. after new arguments were added?)<br />
* Make code lint clean (and maybe extend lint to not fall into our traps), and run lint over the tree. Report regressions<br />
* Use LLVM's static code checking facilities, report regressions.<br />
* Work on code coverage support for coreboot code (dump data into ram, or via serial. Provide tools to fetch it). Analyse that data.<br />
<br />
'''Links'''<br />
* LLVM tools: [http://clang.llvm.org/StaticAnalysis.html Clang static analyser], [http://llvm.org/ProjectsWithLLVM/#Calysto SSA assertion checker]<br />
* Lint tools: [http://lclint.cs.virginia.edu/ Splint]<br />
* Coverage: [http://ltp.sourceforge.net/test/coverage/lcov.php LCOV], [http://ggcov.sourceforge.net GGCOV]<br />
<br />
'''Mentors'''<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
<br />
== coreboot test suite ==<br />
Create a test suite to gather and report coreboot mainboard and payload settings. This project may leverage libpayload, coreinfo, memtest86, BITS, and other tools. The suite should gather result and report them at summary and detailed levels. The goal is to help coreboot developers identify problems and to test coreboot features. This project should work closely with the testing rig and test reporting projects. It is important the the student considers how testing and reporting can be extended as features and tests are added in the future.<br />
<br />
'''Links'''<br />
* [http://biosbits.org/ BITS]<br />
http://www.coreboot.org/Supported_Motherboards<br />
<br />
'''Mentors'''<br />
* [[User:MJones|Marc Jones]] <br />
<br />
== coreboot cheap testing rig ==<br />
The goal of this project is to create a cheap testing rig which works with the existing board test infrastructure. We have a hardware test system since 2006:<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/Slides-LinuxBIOS-QA.pdf Quality Assurance Talk (Slides)]<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/TestIntegrationManual.pdf Test Integration Manual]<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/DevelopersManual.pdf Test Developers Manual]<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/TestSpecification.pdf Test Specification]<br />
<br />
The initial version of our testing rig used a remote power switch and was rather expensive. With cheaper technologies such as X10, it's possible to drop the testing costs per board significantly.<br />
<br />
'''Links'''<br />
* http://qa.coresystems.de<br />
* [[InSystemFlasher]] is a cheap DIY hardware prototype for building an automated testing rig for modern SPI-based boards. This could be used as a starting point.<br />
<br />
'''Mentors'''<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
<br />
== coreboot mainboard test result reporting ==<br />
One of the biggest challenges in coreboot is support many systems in the same codebase. As systems age and coreboot continues to develop, the condition of mainboards becomes unknown. This project would define a coreboot test results reporting mechanism, gather data, and report passing and failing systems on a webpage. This project would work closely with the coreboot test suite project and/or the hardware test rig project. A good example of test results gathering and reporting is done by the Phoronix/Openbenchmark. The student should investigate other test and reporting solutions to leverage the best options for coreboot. It is important the the student considers how testing and reporting can be extended as features and tests are added in the future.<br />
<br />
'''Links'''<br />
* http://openbenchmarking.org/<br />
* http://www.coreboot.org/Supported_Motherboards<br />
<br />
'''Mentors'''<br />
* [[User:Stepan|Stefan Reinauer]]<br />
* [[User:MJones|Marc Jones]]<br />
<br />
<br />
== coreboot ports for Family14 mainboards == <br />
Identify potential mainboards to port based on the recently released AMD Family 14 support. The goal would be to support publicly available plaftorms with a number of payloads and operating systems.<br />
<br />
'''Mentors'''<br />
*[[User:Jason Wang|QingPei Wang]]<br />
<br />
<br />
== coreboot ACPI/S3/power managment ==<br />
coreboot has support for ACPI tables and S3 support for some platforms, but it is very mainboard specific. Create a generic solution for ACPI table generation and S3 support.<br />
<br />
'''Mentors'''<br />
*<br />
<br />
<br />
==coreboot port to ARM SOC's with PCIe==<br />
<br />
[http://www.xilinx.com/products/silicon-devices/epp/zynq-7000/index.htm Xilinx Zynq-7030]<br />
<br />
[http://www.altera.com/devices/fpga/cyclone-v-fpgas/hard-processor-system/cyv-soc-hps.html Altera Cyclone V ]<br />
<br />
[http://www.st.com/internet/mcu/product/251211.jsp ST spear1340]<br />
<br />
<br />
[[ARM]] SOC's with PCIe are available. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support.<br />
<br />
Note that coreboot has in the past supported three different CPUs (x86, Alpha, PPC), so the structure is there for adding in a new processor family. <br />
We will need to find the right platform to do the work, but I (Ron) can provide a board and JTAG debugger if needed. <br />
<br />
There was an ARM project started in 2011. <br />
<br />
http://blogs.coreboot.org/blog/2011/05/11/gsoc2011-project-porting-coreboot-to-arm-architecture/<br />
<br />
'''Mentors'''<br />
* Bari Ari<br />
* [[User:Rminnich|Ron Minnich]]<br />
* [[User:Jason Wang|QingPei Wang]]<br />
<br />
== coreboot panic room ==<br />
<br />
Create a safe boot solution for coreboot to easily and cheaply recover the system in case of a panic(). <br />
<br />
Ron would like to base this solution around SerialICE. The basic idea is that the system always boots to SerialICE. There is a test in CMOS for 'last boot worked' and, if this is set, SerialICE finds a coreboot in cbfs and runs it. If 'last boot worked' is not set, or the user hits some magic keyboard sequence, SerialICE takes control. <br />
<br />
SerialICE needs to be extended (not much) to make this work. Having this capability would make it possible for Ron to get some very hard ports working that are just not possible today. At the same time, there are lots of hardware boards to test this idea on, so it should be easy to get it working. <br />
<br />
It might be possible to integrate this into the coreboot build as a bootblock option (in the same spot as the fallback/normal switch and the simple loader).<br />
<br />
<br />
There was a panic room project started in 2011 <br />
http://blogs.coreboot.org/blog/2011/05/09/gsoc-project-coreboot-panic-room-diagnostics-also-remote-flashing/<br />
<br />
'''Mentors'''<br />
* [[User:Rminnich|Ron Minnich]]<br />
<br />
== Board config infrastructure ==<br />
<br />
Design data structures that host information about the board layout so coreboot can better initialize components and generate all kinds of tables (mptable, pirq, acpi, ...) from that dynamically (at build or runtime, as appropriate). Adapt boards to use that instead of the current hardcodes.<br />
<br />
'''Links'''<br />
* ?<br />
<br />
'''Mentors'''<br />
* ?<br />
<br />
<br />
== Refactor AMD code ==<br />
<br />
AMD K8 and AMD Fam10 are different enough to have their own code. This is unfortunate, as you have to decide which CPU type you use in a given mainboard. Refactor AMD code so a single image can support both chip types on a given board. Also move tables from get_bus_conf and the like to the device tree or kconfig options (or runtime detection), as appropriate.<br />
<br />
'''Links'''<br />
* ?<br />
<br />
'''Mentors'''<br />
* [[User:Stepan|Stefan Reinauer]]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=10900Laptop2011-10-03T20:35:31Z<p>Bari: /* Random product links */ clarification of why an old list of laptops is here</p>
<hr />
<div>== Laptops with coreboot Support ==<br />
<br />
* coreboot supports the [http://en.getac.com/products/P470/P470_overview.html Getac P470] semi rugged notebook, based on Intel 82945GM/ICH7.<br />
* coreboot supports the [http://www.roda-computer.com/en/products/notebooks/rocky-iii-rk886ex.html Roda RK886EX (Rocky III+)] laptop, based on Intel 82945GM/ICH7.<br />
* coreboot supports one variant of the Lenovo [[Thinkpad X60s]].<br />
<br />
== Embedded controllers ==<br />
<br />
The remaining issue with supporting netbooks may be open firmware support for the [[Embedded controller]] (EC).<br />
These ECs used to support keyboard scan, lid open/closed, battery charging, power management, etc.<br />
<br />
coreboot should work with the "stock" EC firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)?<br />
<br />
== HOWTO to find a way ==<br />
<br />
* find a model and manufacturer of your laptop<br />
* download these tools:<br />
# superiotool ( svn co svn://coreboot.org/coreboot/trunk/util/superiotool )<br />
# inteltool ( svn co svn://coreboot.org/coreboot/trunk/util/inteltool )<br />
# ectool ( svn co svn://coreboot.org/coreboot/trunk/util/ectool )<br />
# dmidecode ( cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/dmidecode co dmidecode )<br />
# msrtool (svn co svn://coreboot.org/coreboot/trunk/util/msrtool )<br />
# nvramtool ( svn co svn://coreboot.org/coreboot/trunk/util/nvramtool )<br />
# flashrom ( svn co svn://coreboot.org/flashrom/trunk flashrom )<br />
* make and install them (make; sudo make install) - you need at least libpci/pciutils<br />
* check that your distro have this tools and install them:<br />
# lspci<br />
# dmesg<br />
# acpitool<br />
# lspnp<br />
# lsusb<br />
* Do this commands:<br />
# lspci -nnvvvxxxx > lscpi.log<br />
# lspnp -vv > lspnp.log<br />
# lsusb -vvv > lsusb.log<br />
# superiotool -deV > superiotool.log<br />
# inteltool -a > inteltool.log<br />
# ectool > ectool.log<br />
# msrtool > msrtool.log<br />
# dmidecode > dmidecode.log<br />
# biosdecode > biosdecode.log<br />
# nvramtool -x > nvramtool.log<br />
# dmesg > dmesg.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick > flashrom_info.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick -r rom.bin > flashrom_read.log<br />
* Save all logs in safe place, and also rom.bin file. <br />
* try to find information - what EC or Super I/O chip is used in your laptop (may be some info in Service Manuals or Disassembly guides)<br />
* if you see that ectool return some fake staff - like only 'FF' or '00' - so you have custom EC configuration, it's a hard work for support<br />
* if you see that ectool return looks like 'right' output - you have a big chances for support<br />
* you need to find from thease outputs Super I/O / EC chip name, or if not see this - disassembly your laptop<br />
* try to find your Super I/O / EC chip datasheet<br />
<br />
== Laptop survey ==<br />
<br />
This not a list of coreboot supported laptops. This page only lists the chipsets, Super I/Os, flash chips, and especially [[embedded controller]]s used in a few laptops, just for reference purposes.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset NB<br />
! align="left" | Chipset SB<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | [[Embedded controller|EC]]<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash S.<br />
! align="left" | Flash T.<br />
! align="left" | Owner<br />
<br />
|- bgcolor="#dddddd"<br />
| ASUS || S96F/Z96F || Intel&nbsp;Core&trade;2 Duo T7400 || Intel&nbsp;i945 || Intel ICH7 || ITE IT8510E || in Super I/O || ? || ? || ? || ? || [http://www.flashrom.org/pipermail/flashrom/2010-January/001986.html macavity]<br />
|- bgcolor="#eeeeee"<br />
| Acer || Aspire One ZG5 || Intel Atom N270 1.6GHz || Intel 82945GME || Intel NH82801GBM ICH7-M || Winbond WPCE775LA0DG || in Super I/O || Winbond 25x80AVSIG || 8Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Acer || Aspire 3613LC || Intel Celeron M 370 1.5GHz L2: 1MB || Intel 82910GML || Intel FW82801FBM SL7W6 ICH6-M || ? || ? || PMC 0537 PM39LV040-70JCE || 1Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX |||| SMSC&nbsp;FDC37N958FR || in Super I/O || AMD AM29F040B || 512KB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude C610|Latitude C610]] || PIII, 1.2 GHz || Intel i830 |||| SMSC&nbsp;LPC47N252 || in Super I/O || SST SST49LF004A || 512KB || no || PLCC || [mailto:coreboot@miradou.com CybFr]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Vostro V13]] || Intel Celeron 743 1.2GHz, L2: 1MB (Ultra Low Voltage) || Mobile Intel GS45 Express GHMC ||Intel 82801IEM ICH9M-E|| none || ITE IT8502E || Winbond 25Q16BVSIG || 2Mb || no || SOIP/PDIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Dell || XPS M1530 || Intel&nbsp;Core&trade;2 Duo T7700 || Intel PM965 || Intel ICH8 || none || Winbond WPC8763L || Winbond 25X16VSIG || 16Mb || ?? || SPI || Corey Osgood<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-S. || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX |||| SMSC FDC37N769 || ? || Fujitsu&nbsp;MBM29F400T<sup>1</sup> || ? || no || TSOP(?) || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Fujitsu-S. || Lifebook S7110 || Intel&nbsp;Core&trade;2 Duo T7200 || Intel&nbsp;i945 || Intel ICH7 || SMSC&nbsp;LPC47N217 || Fujitsu MB90378 || Spansion S25FL008A<sup>2</sup> || 1024 kB || no || SO8 / SPI || twice11<br />
|- bgcolor="#eeeeee"<br />
| Gateway || [[Gateway W730-K8X | W730-K8X]] || Socket 754 |||| ?? || ?? || ?? || SST 39VF040 || ?? || yes || PLCC || [[User:Juri|Juri]]<br />
|- bgcolor="#dddddd"<br />
| Gateway || [[Gateway 6020GZ|6020GZ]] || Celeron M 1.4Ghz || Intel 855GME |||| ?? || ?? || ?? || ?? || no || ?? || [[User:Juri|Juri]]<br />
|- bgcolor="#eeeeee"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 |||| NSC PC87393VJG || NSC PC87570 || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || [http://thread.gmane.org/gmane.linux.bios/13081 NS]<br />
|- bgcolor="#dddddd"<br />
| Getac || P470 || Intel&reg;&nbsp;Core 2 Duo Mobile || Intel 945 || Intel ICH7 || ? || ? || ? || 8Mb || no || SPI / SOIC8 || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel&nbsp;Celeron&nbsp;1.7&nbsp;GHz || SiS650 |||| NSC&nbsp;PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel&nbsp;82371MB ||Intel PIIX4M || SMSC&nbsp;FDC37N869 || NSC&nbsp;PC87570 || SST 28SF040A || 512 kB || no || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| IBM || Thinkpad T30 || Intel P4 Mobile, 1.8 GHz || Intel&nbsp;i845 || Intel ICH3-M || NSC&nbsp;PC87392 || Renesas H8S&nbsp;64F3169ATE10 || ST&nbsp;M50FW080N5 || 1024 kB || no || TSOP40 / FWH || edgecase<br />
|- bgcolor="#dddddd"<br />
| IBM || Thinkpad X60s || Intel Core Duo CPU L2300 || Intel&nbsp;i945GM || Intel ICH7-M || NSC&nbsp;PC87392 (in Ultrabase) || Renesas H8S2161B || MX25L1605D || 2048 kB || no || SOIC-8 || [[User:SvenS|Sven Schnelle]]<br />
|- bgcolor="#dddddd"<br />
| MSI || Wind U100 || Intel Atom N280 1.66Ghz || Intel 945GSE || Intel ICH7-M || ? || ENE KB3310 || SST MX25L8005 || 8 Mb|| no || TSOP40 / SPI || ?<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110] || VIA&nbsp;C7-M&nbsp;ULV&nbsp;1.0&nbsp;GHz || VIA VX800 |||| none || ENE KB3310 || ? || ? || no || ? || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Panasonic || Toughbook&nbsp;CF-25 || P166MMX || FW82439TX&nbsp;(430TX) || FW82371AB || NSC PC87336VJG || Renesas&nbsp;3886 || SST SST29EE020 || 256 kB || no || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Roda || Rocky III+ RK886EX || Intel&reg;&nbsp;Core 2 Duo Mobile T5500 || Intel 945 || Intel ICH7 || SMSC&reg;&nbsp;LPC47N227 || Renesas&nbsp;M38859 || SST SST49LF080 || 8Mb || yes || PLCC || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#dddddd"<br />
| Roda || Rocky II+ RT686 || Intel&nbsp;Pentium III || Intel 430BX || Intel FW82371EB || SMSC&reg;&nbsp;FDC37N769 || Renesas&nbsp;M38867M8A || SST SST29LE020 || 256KB || yes || PLCC/parallel || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1XD || P2 400 || 443ZX |||| ? || ? || ST M29W004BT || 512 kB || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1X || P266MMX || 430TX |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Satellite&nbsp;A80-117 || Intel&nbsp;Celeron || Intel&nbsp;915GM || Intel ICH6 || SMSC&nbsp;LPC47N217 || ENE KB910 || ? || 1024 kB || no || TSOP (?) || [[User:Uwe|UH]]<br />
<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br /><br />
<sup>2</sup> Nice thing: EC/Flash is not shared, so you can erase the whole flash during system operation (this was tested).<br /><br />
</small><br />
<br />
Further links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Mailinglist discussion ==<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
* [http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]<br />
<br />
== Random product links ==<br />
<br />
The following list is a out of date. These were laptops of interest as possible candidates for coreboot support. Most, if not all of these laptops are no longer available. It is only here for reference.<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
Netbook designs that use the VIA vx700 chipset:<br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
AMD 690/600 laptops: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=10899Laptop2011-10-03T19:13:24Z<p>Bari: Clarification of the List of Laptops with coreboot Support</p>
<hr />
<div>== Laptops with coreboot Support ==<br />
<br />
* coreboot supports the [http://en.getac.com/products/P470/P470_overview.html Getac P470] semi rugged notebook, based on Intel 82945GM/ICH7.<br />
* coreboot supports the [http://www.roda-computer.com/en/products/notebooks/rocky-iii-rk886ex.html Roda RK886EX (Rocky III+)] laptop, based on Intel 82945GM/ICH7.<br />
* coreboot supports one variant of the Lenovo [[Thinkpad X60s]].<br />
<br />
== Embedded controllers ==<br />
<br />
The remaining issue with supporting netbooks may be open firmware support for the [[Embedded controller]] (EC).<br />
These ECs used to support keyboard scan, lid open/closed, battery charging, power management, etc.<br />
<br />
coreboot should work with the "stock" EC firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)?<br />
<br />
== HOWTO to find a way ==<br />
<br />
* find a model and manufacturer of your laptop<br />
* download these tools:<br />
# superiotool ( svn co svn://coreboot.org/coreboot/trunk/util/superiotool )<br />
# inteltool ( svn co svn://coreboot.org/coreboot/trunk/util/inteltool )<br />
# ectool ( svn co svn://coreboot.org/coreboot/trunk/util/ectool )<br />
# dmidecode ( cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/dmidecode co dmidecode )<br />
# msrtool (svn co svn://coreboot.org/coreboot/trunk/util/msrtool )<br />
# nvramtool ( svn co svn://coreboot.org/coreboot/trunk/util/nvramtool )<br />
# flashrom ( svn co svn://coreboot.org/flashrom/trunk flashrom )<br />
* make and install them (make; sudo make install) - you need at least libpci/pciutils<br />
* check that your distro have this tools and install them:<br />
# lspci<br />
# dmesg<br />
# acpitool<br />
# lspnp<br />
# lsusb<br />
* Do this commands:<br />
# lspci -nnvvvxxxx > lscpi.log<br />
# lspnp -vv > lspnp.log<br />
# lsusb -vvv > lsusb.log<br />
# superiotool -deV > superiotool.log<br />
# inteltool -a > inteltool.log<br />
# ectool > ectool.log<br />
# msrtool > msrtool.log<br />
# dmidecode > dmidecode.log<br />
# biosdecode > biosdecode.log<br />
# nvramtool -x > nvramtool.log<br />
# dmesg > dmesg.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick > flashrom_info.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick -r rom.bin > flashrom_read.log<br />
* Save all logs in safe place, and also rom.bin file. <br />
* try to find information - what EC or Super I/O chip is used in your laptop (may be some info in Service Manuals or Disassembly guides)<br />
* if you see that ectool return some fake staff - like only 'FF' or '00' - so you have custom EC configuration, it's a hard work for support<br />
* if you see that ectool return looks like 'right' output - you have a big chances for support<br />
* you need to find from thease outputs Super I/O / EC chip name, or if not see this - disassembly your laptop<br />
* try to find your Super I/O / EC chip datasheet<br />
<br />
== Laptop survey ==<br />
<br />
This not a list of coreboot supported laptops. This page only lists the chipsets, Super I/Os, flash chips, and especially [[embedded controller]]s used in a few laptops, just for reference purposes.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset NB<br />
! align="left" | Chipset SB<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | [[Embedded controller|EC]]<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash S.<br />
! align="left" | Flash T.<br />
! align="left" | Owner<br />
<br />
|- bgcolor="#dddddd"<br />
| ASUS || S96F/Z96F || Intel&nbsp;Core&trade;2 Duo T7400 || Intel&nbsp;i945 || Intel ICH7 || ITE IT8510E || in Super I/O || ? || ? || ? || ? || [http://www.flashrom.org/pipermail/flashrom/2010-January/001986.html macavity]<br />
|- bgcolor="#eeeeee"<br />
| Acer || Aspire One ZG5 || Intel Atom N270 1.6GHz || Intel 82945GME || Intel NH82801GBM ICH7-M || Winbond WPCE775LA0DG || in Super I/O || Winbond 25x80AVSIG || 8Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Acer || Aspire 3613LC || Intel Celeron M 370 1.5GHz L2: 1MB || Intel 82910GML || Intel FW82801FBM SL7W6 ICH6-M || ? || ? || PMC 0537 PM39LV040-70JCE || 1Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX |||| SMSC&nbsp;FDC37N958FR || in Super I/O || AMD AM29F040B || 512KB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude C610|Latitude C610]] || PIII, 1.2 GHz || Intel i830 |||| SMSC&nbsp;LPC47N252 || in Super I/O || SST SST49LF004A || 512KB || no || PLCC || [mailto:coreboot@miradou.com CybFr]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Vostro V13]] || Intel Celeron 743 1.2GHz, L2: 1MB (Ultra Low Voltage) || Mobile Intel GS45 Express GHMC ||Intel 82801IEM ICH9M-E|| none || ITE IT8502E || Winbond 25Q16BVSIG || 2Mb || no || SOIP/PDIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Dell || XPS M1530 || Intel&nbsp;Core&trade;2 Duo T7700 || Intel PM965 || Intel ICH8 || none || Winbond WPC8763L || Winbond 25X16VSIG || 16Mb || ?? || SPI || Corey Osgood<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-S. || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX |||| SMSC FDC37N769 || ? || Fujitsu&nbsp;MBM29F400T<sup>1</sup> || ? || no || TSOP(?) || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Fujitsu-S. || Lifebook S7110 || Intel&nbsp;Core&trade;2 Duo T7200 || Intel&nbsp;i945 || Intel ICH7 || SMSC&nbsp;LPC47N217 || Fujitsu MB90378 || Spansion S25FL008A<sup>2</sup> || 1024 kB || no || SO8 / SPI || twice11<br />
|- bgcolor="#eeeeee"<br />
| Gateway || [[Gateway W730-K8X | W730-K8X]] || Socket 754 |||| ?? || ?? || ?? || SST 39VF040 || ?? || yes || PLCC || [[User:Juri|Juri]]<br />
|- bgcolor="#dddddd"<br />
| Gateway || [[Gateway 6020GZ|6020GZ]] || Celeron M 1.4Ghz || Intel 855GME |||| ?? || ?? || ?? || ?? || no || ?? || [[User:Juri|Juri]]<br />
|- bgcolor="#eeeeee"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 |||| NSC PC87393VJG || NSC PC87570 || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || [http://thread.gmane.org/gmane.linux.bios/13081 NS]<br />
|- bgcolor="#dddddd"<br />
| Getac || P470 || Intel&reg;&nbsp;Core 2 Duo Mobile || Intel 945 || Intel ICH7 || ? || ? || ? || 8Mb || no || SPI / SOIC8 || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel&nbsp;Celeron&nbsp;1.7&nbsp;GHz || SiS650 |||| NSC&nbsp;PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel&nbsp;82371MB ||Intel PIIX4M || SMSC&nbsp;FDC37N869 || NSC&nbsp;PC87570 || SST 28SF040A || 512 kB || no || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| IBM || Thinkpad T30 || Intel P4 Mobile, 1.8 GHz || Intel&nbsp;i845 || Intel ICH3-M || NSC&nbsp;PC87392 || Renesas H8S&nbsp;64F3169ATE10 || ST&nbsp;M50FW080N5 || 1024 kB || no || TSOP40 / FWH || edgecase<br />
|- bgcolor="#dddddd"<br />
| IBM || Thinkpad X60s || Intel Core Duo CPU L2300 || Intel&nbsp;i945GM || Intel ICH7-M || NSC&nbsp;PC87392 (in Ultrabase) || Renesas H8S2161B || MX25L1605D || 2048 kB || no || SOIC-8 || [[User:SvenS|Sven Schnelle]]<br />
|- bgcolor="#dddddd"<br />
| MSI || Wind U100 || Intel Atom N280 1.66Ghz || Intel 945GSE || Intel ICH7-M || ? || ENE KB3310 || SST MX25L8005 || 8 Mb|| no || TSOP40 / SPI || ?<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110] || VIA&nbsp;C7-M&nbsp;ULV&nbsp;1.0&nbsp;GHz || VIA VX800 |||| none || ENE KB3310 || ? || ? || no || ? || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Panasonic || Toughbook&nbsp;CF-25 || P166MMX || FW82439TX&nbsp;(430TX) || FW82371AB || NSC PC87336VJG || Renesas&nbsp;3886 || SST SST29EE020 || 256 kB || no || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Roda || Rocky III+ RK886EX || Intel&reg;&nbsp;Core 2 Duo Mobile T5500 || Intel 945 || Intel ICH7 || SMSC&reg;&nbsp;LPC47N227 || Renesas&nbsp;M38859 || SST SST49LF080 || 8Mb || yes || PLCC || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#dddddd"<br />
| Roda || Rocky II+ RT686 || Intel&nbsp;Pentium III || Intel 430BX || Intel FW82371EB || SMSC&reg;&nbsp;FDC37N769 || Renesas&nbsp;M38867M8A || SST SST29LE020 || 256KB || yes || PLCC/parallel || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1XD || P2 400 || 443ZX |||| ? || ? || ST M29W004BT || 512 kB || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1X || P266MMX || 430TX |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Satellite&nbsp;A80-117 || Intel&nbsp;Celeron || Intel&nbsp;915GM || Intel ICH6 || SMSC&nbsp;LPC47N217 || ENE KB910 || ? || 1024 kB || no || TSOP (?) || [[User:Uwe|UH]]<br />
<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br /><br />
<sup>2</sup> Nice thing: EC/Flash is not shared, so you can erase the whole flash during system operation (this was tested).<br /><br />
</small><br />
<br />
Further links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Mailinglist discussion ==<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
* [http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]<br />
<br />
== Random product links ==<br />
<br />
The following list is a few years old. Most if not all of these laptops are no longer available. It is only here for reference purposes.<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
Netbook designs that use the VIA vx700 chipset:<br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
AMD 690/600 laptops: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=10898Laptop2011-10-03T18:54:58Z<p>Bari: /* Random product links */</p>
<hr />
<div>== Recent progress of coreboot on laptops ==<br />
<br />
* coreboot supports the [http://en.getac.com/products/P470/P470_overview.html Getac P470] semi rugged notebook, based on Intel 82945GM/ICH7.<br />
* coreboot supports the [http://www.roda-computer.com/en/products/notebooks/rocky-iii-rk886ex.html Roda RK886EX (Rocky III+)] laptop, based on Intel 82945GM/ICH7.<br />
* VIA has recently released open documentation for the VX700 and VX800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal].<br />
* coreboot supports one variant of the Lenovo [[Thinkpad X60s]].<br />
<br />
== Embedded controllers ==<br />
<br />
The remaining issue with supporting netbooks may be open firmware support for the [[Embedded controller]] (EC).<br />
These ECs used to support keyboard scan, lid open/closed, battery charging, power management, etc.<br />
<br />
coreboot should work with the "stock" EC firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)?<br />
<br />
== HOWTO to find a way ==<br />
<br />
* find a model and manufacturer of your laptop<br />
* download these tools:<br />
# superiotool ( svn co svn://coreboot.org/coreboot/trunk/util/superiotool )<br />
# inteltool ( svn co svn://coreboot.org/coreboot/trunk/util/inteltool )<br />
# ectool ( svn co svn://coreboot.org/coreboot/trunk/util/ectool )<br />
# dmidecode ( cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/dmidecode co dmidecode )<br />
# msrtool (svn co svn://coreboot.org/coreboot/trunk/util/msrtool )<br />
# nvramtool ( svn co svn://coreboot.org/coreboot/trunk/util/nvramtool )<br />
# flashrom ( svn co svn://coreboot.org/flashrom/trunk flashrom )<br />
* make and install them (make; sudo make install) - you need at least libpci/pciutils<br />
* check that your distro have this tools and install them:<br />
# lspci<br />
# dmesg<br />
# acpitool<br />
# lspnp<br />
# lsusb<br />
* Do this commands:<br />
# lspci -nnvvvxxxx > lscpi.log<br />
# lspnp -vv > lspnp.log<br />
# lsusb -vvv > lsusb.log<br />
# superiotool -deV > superiotool.log<br />
# inteltool -a > inteltool.log<br />
# ectool > ectool.log<br />
# msrtool > msrtool.log<br />
# dmidecode > dmidecode.log<br />
# biosdecode > biosdecode.log<br />
# nvramtool -x > nvramtool.log<br />
# dmesg > dmesg.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick > flashrom_info.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick -r rom.bin > flashrom_read.log<br />
* Save all logs in safe place, and also rom.bin file. <br />
* try to find information - what EC or Super I/O chip is used in your laptop (may be some info in Service Manuals or Disassembly guides)<br />
* if you see that ectool return some fake staff - like only 'FF' or '00' - so you have custom EC configuration, it's a hard work for support<br />
* if you see that ectool return looks like 'right' output - you have a big chances for support<br />
* you need to find from thease outputs Super I/O / EC chip name, or if not see this - disassembly your laptop<br />
* try to find your Super I/O / EC chip datasheet<br />
<br />
== Laptop survey ==<br />
<br />
This not a list of coreboot supported laptops. This page only lists the chipsets, Super I/Os, flash chips, and especially [[embedded controller]]s used in a few laptops, just for reference purposes.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset NB<br />
! align="left" | Chipset SB<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | [[Embedded controller|EC]]<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash S.<br />
! align="left" | Flash T.<br />
! align="left" | Owner<br />
<br />
|- bgcolor="#dddddd"<br />
| ASUS || S96F/Z96F || Intel&nbsp;Core&trade;2 Duo T7400 || Intel&nbsp;i945 || Intel ICH7 || ITE IT8510E || in Super I/O || ? || ? || ? || ? || [http://www.flashrom.org/pipermail/flashrom/2010-January/001986.html macavity]<br />
|- bgcolor="#eeeeee"<br />
| Acer || Aspire One ZG5 || Intel Atom N270 1.6GHz || Intel 82945GME || Intel NH82801GBM ICH7-M || Winbond WPCE775LA0DG || in Super I/O || Winbond 25x80AVSIG || 8Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Acer || Aspire 3613LC || Intel Celeron M 370 1.5GHz L2: 1MB || Intel 82910GML || Intel FW82801FBM SL7W6 ICH6-M || ? || ? || PMC 0537 PM39LV040-70JCE || 1Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX |||| SMSC&nbsp;FDC37N958FR || in Super I/O || AMD AM29F040B || 512KB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude C610|Latitude C610]] || PIII, 1.2 GHz || Intel i830 |||| SMSC&nbsp;LPC47N252 || in Super I/O || SST SST49LF004A || 512KB || no || PLCC || [mailto:coreboot@miradou.com CybFr]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Vostro V13]] || Intel Celeron 743 1.2GHz, L2: 1MB (Ultra Low Voltage) || Mobile Intel GS45 Express GHMC ||Intel 82801IEM ICH9M-E|| none || ITE IT8502E || Winbond 25Q16BVSIG || 2Mb || no || SOIP/PDIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Dell || XPS M1530 || Intel&nbsp;Core&trade;2 Duo T7700 || Intel PM965 || Intel ICH8 || none || Winbond WPC8763L || Winbond 25X16VSIG || 16Mb || ?? || SPI || Corey Osgood<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-S. || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX |||| SMSC FDC37N769 || ? || Fujitsu&nbsp;MBM29F400T<sup>1</sup> || ? || no || TSOP(?) || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Fujitsu-S. || Lifebook S7110 || Intel&nbsp;Core&trade;2 Duo T7200 || Intel&nbsp;i945 || Intel ICH7 || SMSC&nbsp;LPC47N217 || Fujitsu MB90378 || Spansion S25FL008A<sup>2</sup> || 1024 kB || no || SO8 / SPI || twice11<br />
|- bgcolor="#eeeeee"<br />
| Gateway || [[Gateway W730-K8X | W730-K8X]] || Socket 754 |||| ?? || ?? || ?? || SST 39VF040 || ?? || yes || PLCC || [[User:Juri|Juri]]<br />
|- bgcolor="#dddddd"<br />
| Gateway || [[Gateway 6020GZ|6020GZ]] || Celeron M 1.4Ghz || Intel 855GME |||| ?? || ?? || ?? || ?? || no || ?? || [[User:Juri|Juri]]<br />
|- bgcolor="#eeeeee"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 |||| NSC PC87393VJG || NSC PC87570 || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || [http://thread.gmane.org/gmane.linux.bios/13081 NS]<br />
|- bgcolor="#dddddd"<br />
| Getac || P470 || Intel&reg;&nbsp;Core 2 Duo Mobile || Intel 945 || Intel ICH7 || ? || ? || ? || 8Mb || no || SPI / SOIC8 || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel&nbsp;Celeron&nbsp;1.7&nbsp;GHz || SiS650 |||| NSC&nbsp;PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel&nbsp;82371MB ||Intel PIIX4M || SMSC&nbsp;FDC37N869 || NSC&nbsp;PC87570 || SST 28SF040A || 512 kB || no || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| IBM || Thinkpad T30 || Intel P4 Mobile, 1.8 GHz || Intel&nbsp;i845 || Intel ICH3-M || NSC&nbsp;PC87392 || Renesas H8S&nbsp;64F3169ATE10 || ST&nbsp;M50FW080N5 || 1024 kB || no || TSOP40 / FWH || edgecase<br />
|- bgcolor="#dddddd"<br />
| IBM || Thinkpad X60s || Intel Core Duo CPU L2300 || Intel&nbsp;i945GM || Intel ICH7-M || NSC&nbsp;PC87392 (in Ultrabase) || Renesas H8S2161B || MX25L1605D || 2048 kB || no || SOIC-8 || [[User:SvenS|Sven Schnelle]]<br />
|- bgcolor="#dddddd"<br />
| MSI || Wind U100 || Intel Atom N280 1.66Ghz || Intel 945GSE || Intel ICH7-M || ? || ENE KB3310 || SST MX25L8005 || 8 Mb|| no || TSOP40 / SPI || ?<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110] || VIA&nbsp;C7-M&nbsp;ULV&nbsp;1.0&nbsp;GHz || VIA VX800 |||| none || ENE KB3310 || ? || ? || no || ? || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Panasonic || Toughbook&nbsp;CF-25 || P166MMX || FW82439TX&nbsp;(430TX) || FW82371AB || NSC PC87336VJG || Renesas&nbsp;3886 || SST SST29EE020 || 256 kB || no || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Roda || Rocky III+ RK886EX || Intel&reg;&nbsp;Core 2 Duo Mobile T5500 || Intel 945 || Intel ICH7 || SMSC&reg;&nbsp;LPC47N227 || Renesas&nbsp;M38859 || SST SST49LF080 || 8Mb || yes || PLCC || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#dddddd"<br />
| Roda || Rocky II+ RT686 || Intel&nbsp;Pentium III || Intel 430BX || Intel FW82371EB || SMSC&reg;&nbsp;FDC37N769 || Renesas&nbsp;M38867M8A || SST SST29LE020 || 256KB || yes || PLCC/parallel || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1XD || P2 400 || 443ZX |||| ? || ? || ST M29W004BT || 512 kB || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1X || P266MMX || 430TX |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Satellite&nbsp;A80-117 || Intel&nbsp;Celeron || Intel&nbsp;915GM || Intel ICH6 || SMSC&nbsp;LPC47N217 || ENE KB910 || ? || 1024 kB || no || TSOP (?) || [[User:Uwe|UH]]<br />
<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br /><br />
<sup>2</sup> Nice thing: EC/Flash is not shared, so you can erase the whole flash during system operation (this was tested).<br /><br />
</small><br />
<br />
Further links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Mailinglist discussion ==<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
* [http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]<br />
<br />
== Random product links ==<br />
<br />
The following list is a few years old. Most if not all of these laptops are no longer available. It is only here for reference purposes.<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
Netbook designs that use the VIA vx700 chipset:<br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
AMD 690/600 laptops: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=10897Laptop2011-10-03T18:51:48Z<p>Bari: /* Laptop survey */</p>
<hr />
<div>== Recent progress of coreboot on laptops ==<br />
<br />
* coreboot supports the [http://en.getac.com/products/P470/P470_overview.html Getac P470] semi rugged notebook, based on Intel 82945GM/ICH7.<br />
* coreboot supports the [http://www.roda-computer.com/en/products/notebooks/rocky-iii-rk886ex.html Roda RK886EX (Rocky III+)] laptop, based on Intel 82945GM/ICH7.<br />
* VIA has recently released open documentation for the VX700 and VX800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal].<br />
* coreboot supports one variant of the Lenovo [[Thinkpad X60s]].<br />
<br />
== Embedded controllers ==<br />
<br />
The remaining issue with supporting netbooks may be open firmware support for the [[Embedded controller]] (EC).<br />
These ECs used to support keyboard scan, lid open/closed, battery charging, power management, etc.<br />
<br />
coreboot should work with the "stock" EC firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)?<br />
<br />
== HOWTO to find a way ==<br />
<br />
* find a model and manufacturer of your laptop<br />
* download these tools:<br />
# superiotool ( svn co svn://coreboot.org/coreboot/trunk/util/superiotool )<br />
# inteltool ( svn co svn://coreboot.org/coreboot/trunk/util/inteltool )<br />
# ectool ( svn co svn://coreboot.org/coreboot/trunk/util/ectool )<br />
# dmidecode ( cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/dmidecode co dmidecode )<br />
# msrtool (svn co svn://coreboot.org/coreboot/trunk/util/msrtool )<br />
# nvramtool ( svn co svn://coreboot.org/coreboot/trunk/util/nvramtool )<br />
# flashrom ( svn co svn://coreboot.org/flashrom/trunk flashrom )<br />
* make and install them (make; sudo make install) - you need at least libpci/pciutils<br />
* check that your distro have this tools and install them:<br />
# lspci<br />
# dmesg<br />
# acpitool<br />
# lspnp<br />
# lsusb<br />
* Do this commands:<br />
# lspci -nnvvvxxxx > lscpi.log<br />
# lspnp -vv > lspnp.log<br />
# lsusb -vvv > lsusb.log<br />
# superiotool -deV > superiotool.log<br />
# inteltool -a > inteltool.log<br />
# ectool > ectool.log<br />
# msrtool > msrtool.log<br />
# dmidecode > dmidecode.log<br />
# biosdecode > biosdecode.log<br />
# nvramtool -x > nvramtool.log<br />
# dmesg > dmesg.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick > flashrom_info.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick -r rom.bin > flashrom_read.log<br />
* Save all logs in safe place, and also rom.bin file. <br />
* try to find information - what EC or Super I/O chip is used in your laptop (may be some info in Service Manuals or Disassembly guides)<br />
* if you see that ectool return some fake staff - like only 'FF' or '00' - so you have custom EC configuration, it's a hard work for support<br />
* if you see that ectool return looks like 'right' output - you have a big chances for support<br />
* you need to find from thease outputs Super I/O / EC chip name, or if not see this - disassembly your laptop<br />
* try to find your Super I/O / EC chip datasheet<br />
<br />
== Laptop survey ==<br />
<br />
This not a list of coreboot supported laptops. This page only lists the chipsets, Super I/Os, flash chips, and especially [[embedded controller]]s used in a few laptops, just for reference purposes.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset NB<br />
! align="left" | Chipset SB<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | [[Embedded controller|EC]]<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash S.<br />
! align="left" | Flash T.<br />
! align="left" | Owner<br />
<br />
|- bgcolor="#dddddd"<br />
| ASUS || S96F/Z96F || Intel&nbsp;Core&trade;2 Duo T7400 || Intel&nbsp;i945 || Intel ICH7 || ITE IT8510E || in Super I/O || ? || ? || ? || ? || [http://www.flashrom.org/pipermail/flashrom/2010-January/001986.html macavity]<br />
|- bgcolor="#eeeeee"<br />
| Acer || Aspire One ZG5 || Intel Atom N270 1.6GHz || Intel 82945GME || Intel NH82801GBM ICH7-M || Winbond WPCE775LA0DG || in Super I/O || Winbond 25x80AVSIG || 8Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Acer || Aspire 3613LC || Intel Celeron M 370 1.5GHz L2: 1MB || Intel 82910GML || Intel FW82801FBM SL7W6 ICH6-M || ? || ? || PMC 0537 PM39LV040-70JCE || 1Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX |||| SMSC&nbsp;FDC37N958FR || in Super I/O || AMD AM29F040B || 512KB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude C610|Latitude C610]] || PIII, 1.2 GHz || Intel i830 |||| SMSC&nbsp;LPC47N252 || in Super I/O || SST SST49LF004A || 512KB || no || PLCC || [mailto:coreboot@miradou.com CybFr]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Vostro V13]] || Intel Celeron 743 1.2GHz, L2: 1MB (Ultra Low Voltage) || Mobile Intel GS45 Express GHMC ||Intel 82801IEM ICH9M-E|| none || ITE IT8502E || Winbond 25Q16BVSIG || 2Mb || no || SOIP/PDIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Dell || XPS M1530 || Intel&nbsp;Core&trade;2 Duo T7700 || Intel PM965 || Intel ICH8 || none || Winbond WPC8763L || Winbond 25X16VSIG || 16Mb || ?? || SPI || Corey Osgood<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-S. || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX |||| SMSC FDC37N769 || ? || Fujitsu&nbsp;MBM29F400T<sup>1</sup> || ? || no || TSOP(?) || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Fujitsu-S. || Lifebook S7110 || Intel&nbsp;Core&trade;2 Duo T7200 || Intel&nbsp;i945 || Intel ICH7 || SMSC&nbsp;LPC47N217 || Fujitsu MB90378 || Spansion S25FL008A<sup>2</sup> || 1024 kB || no || SO8 / SPI || twice11<br />
|- bgcolor="#eeeeee"<br />
| Gateway || [[Gateway W730-K8X | W730-K8X]] || Socket 754 |||| ?? || ?? || ?? || SST 39VF040 || ?? || yes || PLCC || [[User:Juri|Juri]]<br />
|- bgcolor="#dddddd"<br />
| Gateway || [[Gateway 6020GZ|6020GZ]] || Celeron M 1.4Ghz || Intel 855GME |||| ?? || ?? || ?? || ?? || no || ?? || [[User:Juri|Juri]]<br />
|- bgcolor="#eeeeee"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 |||| NSC PC87393VJG || NSC PC87570 || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || [http://thread.gmane.org/gmane.linux.bios/13081 NS]<br />
|- bgcolor="#dddddd"<br />
| Getac || P470 || Intel&reg;&nbsp;Core 2 Duo Mobile || Intel 945 || Intel ICH7 || ? || ? || ? || 8Mb || no || SPI / SOIC8 || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel&nbsp;Celeron&nbsp;1.7&nbsp;GHz || SiS650 |||| NSC&nbsp;PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel&nbsp;82371MB ||Intel PIIX4M || SMSC&nbsp;FDC37N869 || NSC&nbsp;PC87570 || SST 28SF040A || 512 kB || no || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| IBM || Thinkpad T30 || Intel P4 Mobile, 1.8 GHz || Intel&nbsp;i845 || Intel ICH3-M || NSC&nbsp;PC87392 || Renesas H8S&nbsp;64F3169ATE10 || ST&nbsp;M50FW080N5 || 1024 kB || no || TSOP40 / FWH || edgecase<br />
|- bgcolor="#dddddd"<br />
| IBM || Thinkpad X60s || Intel Core Duo CPU L2300 || Intel&nbsp;i945GM || Intel ICH7-M || NSC&nbsp;PC87392 (in Ultrabase) || Renesas H8S2161B || MX25L1605D || 2048 kB || no || SOIC-8 || [[User:SvenS|Sven Schnelle]]<br />
|- bgcolor="#dddddd"<br />
| MSI || Wind U100 || Intel Atom N280 1.66Ghz || Intel 945GSE || Intel ICH7-M || ? || ENE KB3310 || SST MX25L8005 || 8 Mb|| no || TSOP40 / SPI || ?<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110] || VIA&nbsp;C7-M&nbsp;ULV&nbsp;1.0&nbsp;GHz || VIA VX800 |||| none || ENE KB3310 || ? || ? || no || ? || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Panasonic || Toughbook&nbsp;CF-25 || P166MMX || FW82439TX&nbsp;(430TX) || FW82371AB || NSC PC87336VJG || Renesas&nbsp;3886 || SST SST29EE020 || 256 kB || no || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Roda || Rocky III+ RK886EX || Intel&reg;&nbsp;Core 2 Duo Mobile T5500 || Intel 945 || Intel ICH7 || SMSC&reg;&nbsp;LPC47N227 || Renesas&nbsp;M38859 || SST SST49LF080 || 8Mb || yes || PLCC || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#dddddd"<br />
| Roda || Rocky II+ RT686 || Intel&nbsp;Pentium III || Intel 430BX || Intel FW82371EB || SMSC&reg;&nbsp;FDC37N769 || Renesas&nbsp;M38867M8A || SST SST29LE020 || 256KB || yes || PLCC/parallel || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1XD || P2 400 || 443ZX |||| ? || ? || ST M29W004BT || 512 kB || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1X || P266MMX || 430TX |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Satellite&nbsp;A80-117 || Intel&nbsp;Celeron || Intel&nbsp;915GM || Intel ICH6 || SMSC&nbsp;LPC47N217 || ENE KB910 || ? || 1024 kB || no || TSOP (?) || [[User:Uwe|UH]]<br />
<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br /><br />
<sup>2</sup> Nice thing: EC/Flash is not shared, so you can erase the whole flash during system operation (this was tested).<br /><br />
</small><br />
<br />
Further links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Mailinglist discussion ==<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
* [http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]<br />
<br />
== Random product links ==<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
Netbook designs that use the VIA vx700 chipset:<br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=10896Laptop2011-10-03T18:49:29Z<p>Bari: /* Laptop survey */</p>
<hr />
<div>== Recent progress of coreboot on laptops ==<br />
<br />
* coreboot supports the [http://en.getac.com/products/P470/P470_overview.html Getac P470] semi rugged notebook, based on Intel 82945GM/ICH7.<br />
* coreboot supports the [http://www.roda-computer.com/en/products/notebooks/rocky-iii-rk886ex.html Roda RK886EX (Rocky III+)] laptop, based on Intel 82945GM/ICH7.<br />
* VIA has recently released open documentation for the VX700 and VX800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal].<br />
* coreboot supports one variant of the Lenovo [[Thinkpad X60s]].<br />
<br />
== Embedded controllers ==<br />
<br />
The remaining issue with supporting netbooks may be open firmware support for the [[Embedded controller]] (EC).<br />
These ECs used to support keyboard scan, lid open/closed, battery charging, power management, etc.<br />
<br />
coreboot should work with the "stock" EC firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)?<br />
<br />
== HOWTO to find a way ==<br />
<br />
* find a model and manufacturer of your laptop<br />
* download these tools:<br />
# superiotool ( svn co svn://coreboot.org/coreboot/trunk/util/superiotool )<br />
# inteltool ( svn co svn://coreboot.org/coreboot/trunk/util/inteltool )<br />
# ectool ( svn co svn://coreboot.org/coreboot/trunk/util/ectool )<br />
# dmidecode ( cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/dmidecode co dmidecode )<br />
# msrtool (svn co svn://coreboot.org/coreboot/trunk/util/msrtool )<br />
# nvramtool ( svn co svn://coreboot.org/coreboot/trunk/util/nvramtool )<br />
# flashrom ( svn co svn://coreboot.org/flashrom/trunk flashrom )<br />
* make and install them (make; sudo make install) - you need at least libpci/pciutils<br />
* check that your distro have this tools and install them:<br />
# lspci<br />
# dmesg<br />
# acpitool<br />
# lspnp<br />
# lsusb<br />
* Do this commands:<br />
# lspci -nnvvvxxxx > lscpi.log<br />
# lspnp -vv > lspnp.log<br />
# lsusb -vvv > lsusb.log<br />
# superiotool -deV > superiotool.log<br />
# inteltool -a > inteltool.log<br />
# ectool > ectool.log<br />
# msrtool > msrtool.log<br />
# dmidecode > dmidecode.log<br />
# biosdecode > biosdecode.log<br />
# nvramtool -x > nvramtool.log<br />
# dmesg > dmesg.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick > flashrom_info.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick -r rom.bin > flashrom_read.log<br />
* Save all logs in safe place, and also rom.bin file. <br />
* try to find information - what EC or Super I/O chip is used in your laptop (may be some info in Service Manuals or Disassembly guides)<br />
* if you see that ectool return some fake staff - like only 'FF' or '00' - so you have custom EC configuration, it's a hard work for support<br />
* if you see that ectool return looks like 'right' output - you have a big chances for support<br />
* you need to find from thease outputs Super I/O / EC chip name, or if not see this - disassembly your laptop<br />
* try to find your Super I/O / EC chip datasheet<br />
<br />
== Laptop survey ==<br />
<br />
This page lists the chipsets, Super I/Os, flash chips, and especially [[embedded controller]]s used in various laptops.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset NB<br />
! align="left" | Chipset SB<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | [[Embedded controller|EC]]<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash S.<br />
! align="left" | Flash T.<br />
! align="left" | Owner<br />
<br />
|- bgcolor="#dddddd"<br />
| ASUS || S96F/Z96F || Intel&nbsp;Core&trade;2 Duo T7400 || Intel&nbsp;i945 || Intel ICH7 || ITE IT8510E || in Super I/O || ? || ? || ? || ? || [http://www.flashrom.org/pipermail/flashrom/2010-January/001986.html macavity]<br />
|- bgcolor="#eeeeee"<br />
| Acer || Aspire One ZG5 || Intel Atom N270 1.6GHz || Intel 82945GME || Intel NH82801GBM ICH7-M || Winbond WPCE775LA0DG || in Super I/O || Winbond 25x80AVSIG || 8Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Acer || Aspire 3613LC || Intel Celeron M 370 1.5GHz L2: 1MB || Intel 82910GML || Intel FW82801FBM SL7W6 ICH6-M || ? || ? || PMC 0537 PM39LV040-70JCE || 1Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX |||| SMSC&nbsp;FDC37N958FR || in Super I/O || AMD AM29F040B || 512KB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude C610|Latitude C610]] || PIII, 1.2 GHz || Intel i830 |||| SMSC&nbsp;LPC47N252 || in Super I/O || SST SST49LF004A || 512KB || no || PLCC || [mailto:coreboot@miradou.com CybFr]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Vostro V13]] || Intel Celeron 743 1.2GHz, L2: 1MB (Ultra Low Voltage) || Mobile Intel GS45 Express GHMC ||Intel 82801IEM ICH9M-E|| none || ITE IT8502E || Winbond 25Q16BVSIG || 2Mb || no || SOIP/PDIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Dell || XPS M1530 || Intel&nbsp;Core&trade;2 Duo T7700 || Intel PM965 || Intel ICH8 || none || Winbond WPC8763L || Winbond 25X16VSIG || 16Mb || ?? || SPI || Corey Osgood<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-S. || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX |||| SMSC FDC37N769 || ? || Fujitsu&nbsp;MBM29F400T<sup>1</sup> || ? || no || TSOP(?) || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Fujitsu-S. || Lifebook S7110 || Intel&nbsp;Core&trade;2 Duo T7200 || Intel&nbsp;i945 || Intel ICH7 || SMSC&nbsp;LPC47N217 || Fujitsu MB90378 || Spansion S25FL008A<sup>2</sup> || 1024 kB || no || SO8 / SPI || twice11<br />
|- bgcolor="#eeeeee"<br />
| Gateway || [[Gateway W730-K8X | W730-K8X]] || Socket 754 |||| ?? || ?? || ?? || SST 39VF040 || ?? || yes || PLCC || [[User:Juri|Juri]]<br />
|- bgcolor="#dddddd"<br />
| Gateway || [[Gateway 6020GZ|6020GZ]] || Celeron M 1.4Ghz || Intel 855GME |||| ?? || ?? || ?? || ?? || no || ?? || [[User:Juri|Juri]]<br />
|- bgcolor="#eeeeee"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 |||| NSC PC87393VJG || NSC PC87570 || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || [http://thread.gmane.org/gmane.linux.bios/13081 NS]<br />
|- bgcolor="#dddddd"<br />
| Getac || P470 || Intel&reg;&nbsp;Core 2 Duo Mobile || Intel 945 || Intel ICH7 || ? || ? || ? || 8Mb || no || SPI / SOIC8 || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel&nbsp;Celeron&nbsp;1.7&nbsp;GHz || SiS650 |||| NSC&nbsp;PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel&nbsp;82371MB ||Intel PIIX4M || SMSC&nbsp;FDC37N869 || NSC&nbsp;PC87570 || SST 28SF040A || 512 kB || no || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| IBM || Thinkpad T30 || Intel P4 Mobile, 1.8 GHz || Intel&nbsp;i845 || Intel ICH3-M || NSC&nbsp;PC87392 || Renesas H8S&nbsp;64F3169ATE10 || ST&nbsp;M50FW080N5 || 1024 kB || no || TSOP40 / FWH || edgecase<br />
|- bgcolor="#dddddd"<br />
| IBM || Thinkpad X60s || Intel Core Duo CPU L2300 || Intel&nbsp;i945GM || Intel ICH7-M || NSC&nbsp;PC87392 (in Ultrabase) || Renesas H8S2161B || MX25L1605D || 2048 kB || no || SOIC-8 || [[User:SvenS|Sven Schnelle]]<br />
|- bgcolor="#dddddd"<br />
| MSI || Wind U100 || Intel Atom N280 1.66Ghz || Intel 945GSE || Intel ICH7-M || ? || ENE KB3310 || SST MX25L8005 || 8 Mb|| no || TSOP40 / SPI || ?<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110] || VIA&nbsp;C7-M&nbsp;ULV&nbsp;1.0&nbsp;GHz || VIA VX800 |||| none || ENE KB3310 || ? || ? || no || ? || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Panasonic || Toughbook&nbsp;CF-25 || P166MMX || FW82439TX&nbsp;(430TX) || FW82371AB || NSC PC87336VJG || Renesas&nbsp;3886 || SST SST29EE020 || 256 kB || no || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Roda || Rocky III+ RK886EX || Intel&reg;&nbsp;Core 2 Duo Mobile T5500 || Intel 945 || Intel ICH7 || SMSC&reg;&nbsp;LPC47N227 || Renesas&nbsp;M38859 || SST SST49LF080 || 8Mb || yes || PLCC || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#dddddd"<br />
| Roda || Rocky II+ RT686 || Intel&nbsp;Pentium III || Intel 430BX || Intel FW82371EB || SMSC&reg;&nbsp;FDC37N769 || Renesas&nbsp;M38867M8A || SST SST29LE020 || 256KB || yes || PLCC/parallel || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1XD || P2 400 || 443ZX |||| ? || ? || ST M29W004BT || 512 kB || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1X || P266MMX || 430TX |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Satellite&nbsp;A80-117 || Intel&nbsp;Celeron || Intel&nbsp;915GM || Intel ICH6 || SMSC&nbsp;LPC47N217 || ENE KB910 || ? || 1024 kB || no || TSOP (?) || [[User:Uwe|UH]]<br />
<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br /><br />
<sup>2</sup> Nice thing: EC/Flash is not shared, so you can erase the whole flash during system operation (this was tested).<br /><br />
</small><br />
<br />
Further links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Mailinglist discussion ==<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
* [http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]<br />
<br />
== Random product links ==<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
Netbook designs that use the VIA vx700 chipset:<br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=10895Laptop2011-10-03T18:47:58Z<p>Bari: /* Random product links */</p>
<hr />
<div>== Recent progress of coreboot on laptops ==<br />
<br />
* coreboot supports the [http://en.getac.com/products/P470/P470_overview.html Getac P470] semi rugged notebook, based on Intel 82945GM/ICH7.<br />
* coreboot supports the [http://www.roda-computer.com/en/products/notebooks/rocky-iii-rk886ex.html Roda RK886EX (Rocky III+)] laptop, based on Intel 82945GM/ICH7.<br />
* VIA has recently released open documentation for the VX700 and VX800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal].<br />
* coreboot supports one variant of the Lenovo [[Thinkpad X60s]].<br />
<br />
== Embedded controllers ==<br />
<br />
The remaining issue with supporting netbooks may be open firmware support for the [[Embedded controller]] (EC).<br />
These ECs used to support keyboard scan, lid open/closed, battery charging, power management, etc.<br />
<br />
coreboot should work with the "stock" EC firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)?<br />
<br />
== HOWTO to find a way ==<br />
<br />
* find a model and manufacturer of your laptop<br />
* download these tools:<br />
# superiotool ( svn co svn://coreboot.org/coreboot/trunk/util/superiotool )<br />
# inteltool ( svn co svn://coreboot.org/coreboot/trunk/util/inteltool )<br />
# ectool ( svn co svn://coreboot.org/coreboot/trunk/util/ectool )<br />
# dmidecode ( cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/dmidecode co dmidecode )<br />
# msrtool (svn co svn://coreboot.org/coreboot/trunk/util/msrtool )<br />
# nvramtool ( svn co svn://coreboot.org/coreboot/trunk/util/nvramtool )<br />
# flashrom ( svn co svn://coreboot.org/flashrom/trunk flashrom )<br />
* make and install them (make; sudo make install) - you need at least libpci/pciutils<br />
* check that your distro have this tools and install them:<br />
# lspci<br />
# dmesg<br />
# acpitool<br />
# lspnp<br />
# lsusb<br />
* Do this commands:<br />
# lspci -nnvvvxxxx > lscpi.log<br />
# lspnp -vv > lspnp.log<br />
# lsusb -vvv > lsusb.log<br />
# superiotool -deV > superiotool.log<br />
# inteltool -a > inteltool.log<br />
# ectool > ectool.log<br />
# msrtool > msrtool.log<br />
# dmidecode > dmidecode.log<br />
# biosdecode > biosdecode.log<br />
# nvramtool -x > nvramtool.log<br />
# dmesg > dmesg.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick > flashrom_info.log<br />
# flashrom -V -p internal:laptop=force_I_want_a_brick -r rom.bin > flashrom_read.log<br />
* Save all logs in safe place, and also rom.bin file. <br />
* try to find information - what EC or Super I/O chip is used in your laptop (may be some info in Service Manuals or Disassembly guides)<br />
* if you see that ectool return some fake staff - like only 'FF' or '00' - so you have custom EC configuration, it's a hard work for support<br />
* if you see that ectool return looks like 'right' output - you have a big chances for support<br />
* you need to find from thease outputs Super I/O / EC chip name, or if not see this - disassembly your laptop<br />
* try to find your Super I/O / EC chip datasheet<br />
<br />
== Laptop survey ==<br />
<br />
This page attempts to list chipsets, Super I/Os, flash chips, and especially [[embedded controller]]s used in various laptops.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset NB<br />
! align="left" | Chipset SB<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | [[Embedded controller|EC]]<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash S.<br />
! align="left" | Flash T.<br />
! align="left" | Owner<br />
<br />
|- bgcolor="#dddddd"<br />
| ASUS || S96F/Z96F || Intel&nbsp;Core&trade;2 Duo T7400 || Intel&nbsp;i945 || Intel ICH7 || ITE IT8510E || in Super I/O || ? || ? || ? || ? || [http://www.flashrom.org/pipermail/flashrom/2010-January/001986.html macavity]<br />
|- bgcolor="#eeeeee"<br />
| Acer || Aspire One ZG5 || Intel Atom N270 1.6GHz || Intel 82945GME || Intel NH82801GBM ICH7-M || Winbond WPCE775LA0DG || in Super I/O || Winbond 25x80AVSIG || 8Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Acer || Aspire 3613LC || Intel Celeron M 370 1.5GHz L2: 1MB || Intel 82910GML || Intel FW82801FBM SL7W6 ICH6-M || ? || ? || PMC 0537 PM39LV040-70JCE || 1Mb || no || SOIP/DIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX |||| SMSC&nbsp;FDC37N958FR || in Super I/O || AMD AM29F040B || 512KB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude C610|Latitude C610]] || PIII, 1.2 GHz || Intel i830 |||| SMSC&nbsp;LPC47N252 || in Super I/O || SST SST49LF004A || 512KB || no || PLCC || [mailto:coreboot@miradou.com CybFr]<br />
|- bgcolor="#eeeeee"<br />
| Dell || [[Dell Vostro V13]] || Intel Celeron 743 1.2GHz, L2: 1MB (Ultra Low Voltage) || Mobile Intel GS45 Express GHMC ||Intel 82801IEM ICH9M-E|| none || ITE IT8502E || Winbond 25Q16BVSIG || 2Mb || no || SOIP/PDIP || [[User:XVilka|XVilka]]<br />
|- bgcolor="#dddddd"<br />
| Dell || XPS M1530 || Intel&nbsp;Core&trade;2 Duo T7700 || Intel PM965 || Intel ICH8 || none || Winbond WPC8763L || Winbond 25X16VSIG || 16Mb || ?? || SPI || Corey Osgood<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-S. || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX |||| SMSC FDC37N769 || ? || Fujitsu&nbsp;MBM29F400T<sup>1</sup> || ? || no || TSOP(?) || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Fujitsu-S. || Lifebook S7110 || Intel&nbsp;Core&trade;2 Duo T7200 || Intel&nbsp;i945 || Intel ICH7 || SMSC&nbsp;LPC47N217 || Fujitsu MB90378 || Spansion S25FL008A<sup>2</sup> || 1024 kB || no || SO8 / SPI || twice11<br />
|- bgcolor="#eeeeee"<br />
| Gateway || [[Gateway W730-K8X | W730-K8X]] || Socket 754 |||| ?? || ?? || ?? || SST 39VF040 || ?? || yes || PLCC || [[User:Juri|Juri]]<br />
|- bgcolor="#dddddd"<br />
| Gateway || [[Gateway 6020GZ|6020GZ]] || Celeron M 1.4Ghz || Intel 855GME |||| ?? || ?? || ?? || ?? || no || ?? || [[User:Juri|Juri]]<br />
|- bgcolor="#eeeeee"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 |||| NSC PC87393VJG || NSC PC87570 || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || [http://thread.gmane.org/gmane.linux.bios/13081 NS]<br />
|- bgcolor="#dddddd"<br />
| Getac || P470 || Intel&reg;&nbsp;Core 2 Duo Mobile || Intel 945 || Intel ICH7 || ? || ? || ? || 8Mb || no || SPI / SOIC8 || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel&nbsp;Celeron&nbsp;1.7&nbsp;GHz || SiS650 |||| NSC&nbsp;PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel&nbsp;82371MB ||Intel PIIX4M || SMSC&nbsp;FDC37N869 || NSC&nbsp;PC87570 || SST 28SF040A || 512 kB || no || PLCC || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| IBM || Thinkpad T30 || Intel P4 Mobile, 1.8 GHz || Intel&nbsp;i845 || Intel ICH3-M || NSC&nbsp;PC87392 || Renesas H8S&nbsp;64F3169ATE10 || ST&nbsp;M50FW080N5 || 1024 kB || no || TSOP40 / FWH || edgecase<br />
|- bgcolor="#dddddd"<br />
| IBM || Thinkpad X60s || Intel Core Duo CPU L2300 || Intel&nbsp;i945GM || Intel ICH7-M || NSC&nbsp;PC87392 (in Ultrabase) || Renesas H8S2161B || MX25L1605D || 2048 kB || no || SOIC-8 || [[User:SvenS|Sven Schnelle]]<br />
|- bgcolor="#dddddd"<br />
| MSI || Wind U100 || Intel Atom N280 1.66Ghz || Intel 945GSE || Intel ICH7-M || ? || ENE KB3310 || SST MX25L8005 || 8 Mb|| no || TSOP40 / SPI || ?<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110] || VIA&nbsp;C7-M&nbsp;ULV&nbsp;1.0&nbsp;GHz || VIA VX800 |||| none || ENE KB3310 || ? || ? || no || ? || [[User:Uwe|UH]]<br />
|- bgcolor="#dddddd"<br />
| Panasonic || Toughbook&nbsp;CF-25 || P166MMX || FW82439TX&nbsp;(430TX) || FW82371AB || NSC PC87336VJG || Renesas&nbsp;3886 || SST SST29EE020 || 256 kB || no || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Roda || Rocky III+ RK886EX || Intel&reg;&nbsp;Core 2 Duo Mobile T5500 || Intel 945 || Intel ICH7 || SMSC&reg;&nbsp;LPC47N227 || Renesas&nbsp;M38859 || SST SST49LF080 || 8Mb || yes || PLCC || [[User:Stepan|Stefan Reinauer]]<br />
|- bgcolor="#dddddd"<br />
| Roda || Rocky II+ RT686 || Intel&nbsp;Pentium III || Intel 430BX || Intel FW82371EB || SMSC&reg;&nbsp;FDC37N769 || Renesas&nbsp;M38867M8A || SST SST29LE020 || 256KB || yes || PLCC/parallel || [[User:Uwe|UH]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1XD || P2 400 || 443ZX |||| ? || ? || ST M29W004BT || 512 kB || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Sony || Vaio&nbsp;Picturebook&nbsp;PCG-C1X || P266MMX || 430TX |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA |||| ? || ? || ? || ? || ? || ? || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Satellite&nbsp;A80-117 || Intel&nbsp;Celeron || Intel&nbsp;915GM || Intel ICH6 || SMSC&nbsp;LPC47N217 || ENE KB910 || ? || 1024 kB || no || TSOP (?) || [[User:Uwe|UH]]<br />
<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br /><br />
<sup>2</sup> Nice thing: EC/Flash is not shared, so you can erase the whole flash during system operation (this was tested).<br /><br />
</small><br />
<br />
Further links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Mailinglist discussion ==<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
* [http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
* [http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]<br />
<br />
== Random product links ==<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
Netbook designs that use the VIA vx700 chipset:<br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10887ARM2011-08-16T13:41:01Z<p>Bari: /* Platforms */ added SBC-A510</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10886ARM2011-08-02T15:39:22Z<p>Bari: </p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10885ARM2011-08-02T15:28:57Z<p>Bari: changed marvell to VersatilePB from Armltd as the first supported platform</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10810ARM2011-06-09T14:53:00Z<p>Bari: /* coreboot on ARM */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10809ARM2011-06-09T14:49:25Z<p>Bari: /* ARM SOC's */ added ZMS-20</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10808ARM2011-06-09T14:43:43Z<p>Bari: /* ARM SOC's */ added Panasonic UniPhier</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Developer_Manual&diff=10784Developer Manual2011-06-05T19:48:06Z<p>Bari: /* Supporting a new board with a unsupported cpu, chipset or superIO */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=VIA_EPIA-LN&diff=10782VIA EPIA-LN2011-06-05T04:22:07Z<p>Bari: /* Status */</p>
<hr />
<div>This page describes how to use coreboot on the '''VIA EPIA-LN''' mainboard.<br />
<br />
This page is a work in progress.<br />
<br />
== Status ==<br />
<br />
{{Status|<br />
<br />
|CPU_status = OK<br />
|CPU_comments = <br />
|CPU_L1_status = OK<br />
|CPU_L1_comments = Always on<br />
|CPU_L2_status = OK<br />
|CPU_L2_comments =Always on<br />
|CPU_L3_status = N/A<br />
|CPU_multiple_status = N/A<br />
|CPU_multicore_status = N/A<br />
|CPU_virt_status = N/A<br />
<br />
|RAM_EDO_status = N/A<br />
|RAM_SDRAM_status = N/A<br />
|RAM_SODIMM_status = N/A<br />
|RAM_DDR_status = N/A<br />
|RAM_DDR2_status = OK<br />
|RAM_DDR3_status = N/A<br />
|RAM_dualchannel_status = N/A<br />
|RAM_ecc_status = ?<br />
<br />
|IDE_status = OK<br />
|IDE_comments = <br />
|IDE_CF_status = OK<br />
|IDE_CF_comments = <br />
|IDE_25_status = N/A<br />
|CDROM_DVD_status = OK<br />
|CDROM_DVD_comments = <br />
|SATA_status = OK<br />
|SATA_comments = <br />
|USB_status = OK<br />
|USB_comments =<br />
|Onboard_VGA_status = OK <br />
|Onboard_VGA_comments = Openchrome is fine without vgabios or bochs<br />
|Onboard_ethernet_status = OK<br />
|Onboard_audio_status = OK<br />
|Onboard_modem_status = N/A<br />
|Onboard_firewire_status = N/A<br />
|Smartcard_status = N/A<br />
|Onboard_CF_status = N/A<br />
|Onboard_PCMCIA_status = N/A<br />
<br />
|ISA_cards_status = N/A<br />
|AMR_cards_status = N/A<br />
|AGP_cards_status = N/A<br />
|PCI_cards_status = OK<br />
|PCI_cards_comments =<br />
|PCIE_x1_status = N/A<br />
|PCIE_x1_comments = <br />
|PCIE_x2_status = N/A<br />
|PCIE_x4_status = N/A<br />
|PCIE_x8_status = N/A<br />
|PCIE_x16_status = N/A<br />
|PCIE_x16_comments = <br />
|PCIE_x32_status = N/A<br />
|HTX_status = N/A<br />
<br />
|Floppy_status = N/A<br />
|Floppy_comments = <br />
|COM1_status = OK<br />
|COM2_status = Not tested<br />
|PP_status = Not tested<br />
|PP_comments = <br />
|PS2_keyboard_status = OK<br />
|PS2_mouse_status = OK<br />
|Game_port_status = N/A<br />
|Game_port_comments = <br />
|IR_status = Not tested<br />
|Speaker_status = OK<br />
|DiskOnChip_status = NA<br />
<br />
|Sensors_status = Not tested<br />
|Sensors_comments = <br />
|Watchdog_status = OK<br />
|Watchdog_comments = <br />
|CAN_bus_status = N/A<br />
|CPUfreq_status = OK<br />
|CPUfreq_comments = <br />
|Powersave_status = N/A<br />
|ACPI_status = ?<br />
|ACPI_comments = <br />
|Reboot_status = OK<br />
|Poweroff_status = <br />
|LEDs_status = OK<br />
|LEDs_comments = <br />
|HPET_status = Not tested<br />
|HPET_comments = <br />
|RNG_status = N/A<br />
|WakeOnModem_status = Untested<br />
|WakeOnLAN_status = Untested<br />
|WakeOnKeyboard_status = Untested<br />
|WakeOnMouse_status = Untested<br />
|Flashrom_status = OK<br />
|Flashrom_comments = SST 512KB, 1MB, 2MB, PMC 512KB,<br />
<br />
}}<br />
<br />
== See also ==<br />
<br />
* http://www.coreboot.org/pipermail/coreboot/2008-February/030101.html (old status post)<br />
* http://www.coreboot.org/pipermail/coreboot/2008-May/034736.html (new patch which got committed later)<br />
<br />
<br />
{{PD-self}}</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10781ARM2011-06-05T04:17:58Z<p>Bari: /* ARM SOC's */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10780ARM2011-06-05T04:16:57Z<p>Bari: /* Platforms */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Support&diff=10777Support2011-06-04T00:55:43Z<p>Bari: </p>
<hr />
<div>= Is my mainboard supported? =<br />
<br />
There are several steps involved in finding out whether your mainboard is supported by coreboot, or if it would be easy to support.<br />
<br />
* First, check the [[Supported Motherboards]]. If your mainboard is in this list, you are lucky and you will be able to try coreboot.<br />
* If your mainboard is not mentioned here, you will have to know how to code C in order to proceed. If you don't, refrain from trying to get coreboot onto your system.<br />
* Next, you will have to do a lot of data gathering:<br />
** Check out your mainboard's chipset. Use lspci on Linux/*BSD to do this. Look at the host bridge and at the LPC bridge. If you find those in our list of [[Supported Chipsets and Devices]] a port might be easy.<br />
** If your chipset is supported, check out the SuperIO with [[Superiotool]]<br />
** Look for a board that has the same chipset and the same SuperIO and start from there. Make sure you have a backup solution in place to recover if something goes wrong. You can not use your vendor bios' recovery bootblock to do this.<br />
** See the [[Developer Manual]] for further information.<br />
<br />
= More Resources =<br />
* [[Laptop]] page with some information on data gathering.</div>Barihttps://www.coreboot.org/index.php?title=Support&diff=10776Support2011-06-04T00:54:41Z<p>Bari: /* Is my mainboard supported? */ added a link to the developer manual</p>
<hr />
<div>= Is my mainboard supported? =<br />
<br />
There are several steps involved in finding out whether your mainboard is supported by coreboot, or if it would be easy to support.<br />
<br />
* First, check the [[Supported Motherboards]]. If your mainboard is in this list, you are lucky and you will be able to try coreboot.<br />
* If your mainboard is not mentioned here, you will have to know how to code C in order to proceed. If you don't, refrain from trying to get coreboot onto your system.<br />
* Next, you will have to do a lot of data gathering:<br />
** Check out your mainboard's chipset. Use lspci on Linux/*BSD to do this. Look at the host bridge and at the LPC bridge. If you find those in our list of [[Supported Chipsets and Devices]] a port might be easy.<br />
** If your chipset is supported, check out the SuperIO with [[Superiotool]]<br />
** Look for a board that has the same chipset and the same SuperIO and start from there. Make sure you have a backup solution in place to recover if something goes wrong. You can not use your vendor bios' recovery bootblock to do this.<br />
** See the [http://www.coreboot.org/Developer_Manual Developer Manual] for further information.<br />
<br />
= More Resources =<br />
* [[Laptop]] page with some information on data gathering.</div>Barihttps://www.coreboot.org/index.php?title=Developer_Manual&diff=10775Developer Manual2011-06-04T00:48:05Z<p>Bari: /* How to support a new board */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Developer_Manual&diff=10774Developer Manual2011-06-04T00:42:23Z<p>Bari: /* Supporting a new board with a unsupported cpu, chipset or superIO */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10773ARM2011-06-03T21:06:52Z<p>Bari: /* Platforms */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Developer_Manual&diff=10771Developer Manual2011-06-03T20:12:12Z<p>Bari: added info on supporting new boards</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10743ARM2011-05-12T09:25:34Z<p>Bari: /* ARM SOC's */ added link to Samsung Exynos 4210</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
coreboot on ARM is a work-in-progress. coreboot currently does not support ARM.<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI, SAS, SATA and SCSI devices; fast boot times; and payload support.<br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/251211.jsp STMicroelectronics SPEAr1340 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
[http://www.caviumnetworks.com/ECONA_CNS3XXX.html Cavium Networks ECONA CNS3XXX]<br />
<br />
[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=844&partnum=Exynos%204210&xFmly_id=229 Samsung Exynos 4210 with PCIe]<br />
<br />
==Platforms==<br />
<br />
[http://www.globalscaletechnologies.com/t-openrdudetails.aspx OpenRD Ultimate]<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10742ARM2011-05-11T12:17:06Z<p>Bari: /* ARM SOC's */ added link to ST SPEAr1340</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
coreboot on ARM is a work-in-progress. coreboot currently does not support ARM.<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI, SAS, SATA and SCSI devices; fast boot times; and payload support.<br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/251211.jsp STMicroelectronics SPEAr1340 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
[http://www.caviumnetworks.com/ECONA_CNS3XXX.html Cavium Networks ECONA CNS3XXX]<br />
<br />
==Platforms==<br />
<br />
[http://www.globalscaletechnologies.com/t-openrdudetails.aspx OpenRD Ultimate]<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10701ARM2011-04-08T16:32:27Z<p>Bari: /* coreboot on ARM */</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
coreboot on ARM is a work-in-progress. coreboot currently does not support ARM.<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI, SAS, SATA and SCSI devices; fast boot times; and payload support.<br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
[http://www.caviumnetworks.com/ECONA_CNS3XXX.html Cavium Networks ECONA CNS3XXX]<br />
<br />
==Platforms==<br />
<br />
[http://www.globalscaletechnologies.com/t-openrdudetails.aspx OpenRD Ultimate]<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10700ARM2011-04-08T16:22:36Z<p>Bari: /* Platforms */</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
coreboot on ARM is a work-in-progress. coreboot currently does not support ARM.<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support.<br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
[http://www.caviumnetworks.com/ECONA_CNS3XXX.html Cavium Networks ECONA CNS3XXX]<br />
<br />
==Platforms==<br />
<br />
[http://www.globalscaletechnologies.com/t-openrdudetails.aspx OpenRD Ultimate]<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10699ARM2011-04-08T16:15:26Z<p>Bari: /* coreboot on ARM */</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
coreboot on ARM is a work-in-progress. coreboot currently does not support ARM.<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support.<br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
[http://www.caviumnetworks.com/ECONA_CNS3XXX.html Cavium Networks ECONA CNS3XXX]<br />
<br />
==Platforms==<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10697ARM2011-04-08T05:06:14Z<p>Bari: /* ARM SOC's */</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support. <br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
[http://www.caviumnetworks.com/ECONA_CNS3XXX.html Cavium Networks ECONA CNS3XXX]<br />
<br />
==Platforms==<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10696ARM2011-04-08T05:01:59Z<p>Bari: /* ARM SOC's */</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support. <br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/armada_xp/ Marvell Armada XP]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
==Platforms==<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10695ARM2011-04-08T04:58:30Z<p>Bari: /* Platforms */</p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support. <br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
==Platforms==<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]<br />
<br />
[http://www.ztsystems.com/Portals/0/ZTSystems_R1801e.pdf ZTSystems R1801e rackmount server]</div>Barihttps://www.coreboot.org/index.php?title=GSoC&diff=10694GSoC2011-04-08T04:55:01Z<p>Bari: /* coreboot port to Marvell ARM SOC's with PCIe */</p>
<hr />
<div>= Google Summer of Code 2011 = <br />
<br />
http://1.bp.blogspot.com/-61a6mHfP1bU/TWbmtb5TAAI/AAAAAAAAABo/w56YXLjXDGY/s400/GSOC_2011_300x200px.png<br />
<br />
Welcome to the [http://www.google-melange.com/ Google Summer of Code(tm)] page of the [[Welcome to coreboot|coreboot project]]. <br />
<br />
Apply for a coreboot GSoC project at: http://www.google-melange.com/gsoc/org/show/google/gsoc2011/coreboot<br />
<br />
This year, coreboot also tries to host some flashrom projects.<br />
<br />
<br />
== Deadlines ==<br />
<br />
Make sure you check the https://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline<br />
<br />
<br />
= Why work for coreboot =<br />
<br />
Why would you like to work for coreboot?<br />
<br />
* coreboot offers you the opportunity to work with modern technology "right on the iron".<br />
* Your application will be available to users worldwide and promoted along with all other coreboot projects.<br />
* We are a very passionate team - so you will interact directly with the project initiators and project leaders. <br />
* We have a large, helpful community. Over 100 experts in hardware and firmware lurk on our mailing list, many of them waiting to help you.<br />
<br />
<br />
= Summer of Code Application =<br />
<br />
Please complete the standard Google SoC 2011 application. Prospective corebot GSoC student should provide the following information as part of their application. <br />
<br />
:Name:<br />
:Email:<br />
:IM/IRC/Skype/other contact:<br />
<br />
:Country/Timezone:<br />
:School:<br />
:Degree Program:<br />
:Year:<br />
<br />
:Most students have some time off planned during GSoC. Do you have any vacations? When and how long?<br />
<br />
<br />
:coreboot welcomes students from all backgrounds and levels of experience. To be seriously consider for coreboot GSoC, we recommend joining the mailing list and IRC channel. Introduce yourself and mention that you are a prospective GSoC student. Ask questions and discuss the project that you are considering. Community involvement is a key component of coreboot development. By the time you have submitted your application, you should have downloaded, built a and booted coreboot in QEMU, SimNow, or on real hardware. Please, email your serial output results to the mailing list. <br />
<br />
:The following information will help coreboot match students with mentors and projects.<br />
<br />
:Please comment on your software and firmware experience.<br />
<br />
:Have you participated in the coreboot community before?<br />
<br />
:Have you contributed to an open source project? Which one? What was your experience?<br />
<br />
:Have you built and run coreboot? Did you have problems?<br />
<br />
:Bonus, Did you find and fix a coreboot bug? Did you send a patch to the email list?<br />
<br />
<br />
:Please provide an overview of your project and a break down your project in small specific goals. Explain what risks or potential problems your project might experience. What would you expect as a minimum level of success? Do you have a stretch goal? <br />
<br />
<br />
Feel free to keep your application short. A 15 page essay is no better than a 2 page summary. If you wish to write 15 pages, you are of course welcome to do so, and we will gladly put your paper up on the web page. But it is not required for the application.<br />
<br />
<br />
== How to apply ==<br />
<br />
The Drupal project has a great page on [http://drupal.org/node/59037 How to write an SOC application].<br />
<br />
Please also read Google's [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].<br />
<br />
<br />
== Some Caveats ==<br />
<br />
* Google Summer-of-Code projects are a full (day-) time job. This means we expect roughly 30-40 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply.<br />
* Getting paid by Google requires that you meet certain milestones. First, you must be in good standing with the community before the official start of the program. We suggest you post some design emails to the mailing list, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start. Also, you must have made progress and committed significant code before the mid-term point.<br />
* We require accepted students to have a blog, where you will write about your project on a regular basis. This is so that the community at large can be involved and help you. SoC is not a private contract between your mentor and you. http://blogs.coreboot.org/<br />
<br />
Note that "regular basis" in the last item does _not_ mean "3 days before evaluation deadlines". You should be "around" all the time (reporting your feedback, sending in partial successes).<br />
We don't expect our students to be experts in our problem domain, but we don't want you to fail because some basic misunderstanding was in your way of completing the task.<br />
<br />
<br />
== Time Frame ==<br />
<br />
'''DEADLINE FOR STUDENT APPLICATIONS:''' Students who are interested in working on a coreboot-related GSoC project must apply between '''March 28, 2011''' and '''April 8, 2011'''! If you want to apply, please get in contact with us right away, not just when you send your application!<br />
<br />
<br />
== Student requirements ==<br />
<br />
We will only accept your proposal if you have demonstrated that you can work with our codebase. For that, you have to send a patch to the list which is acceptable. Just ask for simple tasks on the mailing list or on IRC.<br />
<br />
<br />
= Contact =<br />
<br />
If you are interested in becoming a GSoC student, please contact [mailto:marcj303@gmail.com Marc Jones].<br />
<br />
There is also an IRC channel on irc.freenode.net: #coreboot<br />
<br />
<br />
= coreboot GSoC Mentor =<br />
Please add you name to this list and follow the coreboot mentor link to [http://www.google-melange.com/gsoc/profile/mentor/google/gsoc2011?org=coreboot apply to be a coreboot mentor]<br />
<br />
* [[User:Stepan|Stefan Reinauer]]<br />
* [[User:MJones|Marc Jones]]<br />
* [[User:Jason Wang|QingPei Wang]]<br />
<br />
http://www.google-melange.com/gsoc/profile/mentor/google/gsoc2011?org=coreboot<br />
<br />
<br />
= Possible ideas =<br />
The following are some ideas that have come up in the community. Some are more or less suitable for GSoC and prospective students' application should expand on some ideas and pair back others.<br />
<br />
<br />
== flashrom ==<br />
<br />
Note: The list below is an idea collection. Individual list items are simple enough to serve only as partial GSoC task, but they are grouped to reasonable tasks. If you're interested, please talk to us on the flashrom mailing list and/or on IRC irc://irc.freenode.net/#flashrom<br />
<br />
''[http://www.flashrom.org/GSoC/2010 http://www.flashrom.org/GSoC/2010] has more flashrom ideas and suggestions.''<br />
<br />
=== Multiple UIs for flashrom ===<br />
* flashrom TUI (text mode user interface) (for command line and flashrom-as-payload)<br />
* flashrom GUI (graphics mode user interface) (should be cross-platform, Sean Nelson has preliminary code you can base this on)<br />
<br />
=== Recovery of dead boards and onboard flash updates ===<br />
* flashrom as payload<br />
* flashrom remote flashing for coreboot panic room mode<br />
* flashrom remote flashing with modified SerialICE<br />
<br />
=== SPI bitbanging hardware support ===<br />
* flashrom support for Nvidia SPI chipset hardware<br />
* flashrom support for RayeR SPIPGM hardware<br />
* flashrom support for [[Paraflasher]] hardware<br />
* flashrom support for Willem hardware<br />
* flashrom support for some-yet-uninvented cheap universal LPC/FWH/SPI flasher hardware<br />
* flashrom support for bitbanging LPC/FWH (code exists, Uwe Hermann <br />
* flashrom support for bitbanging Parallel<br />
<br />
=== Generic flashrom infrastructure improvements ===<br />
* flashrom support for automatic recovery in case something goes wrong<br />
* flashrom support for partial reflashing<br />
* flashrom support for bytewise flashing (similar to the point above)<br />
<br />
<br />
== Infrastructure for automatic code checking ==<br />
We already have a build bot that builds various configurations of coreboot. It would be nice to extend it with various code validation routines, for example:<br />
* Validate that there's no regression in doxygen documentation (eg. are all arguments to functions still explained in @param tags, eg. after new arguments were added?)<br />
* Make code lint clean (and maybe extend lint to not fall into our traps), and run lint over the tree. Report regressions<br />
* Use LLVM's static code checking facilities, report regressions.<br />
* Work on code coverage support for coreboot code (dump data into ram, or via serial. Provide tools to fetch it). Analyse that data.<br />
<br />
=== Links ===<br />
* LLVM tools: [http://clang.llvm.org/StaticAnalysis.html Clang static analyser], [http://llvm.org/ProjectsWithLLVM/#Calysto SSA assertion checker]<br />
* Lint tools: [http://lclint.cs.virginia.edu/ Splint]<br />
* Coverage: [http://ltp.sourceforge.net/test/coverage/lcov.php LCOV], [http://ggcov.sourceforge.net GGCOV]<br />
<br />
=== Mentors ===<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
<br />
== coreboot test suite ==<br />
Create a test suite to gather and report coreboot mainboard and payload settings. This project may leverage libpayload, coreinfo, memtest86, BITS, and other tools. The suite should gather result and report them at summary and detailed levels. The goal is to help coreboot developers identify problems and to test coreboot features. This project should work closely with the testing rig and test reporting projects. It is important the the student considers how testing and reporting can be extended as features and tests are added in the future.<br />
<br />
=== Links ===<br />
* [http://biosbits.org/ BITS]<br />
http://www.coreboot.org/Supported_Motherboards<br />
<br />
=== Mentor ===<br />
* [[User:MJones|Marc Jones]] <br />
<br />
== coreboot cheap testing rig ==<br />
The goal of this project is to create a cheap testing rig which works with the existing board test infrastructure. We have a hardware test system since 2006:<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/Slides-LinuxBIOS-QA.pdf Quality Assurance Talk (Slides)]<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/TestIntegrationManual.pdf Test Integration Manual]<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/DevelopersManual.pdf Test Developers Manual]<br />
* [http://www.coresystems.de/PDFs/LinuxBIOS-testing/TestSpecification.pdf Test Specification]<br />
<br />
The initial version of our testing rig used a remote power switch and was rather expensive. With cheaper technologies such as X10, it's possible to drop the testing costs per board significantly.<br />
<br />
=== Links ===<br />
* http://qa.coresystems.de<br />
* [[InSystemFlasher]] is a cheap DIY hardware prototype for building an automated testing rig for modern SPI-based boards. This could be used as a starting point.<br />
<br />
=== Mentors ===<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
<br />
== coreboot mainboard test result reporting ==<br />
One of the biggest challenges in coreboot is support many systems in the same codebase. As systems age and coreboot continues to develop, the condition of mainboards becomes unknown. This project would define a coreboot test results reporting mechanism, gather data, and report passing and failing systems on a webpage. This project would work closely with the coreboot test suite project and/or the hardware test rig project. A good example of test results gathering and reporting is done by the Phoronix/Openbenchmark. The student should investigate other test and reporting solutions to leverage the best options for coreboot. It is important the the student considers how testing and reporting can be extended as features and tests are added in the future.<br />
<br />
=== Links ===<br />
* http://openbenchmarking.org/<br />
* http://www.coreboot.org/Supported_Motherboards<br />
<br />
=== Mentor ===<br />
* [[User:Stepan|Stefan Reinauer]]<br />
* [[User:MJones|Marc Jones]]<br />
<br />
<br />
== coreboot ports for Family14 mainboards == <br />
Identify potential mainboards to port based on the recently released AMD Family 14 support. The goal would be to support publicly available plaftorms with a number of payloads and operating systems.<br />
<br />
=== Mentor ===<br />
*[[User:Jason Wang|QingPei Wang]]<br />
<br />
<br />
== coreboot ACPI/S3/power managment ==<br />
coreboot has support for ACPI tables and S3 support for some platforms, but it is very mainboard specific. Create a generic solution for ACPI table generation and S3 support.<br />
<br />
=== Mentor ===<br />
*<br />
<br />
<br />
==coreboot port to Marvell ARM SOC's with PCIe==<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Processors] These [[ARM]] SOC's with PCIe will become popular in netbooks later this year. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support.<br />
<br />
Note that coreboot has in the past supported three different CPUs (x86, Alpha, PPC), so the structure is there for adding in a new processor family. <br />
We will need to find the right platform to do the work, but I (Ron) can provide a board and JTAG debugger if needed. <br />
<br />
=== Mentors ===<br />
* Bari Ari<br />
* [[User:Rminnich|Ron Minnich]]<br />
* [[User:Jason Wang|QingPei Wang]]<br />
<br />
== coreboot panic room ==<br />
<br />
Create a safe boot solution for coreboot to easily and cheaply recover the system in case of a panic(). <br />
<br />
Ron would like to base this solution around SerialICE. The basic idea is that the system always boots to SerialICE. There is a test in CMOS for 'last boot worked' and, if this is set, SerialICE finds a coreboot in cbfs and runs it. If 'last boot worked' is not set, or the user hits some magic keyboard sequence, SerialICE takes control. <br />
<br />
SerialICE needs to be extended (not much) to make this work. Having this capability would make it possible for Ron to get some very hard ports working that are just not possible today. At the same time, there are lots of hardware boards to test this idea on, so it should be easy to get it working. <br />
<br />
It might be possible to integrate this into the coreboot build as a bootblock option (in the same spot as the fallback/normal switch and the simple loader).<br />
<br />
=== Mentors ===<br />
* [[User:Rminnich|Ron Minnich]]<br />
<br />
<br />
== Board config infrastructure ==<br />
<br />
Design data structures that host information about the board layout so coreboot can better initialize components and generate all kinds of tables (mptable, pirq, acpi, ...) from that dynamically (at build or runtime, as appropriate). Adapt boards to use that instead of the current hardcodes.<br />
<br />
=== Links ===<br />
* ?<br />
<br />
=== Mentors ===<br />
* ?<br />
<br />
<br />
== Refactor AMD code ==<br />
<br />
AMD K8 and AMD Fam10 are different enough to have their own code. This is unfortunate, as you have to decide which CPU type you use in a given mainboard. Refactor AMD code so a single image can support both chip types on a given board. Also move tables from get_bus_conf and the like to the device tree or kconfig options (or runtime detection), as appropriate.<br />
<br />
=== Links ===<br />
* ?<br />
<br />
=== Mentors ===<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
<br />
=== Laptop support ===<br />
<br />
This one is really HARD. If you're lucky and if you have datasheets, you can do it in maybe 1 month. If you're unlucky, it can take the whole GSoC or more. If there is interest, we'll try to find an embedded controller which won't cause you to give up in frustration. Still, it might be beneficial if you're willing to solder.<br />
* flashrom support for embedded controllers (ECs) in laptops<br />
<br />
<br />
=== Links ===<br />
* [http://www.flashrom.org/ flashrom]<br />
<br />
=== Mentors ===<br />
* ?<br />
<br />
<br />
== Your own Project Ideas ==<br />
<br />
We have come up with some ideas for cool Summer of Code projects here. These are projects that we think can be managed in the short period of GSoC, and they cover areas where coreboot is trying to reach new users and new use cases.<br />
<br />
But of course your application does not need to be based on any of the ideas listed below. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!<br />
<br />
Feel free to contact us at the email address above, and don't hesitate to suggest whatever you have in mind.<br />
<br />
<br />
= Previous Summer of Code projects =<br />
<br />
We successfully participated in Google's Summer of Code in 2007, 2008, 2009, and 2010. See our [[Previous GSoC Projects|list of previous GSoC projects]].</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10693ARM2011-04-08T04:52:55Z<p>Bari: </p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==<br />
<br />
ARM SOC's with PCIe are now on the market for tablets, netbooks and servers. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support. <br />
<br />
==ARM SOC's==<br />
<br />
[http://www.marvell.com/products/processors/armada.html Marvell Armada 300, 510, 1000 with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/discovery_innovation/ Marvell Discovery Innovation Series with PCIe]<br />
<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Kirkwood Series with PCIe]<br />
<br />
[http://www.st.com/internet/mcu/product/250658.jsp STMicroelectronics SPEAr1310 with PCIe]<br />
<br />
[http://focus.ti.com/dsp/docs/dspplatformscontento.tsp?sectionId=2&familyId=1875&tabId=2643 TI Sitara with PCIe]<br />
<br />
==Platforms==<br />
<br />
[http://www.marvell.com/platforms/open_rd.html OpenRD Platforms]</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10691ARM2011-04-08T04:29:43Z<p>Bari: </p>
<hr />
<div>=ARM=<br />
<br />
==coreboot on ARM==</div>Barihttps://www.coreboot.org/index.php?title=ARM&diff=10690ARM2011-04-08T04:28:05Z<p>Bari: The start of pages about ARM support</p>
<hr />
<div>ARM<br />
<br />
coreboot on ARM</div>Barihttps://www.coreboot.org/index.php?title=Datasheets&diff=10169Datasheets2010-11-18T21:11:45Z<p>Bari: /* AMD RD890 */</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Developer_Manual/Tools&diff=9867Developer Manual/Tools2010-08-20T05:12:52Z<p>Bari: /* PLAICE: Programmer, Logic Analyzer and In-Circuit Emulator */ deleted dead project</p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Ectool&diff=9708Ectool2010-05-18T16:26:00Z<p>Bari: added - Only ACPI-compliant EC's will be detected.</p>
<hr />
<div>'''ectool''' is a small utility that dumps the RAM of a laptop's Embedded/Environmental Controller (EC).<br />
<br />
'''ectool''' expects an EC as described in the ACPI specification.<br />
Only ACPI-compliant EC's will be detected.<br />
<br />
== Installation ==<br />
<br />
'''Manual installation'''<br />
<br />
$ svn co svn://coreboot.org/coreboot/trunk/util/ectool<br />
$ cd ectool<br />
$ make<br />
$ sudo make install<br />
<br />
You can [http://tracker.coreboot.org/trac/coreboot/browser/trunk/util/ectool browse the ectool source code] using the trac web interface.<br />
<br />
== Usage ==<br />
<br />
$ ectool<br />
<br />
Please see '''ectool -h''' for information on various other options.<br />
<br />
<br />
{{PD-self}}</div>Barihttps://www.coreboot.org/index.php?title=GSoC&diff=9415GSoC2010-03-15T16:02:07Z<p>Bari: /* coreboot port to Marvell ARM SOC's with PCIe */</p>
<hr />
<div>= Google Summer of Code 2010 =<br />
<br />
http://3.bp.blogspot.com/_fxRR_bT3LgA/S5U3rk2J-eI/AAAAAAAACE8/mBRYQwSqvqQ/s400/2010_NoURL_300x267px.jpg<br />
<br />
Welcome to the [http://code.google.com/soc/ Google Summer of Code(tm)] page of the [[Welcome to coreboot|coreboot project]]. Apply for a coreboot GSoC project at http://socghop.appspot.com/.<br />
<br />
This year, coreboot also tries to host some flashrom projects.<br />
<br />
== Deadlines ==<br />
<br />
Make sure you check the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline Deadlines]<br />
<br />
= Why work for coreboot =<br />
<br />
Why would you like to work for coreboot?<br />
<br />
* coreboot offers you the opportunity to work with modern technology "right on the iron".<br />
* Your application will be available to users worldwide and promoted along with all other coreboot projects.<br />
* We are a very passionate team - so you will interact directly with the project initiators and project leaders. <br />
* We have a large, helpful community. Over 100 experts in hardware and firmware lurk on our mailing list, many of them waiting to help you.<br />
<br />
<br />
= Summer of Code Application =<br />
<br />
Please complete the standard [http://code.google.com/soc/ Google SoC 2010 application]. Additionally, please provide information on the following:<br />
<br />
# Who are you? What are you studying?<br />
# Why are you the right person for this task?<br />
# Do you have any other commitments that we should know about?<br />
# List your C, Assembler and hardware experience.<br />
# List your history with open source projects.<br />
# What is your preferred method of contact? (Phone, email, Skype, etc) <br />
<br />
Feel free to keep your application short. A 15 page essay is no better than a 2 page summary. If you wish to write 15 pages, you are of course welcome to do so, and we will gladly put your paper up on the web page. But it is not required for the application.<br />
<br />
== How to apply ==<br />
<br />
The Drupal project has a great page on [http://drupal.org/node/59037 How to write an SOC application].<br />
<br />
Please also read Google's [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].<br />
<br />
== Some Caveats ==<br />
<br />
* Google Summer-of-Code projects are a full (day-) time job. This means we expect roughly 30-40 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply.<br />
* Getting paid by Google requires that you meet certain milestones. First, you must be in good standing with the community before the official start of the program. We suggest you post some design emails to the mailing list, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start. Also, you must have made progress and committed significant code before the mid-term point.<br />
* We are thinking of requiring accepted students to have a blog, where you will write about your project on a regular basis. This is so that the community at large can be involved and help you. SoC is not a private contract between your mentor and you.<br />
<br />
Note that "regular basis" in the last item does _not_ mean "3 days before evaluation deadlines". You should be "around" all the time (reporting your feedback, sending in partial successes).<br />
We don't expect our students to be experts in our problem domain, but we don't want you to fail because some basic misunderstanding was in your way of completing the task.<br />
<br />
== Time Frame ==<br />
<br />
'''DEADLINE FOR STUDENT APPLICATIONS:''' Students who are interested in working on a coreboot-related GSoC project must apply between '''March 29, 2010''' and '''April 9, 2010'''! If you want to apply, please get in contact with us right away, not just when you send your application!<br />
<br />
== Student requirements ==<br />
<br />
We will only accept your proposal if you have demonstrated that you can work with our codebase. For that, you have to send a patch to the list which is acceptable. Just ask for simple tasks on the mailing list or on IRC.<br />
<br />
= Contact =<br />
<br />
If you are interested in becoming a GSoC student, please contact [mailto:stepan@coresystems.de Stefan Reinauer].<br />
<br />
There is also an IRC channel on irc.freenode.net: #coreboot<br />
<br />
= Possible ideas =<br />
<br />
== Infrastructure for automatic code checking ==<br />
<br />
We already have a build bot that builds various configurations of coreboot. It would be nice to extend it with various code validation routines, for example:<br />
* Validate that there's no regression in doxygen documentation (eg. are all arguments to functions still explained in @param tags, eg. after new arguments were added?)<br />
* Make code lint clean (and maybe extend lint to not fall into our traps), and run lint over the tree. Report regressions<br />
* Use LLVM's static code checking facilities, report regressions.<br />
* Work on code coverage support for coreboot code (dump data into ram, or via serial. Provide tools to fetch it). Analyse that data.<br />
<br />
=== Links ===<br />
* LLVM tools: [http://clang.llvm.org/StaticAnalysis.html Clang static analyser], [http://llvm.org/ProjectsWithLLVM/#Calysto SSA assertion checker]<br />
* Lint tools: [http://lclint.cs.virginia.edu/ Splint]<br />
* Coverage: [http://ltp.sourceforge.net/test/coverage/lcov.php LCOV], [http://ggcov.sourceforge.net GGCOV]<br />
<br />
=== Mentors ===<br />
* [[User:MJones|Marc Jones]]<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
== TianoCore on coreboot ==<br />
<br />
[http://www.tianocore.org/ Tiano Core] is Intel's EFI implementation. Unlike coreboot, it is not a firmware, but rather a bootloader. Last year we started porting TianoCore to run on coreboot, but there are many things left to do. Improve Tiano Core running as a coreboot payloads, or change coreboot so it can load Tiano Core as a payloads.<br />
<br />
This project requires no hardware skills, but especially in case of TianoCore might require knowledge of Windows compilers (VC2005?)<br />
<br />
=== Links ===<br />
* [http://www.tianocore.org/ Tiano Core]<br />
<br />
=== Mentors ===<br />
* [[User:Rminnich|Ron Minnich]]<br />
* [[User:Stepan|Stefan Reinauer]]<br />
* [[User:MJones|Marc Jones]]<br />
<br />
==coreboot port to Marvell ARM SOC's with PCIe==<br />
[http://www.marvell.com/products/processors/embedded/kirkwood/ Marvell Processors] These ARM SOC's with PCIe will become popular in netbooks later this year. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support.<br />
<br />
== coreboot port to AMD 800 series chipsets ==<br />
(probably too big of a task)<br />
<br />
== coreboot mass-porting to AMD 780 series mainboards ==<br />
(since code is now available)<br />
<br />
== coreboot panic room ==<br />
(maybe just reuse the SerialICE core, too small project for full GSoC)<br />
<br />
== coreboot cheap testing rig ==<br />
create a cheap testing rig which works with the existing board test infrastructure<br />
<br />
== coreboot GeodeLX port from v3 to v4 ==<br />
significant parts of that are already done, so it's hard to fill a full GSoC with that. One thing could be "verify that everything is brought over", but that's nothing that can be reasonably proven (and it might also be too close to "documentation tasks", which are not allowed)<br />
<br />
== drivers for libpayload ==<br />
IDE, AHCI, Bluetooth, Firewire, Smartcards, maybe filesystems. Work towards making FILO only a shell, which uses libpayload for the "real" work. Notice that libpayload code must be licensed BSD-style (so ports from FILO, SeaBIOS or Linux won't work).<br />
Pick a given set and tell us why it's enough work for the allocated time, but not too much for you. Also, which sources (if any) you want to draw from.<br />
<br />
== Board config infrastructure ==<br />
Design data structures that host information about the board layout so coreboot can better initialize components and generate all kinds of tables (mptable, pirq, acpi, ...) from that dynamically (at build or runtime, as appropriate). Adapt boards to use that instead of the current hardcodes.<br />
<br />
== flashrom ==<br />
<br />
Note: The list below is an idea collection. Many of the projects are simple enough to serve only as partial GSoC task<br />
<br />
* flashrom text mode GUI<br />
* flashrom graphics mode GUI (Sean Nelson has preliminary code)<br />
* flashrom as payload<br />
* flashrom under DOS<br />
* flashrom remote flashing for coreboot panic room mode<br />
* flashrom remote flashing with modified SerialICE<br />
* flashrom support for Nvidia SPI chipset hardware<br />
* flashrom support for [[Paraflasher]] hardware<br />
* flashrom support for RayeR SPIPGM hardware<br />
* flashrom support for Willem hardware<br />
* flashrom support for some-yet-uninvented cheap universal LPC/FWH/SPI flasher hardware<br />
* flashrom support for bitbanging LPC/FWH<br />
* flashrom support for bitbanging Parallel<br />
* flashrom support for partial reflashing<br />
* flashrom support for automatic recovery in case something goes wrong<br />
* flashrom support for embedded controllers (ECs) in laptops<br />
<br />
== Your own Project Ideas ==<br />
<br />
We have come up with some ideas for cool Summer of Code projects here. These are projects that we think can be managed in the short period of GSoC, and they cover areas where coreboot is trying to reach new users and new use cases.<br />
<br />
But of course your application does not need to be based on any of the ideas listed below. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!<br />
<br />
Feel free to contact us at the email address above, and don't hesitate to suggest whatever you have in mind.<br />
<br />
= Previous Summer of Code projects =<br />
<br />
We successfully participated in Google's Summer of Code in 2007, 2008 and 2009. See our [[Previous GSoC Projects|list of previous GSoC projects]].</div>Barihttps://www.coreboot.org/index.php?title=GSoC&diff=9411GSoC2010-03-15T15:39:14Z<p>Bari: /* coreboot mass-porting to AMD 780 series mainboards */ changed to code is available</p>
<hr />
<div>= Google Summer of Code 2010 =<br />
<br />
http://3.bp.blogspot.com/_fxRR_bT3LgA/S5U3rk2J-eI/AAAAAAAACE8/mBRYQwSqvqQ/s400/2010_NoURL_300x267px.jpg<br />
<br />
Welcome to the [http://code.google.com/soc/ Google Summer of Code(tm)] page of the [[Welcome to coreboot|coreboot project]]. Apply for a coreboot GSoC project at http://socghop.appspot.com/.<br />
<br />
This year, coreboot also tries to host some flashrom projects.<br />
<br />
== Deadlines ==<br />
<br />
Make sure you check the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline Deadlines]<br />
<br />
= Why work for coreboot =<br />
<br />
Why would you like to work for coreboot?<br />
<br />
* coreboot offers you the opportunity to work with modern technology "right on the iron".<br />
* Your application will be available to users worldwide and promoted along with all other coreboot projects.<br />
* We are a very passionate team - so you will interact directly with the project initiators and project leaders. <br />
* We have a large, helpful community. Over 100 experts in hardware and firmware lurk on our mailing list, many of them waiting to help you.<br />
<br />
<br />
= Summer of Code Application =<br />
<br />
Please complete the standard [http://code.google.com/soc/ Google SoC 2010 application]. Additionally, please provide information on the following:<br />
<br />
# Who are you? What are you studying?<br />
# Why are you the right person for this task?<br />
# Do you have any other commitments that we should know about?<br />
# List your C, Assembler and hardware experience.<br />
# List your history with open source projects.<br />
# What is your preferred method of contact? (Phone, email, Skype, etc) <br />
<br />
Feel free to keep your application short. A 15 page essay is no better than a 2 page summary. If you wish to write 15 pages, you are of course welcome to do so, and we will gladly put your paper up on the web page. But it is not required for the application.<br />
<br />
== How to apply ==<br />
<br />
The Drupal project has a great page on [http://drupal.org/node/59037 How to write an SOC application].<br />
<br />
Please also read Google's [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].<br />
<br />
== Some Caveats ==<br />
<br />
* Google Summer-of-Code projects are a full (day-) time job. This means we expect roughly 30-40 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply.<br />
* Getting paid by Google requires that you meet certain milestones. First, you must be in good standing with the community before the official start of the program. We suggest you post some design emails to the mailing list, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start. Also, you must have made progress and committed significant code before the mid-term point.<br />
* We are thinking of requiring accepted students to have a blog, where you will write about your project on a regular basis. This is so that the community at large can be involved and help you. SoC is not a private contract between your mentor and you.<br />
<br />
Note that "regular basis" in the last item does _not_ mean "3 days before evaluation deadlines". You should be "around" all the time (reporting your feedback, sending in partial successes).<br />
We don't expect our students to be experts in our problem domain, but we don't want you to fail because some basic misunderstanding was in your way of completing the task.<br />
<br />
== Time Frame ==<br />
<br />
'''DEADLINE FOR STUDENT APPLICATIONS:''' Students who are interested in working on a coreboot-related GSoC project must apply between '''March 23, 2009''' and '''April 3, 2009'''! If you want to apply, please get in contact with us right away!<br />
<br />
<br />
== Student requirements ==<br />
<br />
We will only accept your proposal if you have demonstrated that you can work with our codebase. For that, you have to send a patch to the list which is acceptable. Just ask for simple tasks on the mailing list or on IRC.<br />
<br />
= Contact =<br />
<br />
If you are interested in becoming a GSoC student, please contact [mailto:stepan@coresystems.de Stefan Reinauer].<br />
<br />
There is also an IRC channel on irc.freenode.net: #coreboot<br />
<br />
= Possible ideas =<br />
<br />
== Infrastructure for automatic code checking ==<br />
<br />
We already have a build bot that builds various configurations of coreboot. It would be nice to extend it with various code validation routines, for example:<br />
* Validate that there's no regression in doxygen documentation (eg. are all arguments to functions still explained in @param tags, eg. after new arguments were added?)<br />
* Make code lint clean (and maybe extend lint to not fall into our traps), and run lint over the tree. Report regressions<br />
* Use LLVM's static code checking facilities, report regressions.<br />
* Work on code coverage support for coreboot code (dump data into ram, or via serial. Provide tools to fetch it). Analyse that data.<br />
<br />
=== Links ===<br />
* LLVM tools: [http://clang.llvm.org/StaticAnalysis.html Clang static analyser], [http://llvm.org/ProjectsWithLLVM/#Calysto SSA assertion checker]<br />
* Lint tools: [http://lclint.cs.virginia.edu/ Splint]<br />
* Coverage: [http://ltp.sourceforge.net/test/coverage/lcov.php LCOV], [http://ggcov.sourceforge.net GGCOV]<br />
<br />
=== Mentors ===<br />
* [[User:PatrickGeorgi|Patrick Georgi]]<br />
* [[User:MJones|Marc Jones]]<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
== TianoCore on coreboot ==<br />
<br />
[http://www.tianocore.org/ Tiano Core] is Intel's EFI implementation. Unlike coreboot, it is not a firmware, but rather a bootloader. Last year we started porting TianoCore to run on coreboot, but there are many things left to do. Improve Tiano Core running as a coreboot payloads, or change coreboot so it can load Tiano Core as a payloads.<br />
<br />
This project requires no hardware skills, but especially in case of TianoCore might require knowledge of Windows compilers (VC2005?)<br />
<br />
=== Links ===<br />
* [http://www.tianocore.org/ Tiano Core]<br />
<br />
=== Mentors ===<br />
* [[User:Rminnich|Ron Minnich]]<br />
* [[User:Stepan|Stefan Reinauer]]<br />
* [[User:MJones|Marc Jones]]<br />
<br />
==coreboot port to Marvell ARM SOC's with PCIe==<br />
[http://www.marvell.com/products/processors/ Marvell Processors] These ARM SOC's with PCIe will become popular in netbooks later this year. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support. <br />
<br />
== coreboot port to AMD 800 series chipsets ==<br />
(probably too big of a task)<br />
<br />
== coreboot mass-porting to AMD 780 series mainboards ==<br />
(since code is now available)<br />
<br />
== coreboot panic room ==<br />
(maybe just reuse the SerialICE core, too small project for full GSoC)<br />
<br />
== coreboot cheap testing rig ==<br />
create a cheap testing rig which works with the existing board test infrastructure<br />
<br />
== coreboot GeodeLX port from v3 to v4 ==<br />
significant parts of that are already done, so it's hard to fill a full GSoC with that. One thing could be "verify that everything is brought over", but that's nothing that can be reasonably proven (and it might also be too close to "documentation tasks", which are not allowed)<br />
<br />
== drivers for libpayload ==<br />
IDE, AHCI, Bluetooth, Firewire, Smartcards, maybe filesystems. Work towards making FILO only a shell, which uses libpayload for the "real" work. Notice that libpayload code must be licensed BSD-style (so ports from FILO, SeaBIOS or Linux won't work).<br />
Pick a given set and tell us why it's enough work for the allocated time, but not too much for you. Also, which sources (if any) you want to draw from.<br />
<br />
== Board config infrastructure ==<br />
Design data structures that host information about the board layout so coreboot can better initialize components and generate all kinds of tables (mptable, pirq, acpi, ...) from that dynamically (at build or runtime, as appropriate). Adapt boards to use that instead of the current hardcodes.<br />
<br />
== flashrom ==<br />
<br />
Note: The list below is an idea collection. Many of the projects are simple enough to serve only as partial GSoC task<br />
<br />
* flashrom text mode GUI<br />
* flashrom graphics mode GUI (Sean Nelson has preliminary code)<br />
* flashrom as payload<br />
* flashrom under DOS<br />
* flashrom remote flashing for coreboot panic room mode<br />
* flashrom remote flashing with modified SerialICE<br />
* flashrom support for Nvidia SPI chipset hardware<br />
* flashrom support for [[Paraflasher]] hardware<br />
* flashrom support for RayeR SPIPGM hardware<br />
* flashrom support for Willem hardware<br />
* flashrom support for some-yet-uninvented cheap universal LPC/FWH/SPI flasher hardware<br />
* flashrom support for bitbanging LPC/FWH<br />
* flashrom support for bitbanging Parallel<br />
* flashrom support for partial reflashing<br />
* flashrom support for automatic recovery in case something goes wrong<br />
* flashrom support for embedded controllers (ECs) in laptops<br />
<br />
== Your own Project Ideas ==<br />
<br />
We have come up with some ideas for cool Summer of Code projects here. These are projects that we think can be managed in the short period of GSoC, and they cover areas where coreboot is trying to reach new users and new use cases.<br />
<br />
But of course your application does not need to be based on any of the ideas listed below. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!<br />
<br />
Feel free to contact us at the email address below, and don't hesitate to suggest whatever you have in mind.<br />
<br />
= Previous Summer of Code projects =<br />
<br />
We successfully participated in Google's Summer of Code in 2007, 2008 and 2009. See our [[Previous GSoC Projects|list of previous GSoC projects]].</div>Barihttps://www.coreboot.org/index.php?title=GSoC&diff=9406GSoC2010-03-14T01:44:03Z<p>Bari: added Marvell ARM coreboot port</p>
<hr />
<div>= Google Summer of Code 2010 =<br />
<br />
http://3.bp.blogspot.com/_fxRR_bT3LgA/S5U3rk2J-eI/AAAAAAAACE8/mBRYQwSqvqQ/s400/2010_NoURL_300x267px.jpg<br />
<br />
Welcome to the [http://code.google.com/soc/ Google Summer of Code(tm)] page of the [[Welcome to coreboot|coreboot project]]. Apply for a coreboot GSoC project at http://socghop.appspot.com/.<br />
<br />
This year, coreboot also tries to host some flashrom projects.<br />
<br />
== Deadlines ==<br />
<br />
Make sure you check the [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline Deadlines]<br />
<br />
= Why work for coreboot =<br />
<br />
Why would you like to work for coreboot?<br />
<br />
* coreboot offers you the opportunity to work with modern technology "right on the iron".<br />
* Your application will be available to users worldwide and promoted along with all other coreboot projects.<br />
* We are a very passionate team - so you will interact directly with the project initiators and project leaders. <br />
* We have a large, helpful community. Over 100 experts in hardware and firmware lurk on our mailing list, many of them waiting to help you.<br />
<br />
<br />
= Summer of Code Application =<br />
<br />
Please complete the standard [http://code.google.com/soc/ Google SoC 2010 application]. Additionally, please provide information on the following:<br />
<br />
# Who are you? What are you studying?<br />
# Why are you the right person for this task?<br />
# Do you have any other commitments that we should know about?<br />
# List your C, Assembler and hardware experience.<br />
# List your history with open source projects.<br />
# What is your preferred method of contact? (Phone, email, Skype, etc) <br />
<br />
Feel free to keep your application short. A 15 page essay is no better than a 2 page summary. If you wish to write 15 pages, you are of course welcome to do so, and we will gladly put your paper up on the web page. But it is not required for the application.<br />
<br />
== How to apply ==<br />
<br />
The Drupal project has a great page on [http://drupal.org/node/59037 How to write an SOC application].<br />
<br />
Please also read Google's [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].<br />
<br />
== Some Caveats ==<br />
<br />
* Google Summer-of-Code projects are a full (day-) time job. This means we expect roughly 30-40 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply.<br />
* Getting paid by Google requires that you meet certain milestones. First, you must be in good standing with the community before the official start of the program. We suggest you post some design emails to the mailing list, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start. Also, you must have made progress and committed significant code before the mid-term point.<br />
* We are thinking of requiring accepted students to have a blog, where you will write about your project on a regular basis. This is so that the community at large can be involved and help you. SoC is not a private contract between your mentor and you. <br />
<br />
== Time Frame ==<br />
<br />
'''DEADLINE FOR STUDENT APPLICATIONS:''' Students who are interested in working on a coreboot-related GSoC project must apply between '''March 23, 2009''' and '''April 3, 2009'''! If you want to apply, please get in contact with us right away!<br />
<br />
<br />
== Student requirements ==<br />
<br />
We will only accept your proposal if you have demonstrated that you can work with our codebase. For that, you have to send a patch to the list which is acceptable. Just ask for simple tasks on the mailing list or on IRC.<br />
<br />
= Contact =<br />
<br />
If you are interested in becoming a GSoC student, please contact [mailto:stepan@coresystems.de Stefan Reinauer].<br />
<br />
There is also an IRC channel on irc.freenode.net: #coreboot<br />
<br />
= Possible ideas =<br />
<br />
== Infrastructure for automatic code checking ==<br />
<br />
We already have a build bot that builds various configurations of coreboot. It would be nice to extend it with various code validation routines, for example:<br />
* Validate that there's no regression in doxygen documentation (eg. are all arguments to functions still explained in @param tags, eg. after new arguments were added?)<br />
* Make code lint clean (and maybe extend lint to not fall into our traps), and run lint over the tree. Report regressions<br />
* Use LLVM's static code checking facilities, report regressions.<br />
* Work on code coverage support for coreboot code (dump data into ram, or via serial. Provide tools to fetch it). Analyse that data.<br />
<br />
=== Links ===<br />
* LLVM tools: [http://clang.llvm.org/StaticAnalysis.html Clang static analyser], [http://llvm.org/ProjectsWithLLVM/#Calysto SSA assertion checker]<br />
* Lint tools: [http://lclint.cs.virginia.edu/ Splint]<br />
* Coverage: [http://ltp.sourceforge.net/test/coverage/lcov.php LCOV], [http://ggcov.sourceforge.net GGCOV]<br />
<br />
=== Mentors ===<br />
* [[User:PatrickGeorgi|Patrick Georgi]]<br />
* [[User:MJones|Marc Jones]]<br />
* [[User:Stepan|Stefan Reinauer]]<br />
<br />
== TianoCore on coreboot ==<br />
<br />
[http://www.tianocore.org/ Tiano Core] is Intel's EFI implementation. Unlike coreboot, it is not a firmware, but rather a bootloader. Last year we started porting TianoCore to run on coreboot, but there are many things left to do. Improve Tiano Core running as a coreboot payloads, or change coreboot so it can load Tiano Core as a payloads.<br />
<br />
This project requires no hardware skills, but especially in case of TianoCore might require knowledge of Windows compilers (VC2005?)<br />
<br />
=== Links ===<br />
* [http://www.tianocore.org/ Tiano Core]<br />
<br />
=== Mentors ===<br />
* [[User:Rminnich|Ron Minnich]]<br />
* [[User:Stepan|Stefan Reinauer]]<br />
* [[User:MJones|Marc Jones]]<br />
<br />
==coreboot port to Marvell ARM SOC's with PCIe==<br />
[http://www.marvell.com/products/processors/ Marvell Processors] These ARM SOC's with PCIe will become popular in netbooks later this year. These systems can take advantage of coreboot's strength in properly configuring PCI devices, fast boot time and payload support. <br />
<br />
== coreboot port to AMD 800 series chipsets ==<br />
(probably too big of a task)<br />
<br />
== coreboot mass-porting to AMD 780 series mainboards ==<br />
(if the code is available until then)<br />
<br />
== coreboot panic room ==<br />
(maybe just reuse the SerialICE core, too small project for full GSoC)<br />
<br />
== coreboot cheap testing rig ==<br />
create a cheap testing rig which works with the existing board test infrastructure<br />
<br />
== coreboot GeodeLX port from v3 to v4 ==<br />
significant parts of that are already done, so it's hard to fill a full GSoC with that. One thing could be "verify that everything is brought over", but that's nothing that can be reasonably proven (and it might also be too close to "documentation tasks", which are not allowed)<br />
<br />
== drivers for libpayload ==<br />
IDE, AHCI, Bluetooth, Firewire, Smartcards, maybe filesystems. Work towards making FILO only a shell, which uses libpayload for the "real" work. Notice that libpayload code must be licensed BSD-style (so ports from FILO, SeaBIOS or Linux won't work).<br />
Pick a given set and tell us why it's enough work for the allocated time, but not too much for you. Also, which sources (if any) you want to draw from.<br />
<br />
== Board config infrastructure ==<br />
Design data structures that host information about the board layout so coreboot can better initialize components and generate all kinds of tables (mptable, pirq, acpi, ...) from that dynamically (at build or runtime, as appropriate). Adapt boards to use that instead of the current hardcodes.<br />
<br />
== flashrom ==<br />
<br />
Note: The list below is an idea collection. Many of the projects are simple enough to serve only as partial GSoC task<br />
<br />
* flashrom text mode GUI<br />
* flashrom graphics mode GUI (Sean Nelson has preliminary code)<br />
* flashrom as payload<br />
* flashrom under DOS<br />
* flashrom remote flashing for coreboot panic room mode<br />
* flashrom remote flashing with modified SerialICE<br />
* flashrom support for Nvidia SPI chipset hardware<br />
* flashrom support for [[Paraflasher]] hardware<br />
* flashrom support for RayeR SPIPGM hardware<br />
* flashrom support for Willem hardware<br />
* flashrom support for some-yet-uninvented cheap universal LPC/FWH/SPI flasher hardware<br />
* flashrom support for bitbanging LPC/FWH<br />
* flashrom support for bitbanging Parallel<br />
* flashrom support for partial reflashing<br />
* flashrom support for automatic recovery in case something goes wrong<br />
* flashrom support for embedded controllers (ECs) in laptops<br />
<br />
== Your own Project Ideas ==<br />
<br />
We have come up with some ideas for cool Summer of Code projects here. These are projects that we think can be managed in the short period of GSoC, and they cover areas where coreboot is trying to reach new users and new use cases.<br />
<br />
But of course your application does not need to be based on any of the ideas listed below. The opposite: Maybe you have a great idea that we just didn't think of yet. Please let us know!<br />
<br />
Feel free to contact us at the email address below, and don't hesitate to suggest whatever you have in mind.<br />
<br />
= Previous Summer of Code projects =<br />
<br />
We successfully participated in Google's Summer of Code in 2007, 2008 and 2009. See our [[Previous GSoC Projects|list of previous GSoC projects]].</div>Barihttps://www.coreboot.org/index.php?title=Board:via/epia-cn&diff=9315Board:via/epia-cn2010-02-11T20:07:27Z<p>Bari: removed comment about FILO</p>
<hr />
<div>This page describes how to use coreboot on the '''VIA EPIA-CN''' mainboard.<br />
<br />
This page is a work in progress.<br />
<br />
VIA EPIA CN13000G<br><br />
VIA EPIA CN10000EG<br />
<br />
The earlier versions of the Epia-CN use a Winbond Super I/O vs the VIA in the later versions.<br />
<br />
== Status ==<br />
<br />
{{Status|<br />
<br />
|CPU_status = OK<br />
|CPU_comments = <br />
|CPU_L1_status = OK<br />
|CPU_L1_comments = Always on<br />
|CPU_L2_status = OK<br />
|CPU_L2_comments =Always on<br />
|CPU_L3_status = N/A<br />
|CPU_multiple_status = N/A<br />
|CPU_multicore_status = N/A<br />
|CPU_virt_status = N/A<br />
<br />
|RAM_EDO_status = N/A<br />
|RAM_SDRAM_status = N/A<br />
|RAM_SODIMM_status = N/A<br />
|RAM_DDR_status = N/A<br />
|RAM_DDR2_status = OK<br />
|RAM_DDR3_status = N/A<br />
|RAM_dualchannel_status = N/A<br />
|RAM_ecc_status = N/A<br />
<br />
|IDE_status = OK<br />
|IDE_comments =<br />
|IDE_CF_status = OK<br />
|IDE_CF_comments = <br />
|IDE_25_status = OK<br />
|IDE_CF_comments = OK using adapter<br />
|CDROM_DVD_status = OK<br />
|CDROM_DVD_comments = <br />
|SATA_status = OK<br />
|SATA_comments =<br />
|USB_status = OK<br />
|USB_comments = UHCI and EHCI<br />
|Onboard_VGA_status = OK<br />
|Onboard_VGA_comments = Openchrome works without vgabios or bochs<br />
|Onboard_ethernet_status = OK<br />
|Onboard_audio_status = OK<br />
|Onboard_modem_status = N/A<br />
|Onboard_firewire_status = N/A<br />
|Smartcard_status = N/A<br />
|Onboard_CF_status = N/A<br />
|Onboard_PCMCIA_status = N/A<br />
<br />
|ISA_cards_status = N/A<br />
|AMR_cards_status = N/A<br />
|AGP_cards_status = N/A<br />
|PCI_cards_status = OK<br />
|PCI_cards_comments =<br />
|PCIE_x1_status = N/A<br />
|PCIE_x1_comments = <br />
|PCIE_x2_status = N/A<br />
|PCIE_x4_status = N/A<br />
|PCIE_x8_status = N/A<br />
|PCIE_x16_status = N/A<br />
|PCIE_x16_comments = <br />
|PCIE_x32_status = N/A<br />
|HTX_status = N/A<br />
<br />
|Floppy_status = N/A<br />
|Floppy_comments = <br />
|COM1_status = OK<br />
|COM2_status = Not tested<br />
|PP_status = Not tested<br />
|PP_comments = <br />
|PS2_keyboard_status = OK<br />
|PS2_mouse_status = OK<br />
|Game_port_status = N/A<br />
|Game_port_comments = <br />
|IR_status = Not tested<br />
|Speaker_status = OK<br />
|DiskOnChip_status = NA<br />
<br />
|Sensors_status = Not tested<br />
|Sensors_comments = <br />
|Watchdog_status = OK<br />
|Watchdog_comments = <br />
|CAN_bus_status = N/A<br />
|CPUfreq_status = OK<br />
|CPUfreq_comments = <br />
|Powersave_status = N/A<br />
|ACPI_status = Not Yet<br />
|ACPI_comments = <br />
|Reboot_status = OK<br />
|Poweroff_status = <br />
|LEDs_status = OK<br />
|LEDs_comments = <br />
|HPET_status = Not tested<br />
|HPET_comments = <br />
|RNG_status = N/A<br />
|WakeOnModem_status = N/A<br />
|WakeOnLAN_status = Untested<br />
|WakeOnKeyboard_status = Untested<br />
|WakeOnMouse_status = Untested<br />
|Flashrom_status = OK<br />
|Flashrom_comments = SST 512KB, 1MB, 2MB, PMC 512KB<br />
<br />
}}<br />
<br />
Use this to extract the vgabios from the factory BIOS:<br><br />
<br />
$ dd if=/dev/mem of=video.bios.bin.4 bs=65536 count=1 skip=12<br />
<br />
Ubuntu 8.04 openchrome drivers support X without the need for bochs or vgabios. viafb support as a payload is in the works.<br />
<br />
== See also ==<br />
<br />
* http://www.coreboot.org/pipermail/coreboot/2008-February/030101.html (old status post)<br />
* http://www.coreboot.org/pipermail/coreboot/2008-May/034736.html (new patch which got committed later)<br />
<br />
<br />
{{PD-self}}</div>Barihttps://www.coreboot.org/index.php?title=User:Bari&diff=9083User:Bari2009-10-29T21:00:44Z<p>Bari: </p>
<hr />
<div>Bari Ari works for O.N.E. Technologies and features opposable thumbs.</div>Barihttps://www.coreboot.org/index.php?title=File:X86_bios.tar.bz2&diff=8306File:X86 bios.tar.bz22009-04-15T18:26:02Z<p>Bari: QNX Fastbios</p>
<hr />
<div>QNX Fastbios</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=7898Laptop2009-01-16T18:06:58Z<p>Bari: /* Recent Progress of coreboot on Laptops */ added more CTL IL1 info</p>
<hr />
<div>== Recent Progress of coreboot on Laptops ==<br />
<br />
The VIA vx700 and vx800 chipsets have recently become popular in many netbook designs. Most of these netbooks are being produced by [http://www.quantatw.com Quanta] for several different OEM's. <br />
<br />
VIA has recently released open documentation for the vx700 and vx800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal] and open documentation for the latest [http://www.x.org/docs/via/ Unichrome] graphics controllers. VIA has also released binary unichrome drivers with 2D and 3D accel support for Ubuntu 8.04 and 8.10 as well as source for 2D at [http://linux.via.com.tw/support/downloadFiles.action VIA Linux Portal]. <br />
<br />
VIA is currently developing coreboot support for the vx800 chipset. [http://www.openchrome.org/ openChrome] support including 2D and 3D accel is also in the works for many new chipsets including the vx700 and vx800. <br />
<br />
The remaining issue with supporting these and other similar netbooks may be open firmware support for the Embedded Controller (EC). The most common EC's in these netbooks are the KB3310, KB3910 and KB3920 from [http://www.ene.com.tw/en/index.asp ENE Technology]. The ENE EC's are 8051 based and are used to support keyboard scan, lid open/closed, battery charging, power management, etc. <br />
<br />
coreboot may work with the "stock" firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)? <br />
<br />
*ENE [http://wiki.laptop.org/images/a/ab/KB3700-ds-01.pdf KB3700 datasheet].<br />
<br />
<br />
The Quanta IL1 reference design seems to use ENE3310 controller. The q1d25i.rom was examined. The EC code is on 0xFFF00000 on One Mini A110. Its 64KB big HOLE0.ROM. <br />
<br />
[https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk/ 8051 simulator]<br />
<br />
[http://dev.laptop.org/git?p=projects/olpcflash;a=blob;f=olpcflash.c;hb=HEAD OpenEC Firmware] [http://wiki.laptop.org/go/OpenEC OpenEC Project]<br />
<br />
[http://www.cagnulein.com/tmp/eee.c-20080812 Example code] that makes use of the KB3310's "Index IO" access functions.<br />
<br />
More discussion and info on the ENE EC's: <br />
<br />
*[http://forum.eeeuser.com/viewtopic.php?pid=99076 eeeUser Discussion] <br />
*[http://code.google.com/p/eeetune/wiki/KBMemoryMap Memory map of ENE KB3310]<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de/wiki/Main_Page Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] More [http://www.a110wiki.de/wiki/CTL_IL1 CTL IL1 info] with tear-down pics. <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
There are still a few netbook designs currently on the market that use the VIA vx700 chipset. <br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
*[http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Laptop Survey ==<br />
<br />
This page attempts to list laptops to find out which one might be easiest to port coreboot to.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Vendor<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset<br />
! align="left" | Video<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | EC<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash Socketed<br />
! align="left" | Flash Type<br />
! align="left" | Still Made<br />
! align="left" | Major Obstacle<br />
! align="left" | Owner<br />
|- bgcolor="#eeeeee"<br />
| Panasonic || Toughbook&nbsp;CF-25 [[CF-25LJM8EAM]] || P166MMX || 430TX || MagicGraph 128ZV NM2093 || || Renesas 3886 || SST 29EE020 || 256 kB || no || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Libretto&nbsp;50M PA1243CM || P133 || custom FPGA || C&T 65550 || || || || || || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook PCG-C1XD || P2 400 || 443ZX || MagicMedia 256AV NM2200 || || || M29W004BT || 512 kB || no || || no || || [[User:Miernik|Miernik]] (broken)<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook PCG-C1X || P266MMX || 430TX || MagicMedia 256AV NM???? || || || || || || || no || || [[User:Miernik|Miernik]] (stolen)<br />
|- bgcolor="#dddddd"<br />
| Gericom || Webboy 340S2 || PIII || SiS630 || SiS630 || [http://www.national.com/pf/PC/PC87393.html PC87393VJG] || [http://www.national.com/pf/PC/PC87570.html PC87570] || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || || || [http://thread.gmane.org/gmane.linux.bios/13081 Norbert Schmidt]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD 14-C1700 || Intel Celeron 1.7 GHz || SiS650 || SiS65x/M650/740 || PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || no || No SIS650 docs || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook XE3(L) || PIII, 750 MHz || Intel 82371MB PIIX4M || ? || SMSC FDC37N869 || ? || ? || ? || no || PLCC || ? || ? || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-Siemens || Lifebook S-4572 || PIII, 750 MHz || Intel 82440MX || ATI Rage Mobility P/M [1002:4c52] || SMSC FDC37N769 || ? || Fujitsu MBM29F400T<sup>1</sup> || ? || no || SPI(?), TSOP(?) || no || Soldered ROM, EC || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#dddddd"<br />
| Dell || [[Dell Latitude CPi A366XT|Latitude CPi A366XT]] || PII, 360 MHz || Intel 440BX || MagicGraph 256AV [10c8:0005] || SMSC&nbsp;FDC37N958FR || in Super I/O || AM29F040B || ? || yes || PLCC || no || ... || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#eeeeee"<br />
| One || [http://www.a110wiki.de A110]] || VIA C7-M ULV 1.0 GHz || VIA VX800 || VIA VX800 || ? || ENE KB3310 || ? || ? || no || ? || no || Soldered ROM, EC || [[User:Uwe|Uwe Hermann]]<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br />
</small><br />
<br />
<br />
Further Links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some Laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further Links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=7826Laptop2009-01-08T05:01:26Z<p>Bari: /* Recent Progress of coreboot on Laptops */ added OpenEC link</p>
<hr />
<div>== Recent Progress of coreboot on Laptops ==<br />
<br />
The VIA vx700 and vx800 chipsets have recently become popular in many netbook designs. Most of these netbooks are being produced by [http://www.quantatw.com Quanta] for several different OEM's. <br />
<br />
VIA has recently released open documentation for the vx700 and vx800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal] and open documentation for the latest [http://www.x.org/docs/via/ Unichrome] graphics controllers. VIA has also released binary unichrome drivers with 2D and 3D accel support for Ubuntu 8.04 and 8.10 as well as source for 2D at [http://linux.via.com.tw/support/downloadFiles.action VIA Linux Portal]. <br />
<br />
VIA is currently developing coreboot support for the vx800 chipset. [http://www.openchrome.org/ openChrome] support including 2D and 3D accel is also in the works for many new chipsets including the vx700 and vx800. <br />
<br />
The remaining issue with supporting these and other similar netbooks may be open firmware support for the Embedded Controller (EC). The most common EC's in these netbooks are the KB3310, KB3910 and KB3920 from [http://www.ene.com.tw/en/index.asp ENE Technology]. The ENE EC's are 8051 based and are used to support keyboard scan, lid open/closed, battery charging, power management, etc. <br />
<br />
coreboot may work with the "stock" firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)? <br />
<br />
*ENE [http://wiki.laptop.org/images/a/ab/KB3700-ds-01.pdf KB3700 datasheet].<br />
<br />
<br />
The Quanta IL1 reference design seems to use ENE3310 controller. The q1d25i.rom was examined. The EC code is on 0xFFF00000 on One Mini A110. Its 64KB big HOLE0.ROM. <br />
<br />
[https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk/ 8051 simulator]<br />
<br />
[http://dev.laptop.org/git?p=projects/olpcflash;a=blob;f=olpcflash.c;hb=HEAD OpenEC Firmware] [http://wiki.laptop.org/go/OpenEC OpenEC Project]<br />
<br />
[http://www.cagnulein.com/tmp/eee.c-20080812 Example code] that makes use of the KB3310's "Index IO" access functions.<br />
<br />
More discussion and info on the ENE EC's: <br />
<br />
*[http://forum.eeeuser.com/viewtopic.php?pid=99076 eeeUser Discussion] <br />
*[http://code.google.com/p/eeetune/wiki/KBMemoryMap Memory map of ENE KB3310]<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de/wiki/Main_Page Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] The CTL IL1 is available in the USA at [http://www.amazon.com/dp/B001BAWIYE Amazon.com] <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
There are still a few netbook designs currently on the market that use the VIA vx700 chipset. <br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
*[http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Laptop Survey (Old) ==<br />
<br />
This page attempts to list laptops to find out which one might be easiest to port coreboot to.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Make<br />
! align="left" | Type<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset<br />
! align="left" | Video<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | Micro<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash Socketed<br />
! align="left" | Flash Type<br />
! align="left" | Still Made<br />
! align="left" | Major Obstacle<br />
! align="left" | Owner<br />
|- bgcolor="#eeeeee"<br />
| Panasonic || Toughbook&nbsp;CF-25 || [[CF-25LJM8EAM]] || P166MMX || 430TX || MagicGraph 128ZV NM2093 || || Renesas 3886 || SST 29EE020 || 256 kB || no || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Libretto&nbsp;50M || PA1243CM || P133 || custom FPGA || C&T 65550 || || || || || || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook || PCG-C1XD || P2 400 || 443ZX || MagicMedia 256AV NM2200 || || || M29W004BT || 512 kB || no || || no || || [[User:Miernik|Miernik]] (broken)<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook || PCG-C1X || P266MMX || 430TX || MagicMedia 256AV NM???? || || || || || || || no || || [[User:Miernik|Miernik]] (stolen)<br />
|- bgcolor="#dddddd"<br />
| Gericom || Webboy || 340S2 || PIII || SiS630 || SiS630 || [http://www.national.com/pf/PC/PC87393.html PC87393VJG] || [http://www.national.com/pf/PC/PC87570.html PC87570] || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || || || [http://thread.gmane.org/gmane.linux.bios/13081 Norbert Schmidt]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD || 14-C1700 || Intel Celeron 1.7 GHz || SiS650 || SiS65x/M650/740 || PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || no || No SIS650 docs || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook || XE3(L) || PIII, 750 MHz || Intel 82371MB PIIX4M || ? || SMSC FDC37N869 || ? || ? || ? || no || PLCC || ? || ? || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-Siemens || Lifebook || S-4572 || PIII, 750 MHz || Intel 82440MX || ATI Rage Mobility P/M [1002:4c52] || SMSC FDC37N769 || ? || Fujitsu MBM29F400T<sup>1</sup> || ? || no || SPI(?), TSOP(?) || no || No socketed PLCC, unknown EC || [[User:Uwe|Uwe Hermann]]<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br />
</small><br />
<br />
<br />
Further Links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some Laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further Links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=7825Laptop2009-01-08T04:44:38Z<p>Bari: /* Recent Progress of coreboot on Laptops */</p>
<hr />
<div>== Recent Progress of coreboot on Laptops ==<br />
<br />
The VIA vx700 and vx800 chipsets have recently become popular in many netbook designs. Most of these netbooks are being produced by [http://www.quantatw.com Quanta] for several different OEM's. <br />
<br />
VIA has recently released open documentation for the vx700 and vx800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal] and open documentation for the latest [http://www.x.org/docs/via/ Unichrome] graphics controllers. VIA has also released binary unichrome drivers with 2D and 3D accel support for Ubuntu 8.04 and 8.10 as well as source for 2D at [http://linux.via.com.tw/support/downloadFiles.action VIA Linux Portal]. <br />
<br />
VIA is currently developing coreboot support for the vx800 chipset. [http://www.openchrome.org/ openChrome] support including 2D and 3D accel is also in the works for many new chipsets including the vx700 and vx800. <br />
<br />
The remaining issue with supporting these and other similar netbooks may be open firmware support for the Embedded Controller (EC). The most common EC's in these netbooks are the KB3310, KB3910 and KB3920 from [http://www.ene.com.tw/en/index.asp ENE Technology]. The ENE EC's are 8051 based and are used to support keyboard scan, lid open/closed, battery charging, power management, etc. <br />
<br />
coreboot may work with the "stock" firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)? <br />
<br />
*ENE [http://wiki.laptop.org/images/a/ab/KB3700-ds-01.pdf KB3700 datasheet].<br />
<br />
<br />
The Quanta IL1 reference design seems to use ENE3310 controller. The q1d25i.rom was examined. The EC code is on 0xFFF00000 on One Mini A110. Its 64KB big HOLE0.ROM. <br />
<br />
[https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk/ 8051 simulator]<br />
<br />
[http://dev.laptop.org/git?p=projects/olpcflash;a=blob;f=olpcflash.c;hb=HEAD OpenEC Firmware]<br />
<br />
[http://www.cagnulein.com/tmp/eee.c-20080812 Example code] that makes use of the KB3310's "Index IO" access functions.<br />
<br />
More discussion and info on the ENE EC's: <br />
<br />
*[http://forum.eeeuser.com/viewtopic.php?pid=99076 eeeUser Discussion] <br />
*[http://code.google.com/p/eeetune/wiki/KBMemoryMap Memory map of ENE KB3310]<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de/wiki/Main_Page Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] The CTL IL1 is available in the USA at [http://www.amazon.com/dp/B001BAWIYE Amazon.com] <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
There are still a few netbook designs currently on the market that use the VIA vx700 chipset. <br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
*[http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Laptop Survey (Old) ==<br />
<br />
This page attempts to list laptops to find out which one might be easiest to port coreboot to.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Make<br />
! align="left" | Type<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset<br />
! align="left" | Video<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | Micro<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash Socketed<br />
! align="left" | Flash Type<br />
! align="left" | Still Made<br />
! align="left" | Major Obstacle<br />
! align="left" | Owner<br />
|- bgcolor="#eeeeee"<br />
| Panasonic || Toughbook&nbsp;CF-25 || [[CF-25LJM8EAM]] || P166MMX || 430TX || MagicGraph 128ZV NM2093 || || Renesas 3886 || SST 29EE020 || 256 kB || no || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Libretto&nbsp;50M || PA1243CM || P133 || custom FPGA || C&T 65550 || || || || || || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook || PCG-C1XD || P2 400 || 443ZX || MagicMedia 256AV NM2200 || || || M29W004BT || 512 kB || no || || no || || [[User:Miernik|Miernik]] (broken)<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook || PCG-C1X || P266MMX || 430TX || MagicMedia 256AV NM???? || || || || || || || no || || [[User:Miernik|Miernik]] (stolen)<br />
|- bgcolor="#dddddd"<br />
| Gericom || Webboy || 340S2 || PIII || SiS630 || SiS630 || [http://www.national.com/pf/PC/PC87393.html PC87393VJG] || [http://www.national.com/pf/PC/PC87570.html PC87570] || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || || || [http://thread.gmane.org/gmane.linux.bios/13081 Norbert Schmidt]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD || 14-C1700 || Intel Celeron 1.7 GHz || SiS650 || SiS65x/M650/740 || PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || no || No SIS650 docs || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook || XE3(L) || PIII, 750 MHz || Intel 82371MB PIIX4M || ? || SMSC FDC37N869 || ? || ? || ? || no || PLCC || ? || ? || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-Siemens || Lifebook || S-4572 || PIII, 750 MHz || Intel 82440MX || ATI Rage Mobility P/M [1002:4c52] || SMSC FDC37N769 || ? || Fujitsu MBM29F400T<sup>1</sup> || ? || no || SPI(?), TSOP(?) || no || No socketed PLCC, unknown EC || [[User:Uwe|Uwe Hermann]]<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br />
</small><br />
<br />
<br />
Further Links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some Laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further Links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]</div>Barihttps://www.coreboot.org/index.php?title=Laptop&diff=7824Laptop2009-01-08T04:26:43Z<p>Bari: added EC firmware links</p>
<hr />
<div>== Recent Progress of coreboot on Laptops ==<br />
<br />
The VIA vx700 and vx800 chipsets have recently become popular in many netbook designs. Most of these netbooks are being produced by [http://www.quantatw.com Quanta] for several different OEM's. <br />
<br />
VIA has recently released open documentation for the vx700 and vx800 chipsets at the [http://linux.via.com.tw/support/downloadFiles.action VIA Download Portal] and open documentation for the latest [http://www.x.org/docs/via/ Unichrome] graphics controllers. VIA has also released binary unichrome drivers with 2D and 3D accel support for Ubuntu 8.04 and 8.10 as well as source for 2D at [http://linux.via.com.tw/support/downloadFiles.action VIA Linux Portal]. <br />
<br />
VIA is currently developing coreboot support for the vx800 chipset. [http://www.openchrome.org/ openChrome] support including 2D and 3D accel is also in the works for many new chipsets including the vx700 and vx800. <br />
<br />
The remaining issue with supporting these and other similar netbooks may be open firmware support for the Embedded Controller (EC). The most common EC's in these netbooks are the KB3910 or KB3886 from [http://www.ene.com.tw/en/index.asp ENE Technology]. The ENE EC's are 8051 based and are used to support keyboard scan, lid open/closed, battery charging, power management, etc. <br />
<br />
coreboot may work with the "stock" firmware. This may still be a challenge because "we don't know what we don't know". Behavior at runtime is fairly standardized, but we don't know what we need to do for initialization - do we need to set up registers, put in tables, kick things, or will it all Just Work (TM)? <br />
<br />
*ENE [http://wiki.laptop.org/images/a/ab/KB3700-ds-01.pdf KB3700 datasheet].<br />
<br />
<br />
The Quanta IL1 reference design seems to use ENE3310 controller. The q1d25i.rom was examined. The EC code is on 0xFFF00000 on One Mini A110. Its 64KB big HOLE0.ROM. <br />
<br />
[https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk/ 8051 simulator]<br />
<br />
[http://dev.laptop.org/git?p=projects/olpcflash;a=blob;f=olpcflash.c;hb=HEAD OpenEC Firmware]<br />
<br />
[http://www.cagnulein.com/tmp/eee.c-20080812 Example code] that makes use of the KB3310's "Index IO" access functions.<br />
<br />
More discussion and info on the ENE EC's: <br />
<br />
*[http://forum.eeeuser.com/viewtopic.php?pid=99076 eeeUser Discussion] <br />
*[http://code.google.com/p/eeetune/wiki/KBMemoryMap Memory map of ENE KB3310]<br />
<br />
VIA has a list of many netbooks at [http://via.com.tw/en/products/notebook/notebook.jsp VIA Partner Mobility Devices]. <br />
<br />
VIA also has information on other mobile platforms at [http://via.com.tw/en/products/notebook/index.jsp VIA Mobility Platform]. <br />
<br />
The [http://www.a110wiki.de/wiki/Main_Page Quanta IL1] vx800 based reference design covers similar models/clones such as: <br />
<br />
*[http://www.one.de/shop/one-notebooks-one-mini-notebooks-c-213_214.html One Mini A110/A115/A120/A140/A150/A470] <br />
*[http://preview.tinyurl.com/5zbzl6 Airis Kira 100/350/740] <br />
*[http://www.norhtec.com/products/gecko/index.html Norhtec Gecko] <br />
*[http://www.pioneercomputers.com.au/products/configure.asp?c1=3&c2=12&id=2458 Pioneer DreamBook Light IL1] <br />
*[http://www.ctlcorp.com/v4/p-697-ctl-il1a-89-netbook-with-windows-xp-home.aspx CTL IL1] The CTL IL1 is available in the USA at [http://www.amazon.com/dp/B001BAWIYE Amazon.com] <br />
*[http://www.aci-asia.com/html/Ethos_7.html ACi Ethos 7] <br />
*[http://www.ilikeblue.net/products/umpc.htm BDSI Deep Blue H1]<br />
<br />
Other vx800 based netbooks: <br />
<br />
*[http://www.everex.com/products/cloudbook_max/cloudbook_max.htm Everex CloudBook MAX] <br />
*[http://www.fic.com.tw/product/ce2a1.aspx FIC CE2A1]<br />
<br />
There are still a few netbook designs currently on the market that use the VIA vx700 chipset. <br />
<br />
*[http://www.sylvaniacomputers.com/products.php?p=g Sylvania G] <br />
*[http://www.everex.com/products/cloudbook/cloudbook.htm Everex Cloudbook] <br />
*[http://www.fic.com.tw/product/ce260.aspx FIC CE260] <br />
*[http://www.fic.com.tw/product/ce268.aspx FIC CE268]<br />
<br />
There are also several AMD 690/600 laptops still available that may be candidates as well: <br />
<br />
*[http://reviews.cnet.com/laptops/acer-extensa-4420-5963/4505-3121_7-33361062.html Acer Extensa 4420] <br />
*[http://www.raondigital.com EVERUN NOTE]<br />
<br />
Intel Atom with i945 chipset netbooks: <br />
<br />
*[http://en.wikipedia.org/wiki/Aspire_One Acer Aspire One] <br />
*[http://en.wikipedia.org/wiki/MSI_Wind_PC MSI Wind] <br />
*[http://en.wikipedia.org/wiki/ASUS_Eee_PC ASUS eeePC]<br />
<br />
A few earlier coreboot discussions on laptops are linked here, you might get useful information out of them: <br />
<br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010985.html Any update on coreboot for laptops] <br />
*[http://comments.gmane.org/gmane.linux.bios/13081 Notebook 340s2 (sis630) 256k Flash] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-February/010972.html yet another reason to use coreboot in laptops I guess] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-April/011429.html coreboot laptop hunt wiki page] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-March/011140.html HP Pavillion ZV5000 (Laptop)] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2005-July/011942.html SA1100] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2003-September/004954.html Laptop with Sis 650 chipset] <br />
*[http://www.coreboot.org/pipermail/linuxbios/2006-September/015551.html coreboot on Laptops]<br />
<br />
== Laptop Survey (Old) ==<br />
<br />
This page attempts to list laptops to find out which one might be easiest to port coreboot to.<br />
<br />
{| border="0" style="font-size: smaller"<br />
|- bgcolor="#6699dd"<br />
! align="left" | Make<br />
! align="left" | Type<br />
! align="left" | Model<br />
! align="left" | CPU<br />
! align="left" | Chipset<br />
! align="left" | Video<br />
! align="left" | Super&nbsp;I/O<br />
! align="left" | Micro<br />
! align="left" | Flash Chip<br />
! align="left" | Flash Size<br />
! align="left" | Flash Socketed<br />
! align="left" | Flash Type<br />
! align="left" | Still Made<br />
! align="left" | Major Obstacle<br />
! align="left" | Owner<br />
|- bgcolor="#eeeeee"<br />
| Panasonic || Toughbook&nbsp;CF-25 || [[CF-25LJM8EAM]] || P166MMX || 430TX || MagicGraph 128ZV NM2093 || || Renesas 3886 || SST 29EE020 || 256 kB || no || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#dddddd"<br />
| Toshiba || Libretto&nbsp;50M || PA1243CM || P133 || custom FPGA || C&T 65550 || || || || || || || no || || [[User:Miernik|Miernik]]<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook || PCG-C1XD || P2 400 || 443ZX || MagicMedia 256AV NM2200 || || || M29W004BT || 512 kB || no || || no || || [[User:Miernik|Miernik]] (broken)<br />
|- bgcolor="#eeeeee"<br />
| Sony || Vaio&nbsp;Picturebook || PCG-C1X || P266MMX || 430TX || MagicMedia 256AV NM???? || || || || || || || no || || [[User:Miernik|Miernik]] (stolen)<br />
|- bgcolor="#dddddd"<br />
| Gericom || Webboy || 340S2 || PIII || SiS630 || SiS630 || [http://www.national.com/pf/PC/PC87393.html PC87393VJG] || [http://www.national.com/pf/PC/PC87570.html PC87570] || Winbond&nbsp;29C020 || 256 kB || yes || PLCC || || || [http://thread.gmane.org/gmane.linux.bios/13081 Norbert Schmidt]<br />
|- bgcolor="#eeeeee"<br />
| Highscreen || XD || 14-C1700 || Intel Celeron 1.7 GHz || SiS650 || SiS65x/M650/740 || PC87391(?) || ? || EON EN29F040(A) || 512 kB || yes || PLCC || no || No SIS650 docs || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#dddddd"<br />
| HP || Omnibook || XE3(L) || PIII, 750 MHz || Intel 82371MB PIIX4M || ? || SMSC FDC37N869 || ? || ? || ? || no || PLCC || ? || ? || [[User:Uwe|Uwe Hermann]]<br />
|- bgcolor="#eeeeee"<br />
| Fujitsu-Siemens || Lifebook || S-4572 || PIII, 750 MHz || Intel 82440MX || ATI Rage Mobility P/M [1002:4c52] || SMSC FDC37N769 || ? || Fujitsu MBM29F400T<sup>1</sup> || ? || no || SPI(?), TSOP(?) || no || No socketed PLCC, unknown EC || [[User:Uwe|Uwe Hermann]]<br />
|}<br />
<br />
<small><br />
<sup>1</sup> According to the vendor BIOS update tool.<br />
</small><br />
<br />
<br />
Further Links:<br />
<br />
* [http://tuxmobil.org/mylaptops.html Tuxmobil Laptop Survey]<br />
* [http://mcelrath.org/laptops.html Laptops/Notebooks with Linux Preinstalled]<br />
* [http://www.fsf.org/campaigns/free-bios.html The Free Software Foundation's Campaign for Free BIOS]<br />
<br />
== Who really makes your laptop? ==<br />
<br />
There are several various brands of laptops, but there are only a few actual laptop makers.<br />
<br />
Name brand companies like Hewlet Packard, Compaq, IBM, Dell, Gateway, Sony, Micron, Toshiba and others; including Alienware and Voodoo do not make their own laptops. The exceptions are Asus and Apple, and even Apple doesn't make all of their laptops.<br />
<br />
Original Design Manufacturers (ODM) make the laptops for Original Equipment Manufacturers (OEM). They in turn, add their preloaded hard drives and sell them to consumers. This is why a laptop is a bit more complicated to support with coreboot. The OEM's may not even have all the specifications for the laptop since the ODM has done all the design and assembly.<br />
<br />
Some Laptop ODMs are:<br />
<br />
* [http://www.quantatw.com Quanta] makes laptops for Sony, Dell, and IBM <br />
* [http://www.inventec.com/ Inventec] and [http://www.arima.com.tw/ Arima] make the Compaq line<br />
* [http://www.compal.com/ Compal] also makes IBM and Dell lines, as well as Hewlett Packard<br />
* [http://www.clevo.com.tw/ Clevo] makes the popular Alienware and Voodoo gaming laptops<br />
<br />
Further Links:<br />
<br />
* [http://www.laptopworldwide.com/laptops.html Makers of Laptops]<br />
* [http://tuxmobil.org/laptop_oem.html Laptop and NoteBook Manufacturer - OEM/ODM Relation Matrix]<br />
* [http://tuxmobil.org/reseller.html Where to Buy a Preinstalled Linux Laptop, Notebook, Mobile Phone or PDA? - Vendor Overview]</div>Barihttps://www.coreboot.org/index.php?title=Supported_Chipsets_and_Devices&diff=7814Supported Chipsets and Devices2009-01-03T18:47:59Z<p>Bari: </p>
<hr />
<div></div>Barihttps://www.coreboot.org/index.php?title=Supported_Chipsets_and_Devices&diff=7813Supported Chipsets and Devices2009-01-03T18:41:27Z<p>Bari: added note to mcp55</p>
<hr />
<div></div>Bari