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- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/