OpenBIOS March 2000

openbios@openbios.org

26 participants
40 discussions

opening tgz and Tar files with winzip95 7.0
by Ross 02 Mar '00

02 Mar '00

Help Anyone: I get the following error message when using winzip95 version 7.0 when trying to unzip the following file stpc-bios-0.1.42..1.tgz (Error Reading After Processing 0 Entries) can someone out there help me out with this one. Winzip95 say's that it can handle these file but its not. //Ross

2 1

RE: [OpenBIOS] opening tgz and Tar files with winzip95 7.0
by Marcus Gossner 02 Mar '00

02 Mar '00

>Help Anyone: > > > >I get the following error message when using > >winzip95 version 7.0 when trying to unzip the following file > >stpc-bios-0.1.42..1.tgz (Error Reading After Processing 0 Entries) > >can someone out there help me out with this one. Winzip95 say's > >that it can handle these file but its not. > >//Ross > I unpacked it with WinZip 7.0 SR-1 (1285g) without any problems (german version of WinZip). Marcus - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

AW: [OpenBIOS] opening tgz and Tar files with winzip95 7.0
by Winter Jörg 02 Mar '00

02 Mar '00

>Help Anyone: >I get the following error message when using >winzip95 version 7.0 when trying to unzip the following file >stpc-bios-0.1.42..1.tgz (Error Reading After Processing 0 Entries) Just tried it on my Win with winzip7.0sr1. Works fine. Maybe you must re-install win (like always)? or have a corrupt file? got it via ftp? had "bin" switch on?? BTW: gnu unzip and tar are available for DOS on alot of linux distr. CD´s pick one an dump winzip ... - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

Re: [OpenBIOS] STPC BIOS sources posted
by Ross 02 Mar '00

02 Mar '00

Hi, jeff: I get the following error message when using winzip95 version 7.0 when trying to unzip the STPC BIOS sources. (Error Reading Reader Processing 0 Entries) I konw you are a great hacker. We are here to help each other wether the problem is big or small. //Ross ---------- > From: Jeff Garzik <jgarzik(a)mandrakesoft.com> > To: openbios(a)elvis.informatik.uni-freiburg.de > Subject: Re: [OpenBIOS] STPC BIOS sources posted > Date: Wednesday, March 01, 2000 9:23 PM > > Ross wrote: > > > > Jeff, can you please send me a copy of this > > file that I can unzip with winuzip for windoze > > 95. Thank you. > > winzip will unpack tar.gz files. beyond that, you're on your own. > > you should really be able to figure this stuff out, if you want to hack > on a BIOS.. :) > > -- > Jeff Garzik | Rule 1: > Building 1024 | There is no cabal. > MandrakeSoft, Inc. | > - > To unsubscribe: send mail to majordomo(a)freiburg.linux.de > with 'unsubscribe openbios' in the body of the message

1 0

Re: [OpenBIOS] asm code
by Edwin Rhodes 01 Mar '00

01 Mar '00

what code do i need to zero 0b8000 - 0bfff0. thanks edwin ----- Original Message ----- From: James <jvh(a)uclink4.berkeley.edu> To: <openbios(a)elvis.informatik.uni-freiburg.de> Sent: Monday, February 21, 2000 3:27 PM Subject: Re: [OpenBIOS] asm code > > hi sorry this is slightly off topic but i need some asm code to clear > > the screen in the linux kernel -- just after it says uncompressing > > linux. how would i implement this in assembler, that would compile > > under gas. thanks edwin > > By the time it says "uncompressing linux" it is already in 32 bit mode C > code (inflate.c). It is writing to the screen directly at memory address > 0b8000. To clear the screen, just zero 0b8000 - 0bfff0. > > > ps. will you eventually implement all the standard bios calls so that > > other os's such as dos etc will run under open bios? or will it be > > just a bios for linux? thanks and good luck. > > I believe the goal is to get support for the 32 bit OSs that don't use the > BIOS, like WinNT, BeOS, Linux, BSD, and others (at least I think that is > the goal and I think those OSs don't use the BIOS). > > - James > > - > To unsubscribe: send mail to majordomo(a)freiburg.linux.de > with 'unsubscribe openbios' in the body of the message > - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

3 2

Fw: aros screen problem on x86/native
by Jaime Dias 01 Mar '00

01 Mar '00

> > hi, > we are having problem to put aros on native x86 i want to know if someone > here could help. > > > You cannot see workbench screen yet because its size is 800x600 so it's > impossible to show it on vga screen (max 640x480) unless we add some > parameters passed to LateIntuiInit. Besides there are still some problems > with vga.hidd - it still hangs during OpenWindow. Aah! And there are some > problems with workbench background. My hidd in PutPixel (or DrawPixel I > don't remember now which is correct) puts color 0 (black) on the screen > instead of the one from bitmap (don't know why - screenbar is show as it > should). > > vga.hidd is a layer between the hardware idependent and the hardware > dependent code > > anyhow to get the 800x600 booting generic svga cards on x86? > > thanks in advance, > jaime dias - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

(some help) Fw: [AROS-Dev] i386/native status
by Jaime Dias 01 Mar '00

01 Mar '00

hi, sorry in advance, but we have only one person on aros team (www.aros.org) that is handle the x86 port, and it apears some trouble now, it's not polite to invite developers on other projects, but i read this list for a while and maybe there is someone who here who could help us in this issue. port aros to x86 is very important for the project, thats why i am posting this mail. (ggi on gfx handle side and openbios on how treat the hardware and gfx on other side) > > But we still don't have the most important (and easy to write > indeed) thing - ide.hidd (ide.device scsi.device....) so we are anable to > start system - we can add dos.library to residentlist but it will not see > any drives. Besides vga.hidd is either buggy or missing some methods so it > can't work propertly at this moment. It do draw point but it don't show a > window (on the other hand it can open screen and alloc colors propertly). > > The most important thing we are missing is TIME (true for me). My last > update was due to my 1.5 week long vacation. Sitting whole nights > (well.. not whole - only to 5 AM) at my PC, fighting with bugs and reading > the hardware books - that's how I spend this time. I know many more than > one month ago but now what I need is time. Without it I can't work. > > > Tell me what the bus.hidd should do and then I'll try to write it. I have > many hardware references at home so I can work (time, time, > time....). irq.hidd would be very easy to write (most of it is placed now > in exec.library, just look at config/i386-native/exec/irq.S and other .S > files) but what we need is ready and well-described idea of it. > > > If you could find something about DMA mode in all new harddrives it would > be great... One could help Frederic with ide.device - working alone is > much slower. > sorry bother, jaime dias - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

Re: AW: [OpenBIOS] Aladdin V chipset
by dave＠denial.force9.co.uk 01 Mar '00

01 Mar '00

Burl Nyswonger <burl(a)watchguard.com> wrote: > 2) high-level (ie: C and Forth) -- It would be nice if there > could be some way to abstract the chipset "advanced" features > into the OpenFirmware device tree. If not, this is still > where I think the "performance" related chipset initialization > should happen. Ugh, no. I spent some time moving the PCI optimisation from the kernel to userspace (see http://linux.powertweak.com). Moving this to BIOS space would not make much sense. The BIOS should contain enough code to get the system into a sane enough state to boot a kernel, and nothing more. Another problem with PCI tweaking, is that some options are motherboard specific. You have no way of detecting if that option is going to work. When a motherboard manufacturer licenses a BIOS from a vendor, they get source with #defines to tell them how certain parts of the board work. How the data/address lines are decoded for example.. Asides from the mobo manufacturer, no-one is going to know how a memory bank has been wired on their board, so they won't know the order in which certain things have to be performed. The only way you can offer this to users is in a 'try and see' approach. Such a tactic does NOT belong in BIOS land. regards, -- Dave. - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

STPC BIOS sources posted
by Jeff Garzik 01 Mar '00

01 Mar '00

free bios hackers-- Johan Rydberg has kindly allowed me to posted his GPL's STPC BIOS sources. The code is early work and incomplete, but may be useful to people here... I have been hacking on this instead of OpenBIOS lately, as it seems easier to use these stpc source to create a BIOS for the i430FX. Download from http://gtf.org/garzik/bios/ Jeff (copied to linux-kernel as there has been quite a bit of interest in BIOS sources there too) -- Jeff Garzik | Rule 1: Building 1024 | There is no cabal. MandrakeSoft, Inc. | - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

1 0

Aladdin V chipset
by Burl Nyswonger 01 Mar '00

01 Mar '00

I have begun to hack on OpenBIOS and am looking to add support for x86 and the Aladdin V chipset (ie: Super Socket7, Asus P5A, etc...). If anyone else has started work on this, or plans to, it would be nice to talk. -- Burl. - To unsubscribe: send mail to majordomo(a)freiburg.linux.de with 'unsubscribe openbios' in the body of the message

6 11