Opened 7 years ago
Closed 3 years ago
#25 closed task (worksforme)
Clean up x86 emulator in the tree?
| Reported by: | uwe | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | coreboot | Keywords: | |
| Cc: | eich@… | Dependencies: | |
| Patch Status: | there is no patch |
Description
From http://www.linuxbios.org/pipermail/linuxbios/2006-November/016626.html:
which of the following x86 emulators in the tree works better and are there any plans to eliminate one of them? LinuxBIOSv2/src/devices/emulator/x86emu/ LinuxBIOSv2/util/vgabios/x86emu/src/x86emu/ Has anyone recently worked to merge this with current x.org and scitech code?
From http://www.linuxbios.org/pipermail/linuxbios/2006-November/016627.html:
> LinuxBIOSv2/src/devices/emulator/x86emu/ part of linuxbios > LinuxBIOSv2/util/vgabios/x86emu/src/x86emu/ standalone, for testing. They had to fork, since one can use glibc, the other can not. > Has anyone recently worked to merge this with current x.org > and scitech code? it's been on the list for years. The last time we tried it, with some "optimized" code from other places, it totally broke. So we need to be careful.
Attachments (0)
Change History (3)
comment:1 Changed 7 years ago by stepan
- version changed from v2 to v3
comment:2 Changed 7 years ago by stepan
- Cc eich@… added
- Summary changed from Remove one x86 emulator from the tree? to Clean up x86 emulator in the tree?
- Type changed from defect to task
I am adding Egbert Eich from the X.org team to this issue. Maybe we find some time at some point to do such a merge / unification together.
comment:3 Changed 3 years ago by stepan
- Patch Status set to there is no patch
- Resolution set to worksforme
- Status changed from new to closed
In the last 3 years a lot of things have happened in this area. We have a lot of fixes in our x86 emulator that may or may not be upstream. The versions we are using now will stay in place as they are (except biosemu.c and yabel may be merged some time, but that's a different ticket)
Note: See
TracTickets for help on using
tickets.

I suggest we leave the userspace version out of v3, but dont touch it in v2.
This way we can always easily find it but it does not become a burden