Bari Ari | 1 Mar 2003 01:06

LinuxBIOS Laptop

Here's a nice candidate to build a LinuxBIOS laptop.

http://www.xbitlabs.com/news/story.html?id=1046444411

The site is currently /.ed but the specs are:

ECS announced recently its DeskNote i-Buddie A980 mobile desktop PC, the 
first ever mobile barebone computer. It features no display, no CPU, no 
RAM and no HDD, but only the case with keyboard and touchpad. The 
indisputable trump of the novelty is that you are free to install the 
most high-end and cutting-edge hardware, or you may buy not really 
expensive components that are enough for your needs.

Here is the list of i-Buddie A980 technical peculiarities:

* Supports Socket 478 Pentium 4 / Celeron processors with 400/533MHz FSB 
with 3.06GHz clock-speed and above;
* SiS650 chipset with SiS962 I/O controller;
* 1 DIMM slot for up to 1GB of PC2100 or PC2700 DDR SDRAM memory.
* Integrated graphics core, ability to install NVIDIA GeForce4 Go420 
mobile graphics card.
* 2-channel ATA-100/66/33 integrated controller;
* Includes an 8x DVD-ROM drive;
* Free bay for 2.5 HDD;
* 4 USB 2.0 ports;
* FireWire (IEEE1394) port ;
* IR port with transfer rate up to 115.2Kbit/s;
* 10/100Mbit/s Ethernet adapter and connector;
* Integrated 56K modem;
* 6-channel audio solution and built-in speakers;
(Continue reading)

Mark Wilkinson | 1 Mar 2003 16:56
Picon

Re: flash_rom.c

Hi Ron,
	I've updated the patch slightly to add a routine to enable flash writes on 
the epia mainboard with out the need for the seperate setpci command.

Mark

On Friday 28 Feb 2003 22:13, Ronald G. Minnich wrote:
> thanks for the patch!
>
> I'll try to get it in today or monday.
>
> ron
--- freebios/util/flash_and_burn/flash_rom.c	Fri Feb 28 17:21:37 2003
+++ mod-freebios/util/flash_and_burn/flash_rom.c	Sat Mar  1 15:37:40 2003
 <at>  <at>  -146,6 +146,30  <at>  <at> 
   return 0;
 }

+int
+enable_flash_epia(struct pci_dev *dev, char *name) {
+/* register 40.b gets bit 4 set to enable flash access
+ * information from README file for epia mainboard
+ *
+ * Should I put a check to make sure it only gets set on device 0:11.0 ?
+ * 
+ */
+  unsigned char old, new;
+  int ok;
+
+  old = pci_read_byte(dev, 0x40);
(Continue reading)

Ronald G. Minnich | 2 Mar 2003 03:07

Re: flash_rom.c

Thanks for that too

anyone who has an 'enable write' patch for the flash_rom.c program, I'll 
take it.

ron

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Adam Agnew | 2 Mar 2003 04:47
Picon
Favicon

Re: About ADLO


You add the Bochs BIOS and the video BIOS to the ROM, NOT replacing the
LinuxBIOS. In this set up, LinuxBIOS does all the hardware initialization,
and the Bochs BIOS does all the legacy BIOS support. ADLO is just a small
glue that holds them together.
At start up, LinuxBIOS runs to initialize the hardware, then it passes
control to ADLO. ADLO sets up an environment which Bochs BIOS will
understand a bit better. Than Bochs BIOS gets control, and it populates
the BIOS interrupt table and passes control to your bootloader (such as
Grub). From there, things function for the most part as you're used to on
a commercial desktop BIOS.

- Adam Agnew

On Fri, 28 Feb 2003, Xavier Pegenaute wrote:

> Hi again,
>
> i'm not sure of how ADLO work ..., to work with ADLO, i need a Matsonic
> motherboard with a LinuxBios installed, once time i have this, i make
> the new elf file with a bios of Bochs and a Video Bios, and after i put
> these files overwriting the LinuxBios ..? or Adding these files to rom
> bios ?, if i add i'll have two bios code runing (first of the LinuxBios,
> and after of Bochs) is not there problems with it ?.
>
> Really is possible make work the Bochs Bios like a normal Bios ..?, they
> have code that only work with Bochs, like an outport to INFO_PORT ...
>
> Regards.
> Xavi.
(Continue reading)

Gregg C Levine | 3 Mar 2003 02:27
Picon

PCD-897-Bare with one DOC

Hello from Gregg C Levine
Here's a question that I think someone can answer. 
I've recently obtained a PCD-897-Bare from an individual that I know
on the Linux-MTD list. The Disk On Chip was formatted as a 2MB device,
with the first 4K as the boot code, and at that I'm guessing. 

Now here is the question: How can I reset it from being reported as a
Drive C device, to a Drive D device? I can provide the details of the
host computer, on request, and off list.

-------------------
Gregg C Levine hansolofalcon <at> worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Felix Radensky | 3 Mar 2003 16:41

VxWorks boot

Hi, folks

After a break I'm back to my task of using LinuxBios to
boot VxWorks and I have the following problem.

As I mentioned in my previous posts, VxWorks loader
insists on beeing loaded at physical address 0x8000. The
loader image size is 576K, and when loaded to 0x8000 it
overrides areas used by LinuxBios itself, so I cannot even
reach the code in LinuxBios that jumps to kernel entry
point. I have verified that  68000 bytes can be copied to
0x8000, but 70000 cannot.

If I'm reading ldscript.ld correctly, LinuxBios uses memory
at 0x4000 for its  data+bss, heap and stack. My question is:
how can I modify this file to allow loading of VxWorks bootloader.

Any other ideas are also welcome.

TIA.

Felix.

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Ronald G. Minnich | 3 Mar 2003 16:54

Re: VxWorks boot


remind me: are you using elf image boot format or the old fashioned stuff. 

the elf image boot stuff that Eric did will handle the problems you are 
having. The old stuff is too primitive to do that.

ron

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Felix Radensky | 3 Mar 2003 17:28

Re: VxWorks boot

Hi, Ron

Currently I'm using the old stuff.

Thanks.

Felix.

Ronald G. Minnich wrote:

>remind me: are you using elf image boot format or the old fashioned stuff. 
>
>the elf image boot stuff that Eric did will handle the problems you are 
>having. The old stuff is too primitive to do that.
>
>ron
>
>  
>

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Ronald G. Minnich | 3 Mar 2003 17:30

Re: VxWorks boot

On Mon, 3 Mar 2003, Felix Radensky wrote:

> Currently I'm using the old stuff.

that's going to take some work then. 

I had to make a stupid, simple tool to convert plan9 kernels to elfimage, 
and if I can find it I will send it to you.

ron

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Nathanael Noblet | 3 Mar 2003 18:34
Picon

Re: Suggestions


On Thursday, February 27, 2003, at 09:44  AM, Steve Gehlbach wrote:
>
> Linuxbios support of vga on boot is not there yet, work ongoing.

Does vga come up after the kernel takes control?? Is that what you mean 
vga on boot? Seeing the LinuxBios stuff through the VGA adapter?

--

-- 
Nathanael Noblet
Gnat Solutions
4604 Monterey Ave NW
Calgary, AB
T3B 5K4

T/F 403.288.5360
C 403.809.5368

http://www.gnat.ca/

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


Gmane