From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <ak@suse.de>, Dave Jones <davej@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: arch/i386/boot rewrite, and all the hard-coded video cards
Date: Mon, 30 Apr 2007 21:41:29 -0600 [thread overview]
Message-ID: <m1d51l1a8m.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4636B227.2020403@zytor.com> (H. Peter Anvin's message of "Mon, 30 Apr 2007 20:21:11 -0700")
"H. Peter Anvin" <hpa@zytor.com> writes:
> Eric W. Biederman wrote:
>> Andi Kleen <ak@suse.de> writes:
>>
>>>> Not that the x86 BIOS is bad. It is nearly a marvel in it's simplicity
>>>> and ubiquitousness,
>>> Simplicity? That must be why x86 motherbords are shipping with (compressed)
>>> 8MB BIOS flash chips now.
>>
>> Those would be 8 megabit chips, and those would be server motherboards
>> you are looking. Most likely the ones that are starting to think ahead
>> to EFI support.
>>
>
> No, 4-8 MB chips are starting to be deployed, but the bulk is for
> OS-less applications.
I don't doubt that there are some rare systems with very large
capacity flash chips. However the size of all BIOS chips are measured
in bits. Anyone talking about the capacity of BIOS chips in bytes
and not bits always raises a red flag with me because that is a very
common mistake.
I would be very surprised if the high volume commodity boards have
exceeded 8 megabits.
Eric
next prev parent reply other threads:[~2007-05-01 3:41 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 1:33 H. Peter Anvin
2007-05-01 1:40 ` Jeff Garzik
2007-05-01 1:42 ` H. Peter Anvin
2007-05-02 7:46 ` Martin Mares
2007-05-02 9:22 ` Andi Kleen
2007-05-02 20:49 ` H. Peter Anvin
2007-05-03 2:15 ` H. Peter Anvin
2007-05-02 19:05 ` Lennart Sorensen
2007-05-01 1:51 ` Dave Jones
2007-05-01 2:17 ` H. Peter Anvin
2007-05-01 2:34 ` Eric W. Biederman
2007-05-01 3:46 ` Andi Kleen
2007-05-01 2:54 ` H. Peter Anvin
2007-05-01 4:29 ` Andi Kleen
2007-05-01 3:38 ` H. Peter Anvin
2007-05-01 3:06 ` Eric W. Biederman
2007-05-01 3:21 ` H. Peter Anvin
2007-05-01 3:41 ` Eric W. Biederman [this message]
2007-05-01 3:44 ` H. Peter Anvin
2007-05-01 2:43 ` Linus Torvalds
2007-05-01 2:59 ` Dave Jones
2007-05-01 20:32 ` Rene Herman
2007-05-01 21:01 ` Rene Herman
2007-05-01 21:41 ` Linus Torvalds
2007-05-01 21:52 ` H. Peter Anvin
2007-06-14 4:51 ` Oleg Verych
2007-06-14 5:11 ` H. Peter Anvin
2007-06-14 7:18 ` Oleg Verych
2007-05-01 22:59 ` Rene Herman
2007-05-01 23:18 ` Antonino A. Daplas
2007-05-02 18:22 ` Jan Engelhardt
2007-05-02 20:59 ` H. Peter Anvin
2007-05-02 21:07 ` Rene Herman
2007-05-02 21:15 ` H. Peter Anvin
2007-05-02 21:20 ` Rene Herman
2007-05-02 21:25 ` H. Peter Anvin
2007-05-02 21:39 ` Rene Herman
2007-05-02 22:11 ` H. Peter Anvin
2007-05-02 22:49 ` Rene Herman
2007-05-02 22:59 ` H. Peter Anvin
2007-05-02 23:18 ` Rene Herman
2007-05-03 2:09 ` H. Peter Anvin
2007-05-01 3:56 ` WANG Cong
2007-05-01 22:41 Vlad
2007-05-01 23:22 ` Rene Herman
2007-05-02 1:10 ` Vlad
2007-05-02 18:25 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1d51l1a8m.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome