From: ASA <llb@udm.net.ru>
To: linux-kernel@vger.kernel.org
Subject: Too big EBDA issue
Date: Fri, 25 Jan 2002 20:58:22 +0400 [thread overview]
Message-ID: <1038781885.20020125205822@udm.net.ru> (raw)
Hello all,
My system is embedded PC/104 and has C&T 65545 videochip and DiskOnChip
flash device. I'm developing a special linux-based application.
Today I had to upgrade DiskOnChip BIOS extender and after that I could not
boot linux anymore. After digging hard in problem I found that EBDA was
enlarged to 33KB so remaining conventional memory was reduced to 607KB but
normal booting proccess bzImage loading requires at least 608 KB. After
checking on other systems with DiskOnChip I found their EBDA have sizes
typically of 29-31 KB.
Yeah, it is very large EBDA (normal PC's I checked just have only 1 KB
EBDA). It seems DickOnChip BIOS requires much space on irder to store own
temporary data to implement their TrueFFS.
But I guess that there will be some other BIOS extensions that will require
another EBDA space. As far as bzImage loading model requires space of 32 K
between 576K (0x90000) and 608K (0x98000) but almost no other place I think
there is necessity to extend boot protocol in order to relocate 16-bit mode
loader closer to the lowest memory bound, not to the upper one.
I also reported that issue to DiskOnChip developers (www.m-sys.com) but
there is a possibility that other hardware developers can extend EBDA also.
So extending boot protocol in order to move far away of cancer of growing
EBDA would be worthly of note. As a new feature for 2.5/2.6 kernels by
example.
--
Best regards,
ASA mailto:llb@udm.net.ru
next reply other threads:[~2002-01-25 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 16:58 ASA [this message]
2002-01-25 17:38 ` H. Peter Anvin
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=1038781885.20020125205822@udm.net.ru \
--to=llb@udm.net.ru \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®