On Mon, 2002-10-28 at 16:27, David Xiong wrote:
> Hello,
> The irq_tables.c dumped from normal BIOS only have information about the pci bus 0.
> I have a multimedia card which has a pci-to-pci bridge on itself. There are 2 pci
>devices
> on that card. So the two devices locate at bus 2. The slot_n
>Did you recalculate the checksum ??
Yes, the checksum has been recalculated.
>Where did you get the idea to set the the table like this?
I do not know how the irqs routed. So I guess I can set the irq table. It is
intresting that this way work on Elite K7SEM.
So I take it for granted it wi
on google, search for "VIA C3 datasheet PDF" :
http://216.239.53.100/search?q=cache:cjUXYbexFz4C:www.via.com.tw/en/viac3/c3
.jsp+VIA+C3+Processor+Datasheets&hl=zh-TW&ie=UTF-8
Regards!
CMZ
- Original Message -
From: "Andrew Ip" <[EMAIL PROTECTED]>
To: "CMZ" <[EMAIL PROTECTED]>
Cc: <[EMAI
On Mon, 2002-10-28 at 17:14, David Xiong wrote:
> >Did you recalculate the checksum ??
> Yes, the checksum has been recalculated.
>
> >Where did you get the idea to set the the table like this?
> I do not know how the irqs routed. So I guess I can set the irq table. It is
>intresting that th
When I boot Red Hat 7.2 with the normal BIOS of the Elite P6VEM3 mother board, the
BIOS will set the irqs into the multimedia card
and the card can work. I think the BIOS has no knowledge about the PCI-PCI bridge
specs.
When I boot from linuxbios, if I don't set the irq_tables.c , nobody wi
freebios/src/southbridge/via/vt8231/southbridge.c
- updated to use pci_find_device
-Andrew
--
Andrew Ip
Email: [EMAIL PROTECTED]
Tel:(852) 2542 2046
Fax:(852) 2542 2036
Mobile: (852) 9201 9866
Cwlinux Limited
Unit 202B 2/F Lai Cheong Factory Building,
479-479A Castle Peak Road,
Lai Chi
On Mon, 28 Oct 2002, Stefan Reinauer wrote:
> > http://www.missl.cs.umd.edu/~agnew/anopenbios.zip
> The requested URL /~agnew/anopenbios.zip was not found on this server.
My mistake. Fixed.
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clu
Hello from Gregg C Levine
Adam, please define that none-sense for me. I have most of the things
here, from that guy's site. My only objections are for the assembler he
chose. I felt he should have used the assembler that's at the core of
the binary utilities of the GNU set of tools, instead of A86.
Hello again from Gregg C Levine
Sorry, Adam, small typo in that statement. It should be "non-sense",
not, "none-sense". Same for all of us. I just looked at his site, and it
still says that other assemblers are not supported. I wonder what he
means by that?
---
Gregg C Levine [EMAIL
This is pretty off topic, but...
http://www.info-zip.org/pub/infozip/FAQ.html#unshrink >
(this applies to the unzip that ships with most linux distributions)
"Why does UnZip say "`shrink' method not supported"?
The `shrink' compression method is encumbered by a patent. Although it
appears that
Hello again from Gregg C Levine
Point taken. I did go over his website the first time I heard about his
product. And that point you found was found, but I completely forgot it,
until now. That sticky issue that Info-Zip is grouching about sounds
about right. However, the folks at WinZip Computing,
Hi:
Someone has experience working with LTSP and Linuxbios?
Ltsp (www.ltsp.org) is a powerfull Thin Client solution, were the server makes the hard work.
LinuxBios looks like the perfetc tool to buil expensive cluster servers for LTSP solutions.
Regards
Ricardo StrauchDo You Yahoo!?
Todo lo que q
Ricardo,
> Someone has experience working with LTSP and Linuxbios?
> Ltsp (www.ltsp.org) is a powerfull Thin Client solution, were the server makes the
>hard work.
> LinuxBios looks like the perfetc tool to buil expensive cluster servers for LTSP
>solutions.
LinuxBIOS does work with LTSP. I ha
On Monday 28 October 2002 3:55 pm, Ricardo Strauch wrote:
> Hi:
>
> Someone has experience working with LTSP and Linuxbios?
>
> Ltsp (www.ltsp.org) is a powerfull Thin Client solution, were the server
> makes the hard work.
>
> LinuxBios looks like the perfetc tool to buil expensive cluster serve
I have been doing Ltsp for over 1 year in production. Using
linuxbios on ltsp clients has many advantages, especially the quick
boot time.
There should be no problem using linuxbios for ltsp since all ltsp
needs is etherboot.
Clustering for the servers would also be favorable. The most
efficient
"Munjun Kang" <[EMAIL PROTECTED]> writes:
> Dear Eric W. Biederman.
>
> First of all, thanks for your reply.
> I apply some other schem to linuxbios.
> This is my boot process.
An unreliable scheme, that does not provide the opportunity for
running anything except the linux kernel. This is why
I got such a card , does LinuxBios work on it ?
Hi,
(B
(BAfter the lart project, I would like to know if some one has done a board
(Bwith SA1110 and where I can found:
(B1) schematic, gerber, orcad files
(B2) Bios and Linux software
(B3) tools (compilator, linker, debugger)...
(B4) Application (do you know if there is a list of Lart/
Greetings,
I have built a firmware chooser as a standalone elf image. Currently, it
only concerns itself with tagged ELF flash images, but there is no reason
it can't be generalized. The idea is that multiple choices of payloads are
pre-pended with a tag including a signature and an ascii descript
On Sun, Oct 27, 2002 at 07:05:58PM -0500, Adam Sulmicki wrote:
> you can find nice example how to use it in linux sources
> (some file in linux/arch/i386/boot, head.S IIRC)
Using it is the easy part, I had to implement it. Fortunately that project
got dropped before I tore all my hair off. :)
Hello from Gregg C Levine
Well, ah, I can't think of any. For my part, you've put in everything it
needs, except the hardware itself. Right now that is. Later? I won't
know until I try out Linux BIOS on an appropriate platform, and I'm
still selecting one of those.
---
Gregg C Levi
Has anyone started on LinuxBIOS support for any flavor of the Intel 845
chipsets?
The 845E and the 845GV are my interests.
Bari
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
This is mostly for Adam Sulmicki for the benefit of our current project,
but it's been about a year since it was mentioned last so I felt it
wouldn't help to reiterate (i know i forgot) that there exists another
open source bios, tinyBIOS
http://www.pcengines.com/tinybios.htm
and since his zip fi
On 24 Oct 2002, Eric W. Biederman wrote:
> make ide_disk.elf
> Or in the normal case of wanting the nic driver as well.
> make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
no target like that exists in the latest cvs for the 5.1 tree.
Also, it seems to me that if I set up
On Tue, 29 Oct 2002, Andrew Ip wrote:
> LinuxBIOS does work with LTSP. I have tested it with m758 and m810 boards.
what failed? I have been talking to the ltsp guys for a while about doing
this; what's missing?
ron
___
Linuxbios mailing list
[EMAIL P
I just built a working bios from the cvs tree for P4DPR!
This is the normal, not the fallback.
I might just take the final step ... once I resolve the etherboot
problems.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mail
Ron,
> > LinuxBIOS does work with LTSP. I have tested it with m758 and m810 boards.
> what failed? I have been talking to the ltsp guys for a while about doing
> this; what's missing?
It works!!!
-Andrew
--
Andrew Ip
Email: [EMAIL PROTECTED]
Tel:(852) 2542 2046
Fax:(852) 2542 2036
Mob
On Tue, 29 Oct 2002, Andrew Ip wrote:
>
> > > LinuxBIOS does work with LTSP. I have tested it with m758 and m810 boards.
Ron can'g read!
So andrew I know you have lots of spare time but can you give me a hint of
what you did for LTSP? etherboot?
thanks
ron
__
This is great.
Our little lnxi cluster is totally supported from CVS. Many thanks to Eric
for the port, and to Steve James who shook out some final nits.
Also, note that Steve James has integrated the Intel motherboard into
LinuxBIOS as well.
ron
___
Ronald G Minnich <[EMAIL PROTECTED]> writes:
> On 24 Oct 2002, Eric W. Biederman wrote:
>
> > make ide_disk.elf
> > Or in the normal case of wanting the nic driver as well.
> > make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
>
> no target like that exists in the latest
Adam Sulmicki <[EMAIL PROTECTED]> writes:
> FWIW, here's summary what I was able to gather so far
>
> > And the format of the GDT is:
> > dummy
> > GDT location
> > source GDT entry
> > target GDT entry
> > BIOS CS
> > BIOS SS
>
> ok, I think I got it nailed down, how about the way it is below?
On 28 Oct 2002, Eric W. Biederman wrote:
> > > make ide_disk.elf
> > > Or in the normal case of wanting the nic driver as well.
> > > make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
> >
> > no target like that exists in the latest cvs for the 5.1 tree.
>
> Try it. It is
Ronald G Minnich <[EMAIL PROTECTED]> writes:
> On 28 Oct 2002, Eric W. Biederman wrote:
>
> > > > make ide_disk.elf
> > > > Or in the normal case of wanting the nic driver as well.
> > > > make eepro100--ide_disk.nrv2belf (nrv2b is the upx compression algorithm)
> > >
> > > no target like that ex
On 28 Oct 2002, Eric W. Biederman wrote:
> Oh, duh. The difference is:
> make bin32/ide_disk.elf
Sorry! Should have tried that :-(
thanks
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Mon, 28 Oct 2002, steven james wrote:
> Does any of this belong in the LinuxBIOS tree? (utils, contrib, other)?
it seems to me that you have built a useful utility, so if you want to
name it, put a man page in there, and commit it, that would be fine by me.
ron
__
35 matches
Mail list logo
