Before this commit UMKa was downloaded, but none of its tests had been executed. Now it executes all the tagged UMKa tests (41 for now). Some tags had been excluded, like #acpi, because the ACPI subsystem is still under development.
git-svn-id: svn://kolibrios.org@9931 a494cfbc-eb01-0410-851d-a64ba20cac60
-extended WDATA structures up to 128 bytes
-added the background_windows constant
-the draw_data array has been deleted
-APPDATA.window and WDATA.thread fields added
-minor fixes in the operation of external file system drivers
git-svn-id: svn://kolibrios.org@9930 a494cfbc-eb01-0410-851d-a64ba20cac60
These are changes from two commits from the upstream clink repo (https://github.com/mkostoevr/clink) and one commit from the upstream epep repo (https://github.com/mkostoevr/epep).
clink:
Commit e63ed12ead17e47d77e848da0e7b9f4dd3ad5127
Bugfix: Make it able to write more than 64k - 1 COFF relocations
If the relocation count is greater than 0xffff then it can't fit
in the NumberOfRelocations field of a section header. In order to
specify greater relocation count IMAGE_SCN_LNK_NRELOC_OVFL flag
should be added to Characteristics and the actual relocation count
should be written into VirtualAddress field of the first COFF
relocation.
Commit 328fc3112a30fcaa808f2cad34028a6507d602a3
Bugfix: Make it able to read more than 64k - 1 COFF relocations
New EPEP API allows to read more than 64k - 1 relocations. Use it
when reading relocation count for filling SectionInfo and when
reading relocations for wriring the output file.
epep:
Commit 3bed4e348a486c346d0a452c58c1d85e1805c09d
Feature: Higher-level COFF relocations API
Number of COFF relocations of a section is stored in the 16-bit
NumberOfRelocations field of a section header. If a COFF object has
more than 2^16 - 1 relocations, then the value does not fit in the
field.
To solve this problem, IMAGE_SCN_LNK_NRELOC_OVFL flag of a section
header has been introduced. If this flag is set for the section,
then the actual number of relocations is stored in the
VirtualAddress field of the first relocation.
If the flag is set, then NumberOfRelocations field of the section
header should be equal to 0xffff, othervice the linker should give
an error.
So this patch introduces few functions adressing this mechanism.
epep_section_contains_extended_relocations:
Checks whether the section has more than 2^16 - 1 relocations.
Retrns error if the IMAGE_SCN_LNK_NRELOC_OVFL flag is set, but
the NumberOfRelocations field is not equal to 0xffff.
epep_get_section_extended_number_of_relocations:
Reads the number of COFF relocations from the VirtualAddress
field of the first COFF relocation.
epep_get_section_number_of_relocations_x:
Gives the number of meaningful relocations of the section.
If the section has less than 2^16 relocations, then returns the
value of the NumberOfRelocations field of the section header,
othervice reads the number of relocations from the first COFF
relocation, but: since the first relocation in this case is not
meaningful, gives the actual number of relocations minus one.
This is used in the function documented below.
Returns 1 in the last argument if the section contains extended
number of relocations, 0 othervice.
epep_get_section_relocation_by_index_x:
If the section has less than 2^16 relocations, then just reads
a relocation by the given index. In case if the section has
extended number of relocations, the first relocation is not
meaningful, so it is skipped, and the relocation at index + 1
is read instead.
git-svn-id: svn://kolibrios.org@9927 a494cfbc-eb01-0410-851d-a64ba20cac60
The test system used a custom command to build the testing kernel.
Make it use the tup system.
git-svn-id: svn://kolibrios.org@9918 a494cfbc-eb01-0410-851d-a64ba20cac60
Syscall 63.2, reading from the board buffer, was overwriting registers
edx and ebp when the buffer was empty. Now it sets eax and ebx according
to the kernel API.
Because of this ancient bug BOARD checks the status of sf63.2 syscall
this way:
mcall 63, 2
cmp ebx, 1
jne no_data
; when the buffer is empty, ebx is untouched, i.e. still 2, haha
; edx and ebp are destroyed, the code is lucky not to use them
By the way, the bug was found using umka tool.
git-svn-id: svn://kolibrios.org@9897 a494cfbc-eb01-0410-851d-a64ba20cac60
TODO: added functions for lock\unlock partition and read\write sectors for user programs
git-svn-id: svn://kolibrios.org@9894 a494cfbc-eb01-0410-851d-a64ba20cac60
This feature is _not_ enabled by default by mkfs.xfs at the moment.
That said, make KolibriOS ready for the future. By the way, fix two
bugs in support of XFSv5 disk format.
git-svn-id: svn://kolibrios.org@9889 a494cfbc-eb01-0410-851d-a64ba20cac60
Current version of mkfs.xfs enables this feature by default.
Now KolibriOS can read such partitions too.
git-svn-id: svn://kolibrios.org@9888 a494cfbc-eb01-0410-851d-a64ba20cac60
