Index
> OS Construction > Goodbye to BIOS? [split off TetrOS thread] |
| Author |
|
|
DimonSoft 04 Nov 2019, 20:50
Mike Gonta wrote:
Didn’t they try to say “Bye to BIOS” ten years ago? And even before then? |
|||
04 Nov 2019, 20:50 |
|
|
Mike Gonta 04 Nov 2019, 21:50
DimonSoft wrote:
It's the UEFI CSM that is going to disappear next year and as such the real mode BIOS and all such things (VGA, 0xB800, the related I/O ports, etc.) including real mode will go with it. arstechnica.com wrote: Take away the BIOS and CSM requirement and it might open the door to also removing these legacy processor modes. Of course, we still have emulation. Oscar Wilde could have wrote: Emulation is the sincerest form of flattery that mediocrity can pay to greatness. It was fun* while it lasted, (some say for too long). *UEFI is simply no fun whatsoever. |
|||
|
04 Nov 2019, 21:50 |
|
|
DimonSoft 05 Nov 2019, 09:21
UEFI is simply not mature enough yet. Many implementations still have very stupid bugs compared to differences in BIOS implementations.
|
|||
|
05 Nov 2019, 09:21 |
|
|
DimonSoft 05 Nov 2019, 12:34
Mike Gonta wrote:
I wish it was about CSM. For example, Graphics Output Protocol had a few problems in relatively new notebook models (a few years ago). Another thing to discuss is whether the design choices like calling convention used in 64-bit UEFI were good ones. Reusing compiler-oriented calling convention might have seemed to be a good idea but why not reusing ART bytecode then? Gives even more bloat with less effort. Probably the only good idea is to support loading arbitrarily-sized bootloaders. Used to be the most lacking feature since at least 8086. But… oh, wait, FAT? Why prefer some particular file systems? This decision might look quite stupid 30–40 years later. Why on earth a bootloader should be a normal file? From reliability point of view. Just make it a separate volume and let the OS author decide. You have GPT? That’s OK, just give us better volume-oriented disk API than BIOS did (anything is better than nothing), that would be just enough. Why add features that are to be deprecated in the future? |
|||
|
05 Nov 2019, 12:34 |
|
|
Fulgurance 02 Apr 2020, 10:30
Hello, i have read this post, and i have question.
If next laptop have UEFI only, what is the future for system based into 16bits start mode coded into assembly ? Intel force all people to use PE to start all UEFI based system now ?  |
|||
|
02 Apr 2020, 10:30 |
|
|
revolution 02 Apr 2020, 15:16
Fulgurance wrote: Hello, i have read this post, and i have question. So choose your laptops with care if you intend to run a different OS from the one the maker puts on. |
|||
|
02 Apr 2020, 15:16 |
|
|
Fulgurance 02 Apr 2020, 15:30
... It's very horrible ... bye to custom file system... Mandatory to use minimal fat system... pff
In futur, processor start into 32 bits mode ? Bye to 16 bits mode ? But how processor start ? With mandatory GDT ??? |
|||
|
02 Apr 2020, 15:30 |
|
|
revolution 02 Apr 2020, 15:40
IIRC VIA once made a CPU that had no 16-bit mode, only 32-bit.
It could happen soon. AMD and Intel might remove support for 16-bit. So make good use of it now while you can.. And cry when it disappears. |
|||
|
02 Apr 2020, 15:40 |
|
|
Fulgurance 02 Apr 2020, 16:46
It's only me i think when this come it's the end of the true programming ? I'm afraid in future assembly dissapear...
I think it's getting out of hand And wait ??? But if 16bits dissapear, how use graphic mode into proprietary graphic card when you would like to build our driver without specification ??? |
|||
|
02 Apr 2020, 16:46 |
|
|
N-LG 02 Apr 2020, 17:27
with UEFI, there is a new protocol called GOP (graphique Output Protocol) to control the graphics card, I haven't tried it yet but it doesn't seem very complicated to use
|
|||
|
02 Apr 2020, 17:27 |
|
|
bitshifter 02 Apr 2020, 17:28
There are plenty of old morherboards to choose from, i just got nos dell gx270 cg566 for $20usd, it has 845 chipset, 4gb ram, 800mhz bus, pentium 4 cpu (testing 3.2ghz) these old mb's will be around for good long time...
_________________ Coding a 3D game engine with fasm is like trying to eat an elephant, you just have to keep focused and take it one 'byte' at a time. |
|||
|
02 Apr 2020, 17:28 |
|
|
Tomasz Grysztar 02 Apr 2020, 17:48
Even if future generations of CPUs drop legacy modes and boot directly into the long mode (which would make most sense in my opinion, modern OSes do not use legacy modes anyway, for 32 bits there is a compatibility sub-mode of the long mode) it would in no way prevent you from writing in assembly. In many ways long mode is actually more comfortable to handle than the legacy modes.
You can use fasm to develop for UEFI (or even write EBC code instead of x86). |
|||
|
02 Apr 2020, 17:48 |
|
|
Fulgurance 02 Apr 2020, 19:59
There are any documentation about this new processor ? There any virtual machine and assembly to test and code for this new motherboard ?
|
|||
|
02 Apr 2020, 19:59 |
|
|
Feryno 05 Apr 2020, 20:33
16 bit realmode is still necessary:
multiprocessor systems - every application CPU starts in 16 bit realmode, abandoning this mode would require an update of APIC and IPI wakeup from ACPI sleep - already prepared to resume CPU in protected mode but every current CPU still uses resume from S3 sleep in 16 bit realmode so I expect 16 bit realmode will be still present for at least few years |
|||
|
05 Apr 2020, 20:33 |
|
|
Fulgurance 08 Apr 2020, 10:38
It's so sad there is no way to use MBR and UEFI ...
I detest to use existing file system... |
|||
|
08 Apr 2020, 10:38 |
|
|
DimonSoft 08 Apr 2020, 12:09
Why not? There’s a place for legacy MBR in GPT. Noone prevents you from making a disk that is both MBR and GPT. Except for the lack of tools to do so and the need to keep in mind the limitation differences of both schemes. And the need to keep both MBR and GPT info about partitions consistent (or not, if you wish to have some cool configuration).
|
|||
|
08 Apr 2020, 12:09 |
|
|
Ali.Z 08 Apr 2020, 20:58
so sad to hear, maybe its better to backup our hardware.
but removing bios means removing realmode, but i dont want them to remove protected mode. seems in a way or other they will force us to write the ugly 64bit assembly, plus 64bit processor is not really 64bit its still limited and cant address the full 64bit memory. basically like a game released in early access mode. secure boot + signing that means they will force some ppl to specific OSes ... yea and maybe even buy new processor. just like the game game published by miceosoft and intel INTEL 7TH GEN IS NOT SUPPORTED ON WINDOWS 7 what a stupid deal. new era of conspiracy, f*** them i wish all of their new designs burn. _________________ Asm For Wise Humans |
|||
|
08 Apr 2020, 20:58 |
|
|
guignol 10 Apr 2020, 02:24
The mistake was introducing 3D gaming back in the 90s.
And SoC is the next near step of every personal computing. though probably a separate chip on communications |
|||
|
10 Apr 2020, 02:24 |
|
|
Fulgurance 10 Apr 2020, 11:10
Sorry guys,but i have other questions. I have looked into UEFI documentation for GOP Graphics output protocol, but how can i access to it ? It's not into EFI SYSTEM TABLE...
|
|||
|
10 Apr 2020, 11:10 |
|
< Last Thread | Next Thread > |
Forum Rules:
|