People are definitely beginning to understand the power of using linux
as your bootloader ...
>From the article:
"The new Technologic Systems Bootloader is totally Linux-based,
enabling much more control over the system through all the standard
Linux utility commands from inside the bootloader itself. Meanwhile,
it delivers fast bootup time, as short as 1.1 seconds, and small
footprint, not only meeting the requirements of the real-world
embedded systems, but delivering additional flexibility and power
instead. After all, it is Linux booting Linux.
The "bootload" facility may be useful for kernel developers, since
they now have a faster way to test their new kernels without rebooting
the whole system. In case a fast bootup solution is not being used,
developers benefit from the use of the "bootload" program given that
the time spent with firmware loading will be saved.
Also, the new Bootloader solution allows the use of standard shell
scripts for the programmatic selection of appropriate kernels, Linux
initrd's, and kernel command line arguments for maximum flexibility.
Click on the link below and find out how the TS-7400 takes advantage
of these features in order to provide multiple booting options via
Linux shell scripts:"
ron
---------- Forwarded message ----------
Date: Jan 10, 2007 9:21 AM
Subject: 1.1 sec from power on to Linux shell (busybox) prompt
To: ron minnich <rminnich(a)gmail.com>
I know these guys provided the lunchbox boards you described in your Linux
Journal article. I like how they accelerated flash boot by implementing HW
ECC in the CPLD. Nice work. This would have been nice in OLPC.
http://www.embeddedarm.com/linux/linuxbootloader.htm
I was excited to discover this project; it looks like good work. I did have
a few comments / questions:
On the list of benefits on the front page it says: "Avoids the need for a
slow, buggy, proprietary BIOS." I would add to this that it gives the end
user freedom from invisible functionality black holes. For example, my
laptop BIOS will on only initiate suspend-to-disk on timeout; there is no
way for me to invoke it on demand (and there is no way for me to update the
existing BIOS to add the needed functionality unless I can reverse engineer
the BIOS at great risk to my system). With LinuxBIOS presumably I would have
some recourse.
I am surprised that the list of payloads is not comprehensive; ie.
apparently Linux BIOS doesn't provide a straight boot from MBR. This
confused me. If this is not a goal, I would suggest making it a goal. This
reflects my own philosophy that end-user interests are best served by
compatibility.
I would also suggest a feature list on the webpage, so that passers-by like
me can see at a glance if you intend to support things like suspend-to-disk
(since the trend is to move s4 functionality to the OS).
Best regards,
Chris
_________________________________________________________________
Dave vs. Carl: The Insignificant Championship Series. Who will win?
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://da…
Hi
I want to run LinuxBIOS on an NCR-7456 POS PC. It`s mainboard is said
to be "Tiger MVP" (http://developer.novell.com/yes/75294.htm) and it
doesn`t seem to be on the SupportedMainboards list. However it`s
equipped with a VT8601A northbridge and VT82C686 southbridge. It also
has a 39VF040 flash chip soldered onboard. The northbridge is said to
be supported by LinuxBIOS but the VT82C686 has a question mark in the
SupportedChipsets table (for linuxbios v1) and isn`t mentioned at all
on the list of devices supported by LinuxBIOS v2. If so, what are the
odds of successfully running LinuxBIOS on this machine ? The BIOS flash
is soldered to the mainboard so it won`t be easy to reflash when
something goes wrong. If the southbridge chip (VT82C686) isn`t
supported what minimal code must be written for it to work ? I assume
that rs232 support is crucial for further development.
I have 2 of those machines, so I`m can experiment a little on one of
them. The second machine has already Linux installed (standard BIOS
though) and here is it`s lspci output:
gammu ~ # lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia]
(rev 05)
Flags: bus master, medium devsel, latency 8
Memory at fd000000 (32-bit, prefetchable) [size=16M]
Capabilities: [a0] AGP version 2.0
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
(prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: fb100000-fc7fffff
Prefetchable memory behind bridge: 10000000-100fffff
Capabilities: [80] Power Management version 2
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
Subsystem: VIA Technologies, Inc. Unknown device 0668
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at 1860 [size=16]
Capabilities: [c0] Power Management version 2
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 1a) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at 1800 [size=32]
Capabilities: [80] Power Management version 2
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 1a) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at 1820 [size=32]
Capabilities: [80] Power Management version 2
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
40)
Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
Flags: medium devsel, IRQ 9
Capabilities: [68] Power Management version 2
00:0d.0 Ethernet controller: National Semiconductor Corporation DP83815
(MacPhyter) Ethernet Controller
Subsystem: National Semiconductor Corporation DP83815
(MacPhyter) Ethernet Controller
Flags: bus master, medium devsel, latency 90, IRQ 9
I/O ports at 1400 [size=256]
Memory at fb000000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at 10100000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
00:10.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
0a)
Subsystem: Creative Labs SBLive! 5.1 Digital Model SB0220
Flags: bus master, medium devsel, latency 64, IRQ 15
I/O ports at 1840 [size=32]
Capabilities: [dc] Power Management version 1
00:10.1 Input device controller: Creative Labs SB Live! Game Port (rev
0a)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 64
I/O ports at 1878 [size=8]
Capabilities: [dc] Power Management version 1
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1
(rev 6a) (prog-if 00 [VGA])
Subsystem: Trident Microsystems CyberBlade/i1
Flags: fast Back2Back, 66MHz, medium devsel, IRQ 7
Memory at fc000000 (32-bit, non-prefetchable) [size=8M]
Memory at fb100000 (32-bit, non-prefetchable) [size=128K]
Memory at fb800000 (32-bit, non-prefetchable) [size=8M]
[virtual] Expansion ROM at 10000000 [disabled] [size=64K]
Capabilities: [80] AGP version 2.0
Capabilities: [90] Power Management version 1
I can also provide dmesg output, exact chip types, dmesg output and any
information that is neccessary. Unfortunately I didn`t find any
additional specs for this machine apart from marketing gibberish. But
I`ll keep looking.
--
Maciej Grela <jid:thermal@jabber.wroc.pl>
counter.li.org: 319794
#24: Remove all files which have a GPL-incompatible license
------------------------+---------------------------------------------------
Reporter: uwe | Owner: somebody
Type: defect | Status: new
Priority: blocker | Milestone: Resolve license issues
Component: code | Version: v2
Resolution: | Keywords:
Dependencies: |
------------------------+---------------------------------------------------
Comment (by anonymous):
Replying to [ticket:24 uwe]:
> Obviously, any file in svn which has a license which is GPL-incompatible
has to be removed. In such a case we can either live with it, rewrite the
file from scratch, or use another implementation which has a proper
license (if available).
jhgdjgs
--
Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/24#comment:2>
LinuxBIOS <http://www.linuxbios.org/>
#24: Remove all files which have a GPL-incompatible license
------------------------+---------------------------------------------------
Reporter: uwe | Owner: somebody
Type: defect | Status: new
Priority: blocker | Milestone: Resolve license issues
Component: code | Version: v2
Resolution: | Keywords:
Dependencies: |
------------------------+---------------------------------------------------
Comment (by anonymous):
Replying to [ticket:24 uwe]:
> Obviously, any file in svn which has a license which is GPL-incompatible
has to be removed. In such a case we can either live with it, rewrite the
file from scratch, or use another implementation which has a proper
license (if available).
--
Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/24#comment:1>
LinuxBIOS <http://www.linuxbios.org/>
This is my machine information:
CPU
Biostar P4TSV-A01 VER:1.0
Pentium 4 2.8Ghz
Socket 478
Chipset
North Bridge: Intel 865G
South Bridge: Intel ICH5
I'm sorry that I can't provide the Linux lspci output for my system.
Super I/O
ITE IT8712F
BIOS
Award legal BIOS
URL to the mainboard specifications page
http://www.biostar.com.tw/products/mainboard/board.php?name=P4TSV
Hope this information is useful. Thank you.
Yours sincerely,
Olivia Cond.