[ros-dev] GSoC :: application rejected
Dear all, The ReactOS Foundation application to GSoC has been rejected this year again. Statistics are not reliable after all. In any case, keep up the good work. We don't need Google to be the bests at what we do. Cheers, -- Pierre Schweitzer pierre at reactos.org System Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. smime.p7s Description: S/MIME Cryptographic Signature ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] [ros-diffs] [akhaldi] 66551: [PSDK] Fix winternl.h version of SECTION_IMAGE_INFORMATION and add missing MEM_EXECUTE_OPTION_DISABLE_THUNK_EMULATION definition.
This is wintrnl.h which should match the Windows one. Make sure you're not
accidentally adding fields that only NDK should have.
Best regards,
Alex Ionescu
On Mon, Mar 2, 2015 at 3:38 PM, akha...@svn.reactos.org wrote:
Author: akhaldi
Date: Mon Mar 2 23:38:49 2015
New Revision: 66551
URL: http://svn.reactos.org/svn/reactos?rev=66551view=rev
Log:
[PSDK] Fix winternl.h version of SECTION_IMAGE_INFORMATION and add missing
MEM_EXECUTE_OPTION_DISABLE_THUNK_EMULATION definition.
Modified:
trunk/reactos/include/psdk/winternl.h
Modified: trunk/reactos/include/psdk/winternl.h
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/include/psdk/winternl.h?rev=66551r1=66550r2=66551view=diff
==
--- trunk/reactos/include/psdk/winternl.h [iso-8859-1] (original)
+++ trunk/reactos/include/psdk/winternl.h [iso-8859-1] Mon Mar 2
23:38:49 2015
@@ -705,6 +705,7 @@
#define MEM_EXECUTE_OPTION_DISABLE 0x01
#define MEM_EXECUTE_OPTION_ENABLE0x02
+#define MEM_EXECUTE_OPTION_DISABLE_THUNK_EMULATION 0x04
#define MEM_EXECUTE_OPTION_PERMANENT 0x08
typedef enum _SECTION_INHERIT {
@@ -1685,23 +1686,28 @@
} SECTION_INFORMATION_CLASS;
typedef struct _SECTION_BASIC_INFORMATION {
- ULONG BaseAddress;
+ PVOID BaseAddress;
ULONG Attributes;
LARGE_INTEGER Size;
} SECTION_BASIC_INFORMATION, *PSECTION_BASIC_INFORMATION;
typedef struct _SECTION_IMAGE_INFORMATION {
- PVOID EntryPoint;
- ULONG StackZeroBits;
- ULONG StackReserved;
- ULONG StackCommit;
- ULONG ImageSubsystem;
+ PVOID TransferAddress;
+ ULONG ZeroBits;
+ SIZE_T MaximumStackSize;
+ SIZE_T CommittedStackSize;
+ ULONG SubSystemType;
WORD SubsystemVersionLow;
WORD SubsystemVersionHigh;
- ULONG Unknown1;
+ ULONG GpValue;
ULONG ImageCharacteristics;
- ULONG ImageMachineType;
- ULONG Unknown2[3];
+ USHORT DllCharacteristics;
+ USHORT Machine;
+ BOOLEAN ImageContainsCode;
+ UCHAR ImageFlags;
+ ULONG LoaderFlags;
+ ULONG ImageFileSize;
+ ULONG CheckSum;
} SECTION_IMAGE_INFORMATION, *PSECTION_IMAGE_INFORMATION;
typedef struct _LPC_SECTION_WRITE {
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] [ros-diffs] [cgutman] 66511: [PCI] - Handle 64-bit PCI base address registers (BARs) - Fix maximum address in resource requirements for 20-bit resources - Fix flags on memory and I/O por
Just make pcix work already
Best regards,
Alex Ionescu
On Sat, Feb 28, 2015 at 11:52 PM, cgut...@svn.reactos.org wrote:
Author: cgutman
Date: Sun Mar 1 07:52:32 2015
New Revision: 66511
URL: http://svn.reactos.org/svn/reactos?rev=66511view=rev
Log:
[PCI]
- Handle 64-bit PCI base address registers (BARs)
- Fix maximum address in resource requirements for 20-bit resources
- Fix flags on memory and I/O port resources
[NTOS]
- Fix handling of 64-bit resources
Modified:
trunk/reactos/drivers/bus/pci/pdo.c
trunk/reactos/ntoskrnl/io/pnpmgr/pnpres.c
Modified: trunk/reactos/drivers/bus/pci/pdo.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/bus/pci/pdo.c?rev=66511r1=66510r2=66511view=diff
==
--- trunk/reactos/drivers/bus/pci/pdo.c [iso-8859-1] (original)
+++ trunk/reactos/drivers/bus/pci/pdo.c [iso-8859-1] Sun Mar 1 07:52:32
2015
@@ -21,6 +21,9 @@
#define DBGPRINT(...)
#endif
+#define PCI_ADDRESS_MEMORY_ADDRESS_MASK_64 0xfff0ull
+#define PCI_ADDRESS_IO_ADDRESS_MASK_64 0xfffcull
+
/*** PRIVATE
*/
static NTSTATUS
@@ -191,80 +194,159 @@
return STATUS_SUCCESS;
}
+static BOOLEAN
+PdoReadPciBar(PPDO_DEVICE_EXTENSION DeviceExtension,
+ ULONG Offset,
+ PULONG OriginalValue,
+ PULONG NewValue)
+{
+ULONG Size;
+ULONG AllOnes;
+
+/* Read the original value */
+Size = HalGetBusDataByOffset(PCIConfiguration,
+ DeviceExtension-PciDevice-BusNumber,
+
DeviceExtension-PciDevice-SlotNumber.u.AsULONG,
+ OriginalValue,
+ Offset,
+ sizeof(ULONG));
+if (Size != sizeof(ULONG))
+{
+DPRINT1(Wrong size %lu\n, Size);
+return FALSE;
+}
+
+/* Write all ones to determine which bits are held to zero */
+AllOnes = MAXULONG;
+Size = HalSetBusDataByOffset(PCIConfiguration,
+ DeviceExtension-PciDevice-BusNumber,
+
DeviceExtension-PciDevice-SlotNumber.u.AsULONG,
+ AllOnes,
+ Offset,
+ sizeof(ULONG));
+if (Size != sizeof(ULONG))
+{
+DPRINT1(Wrong size %lu\n, Size);
+return FALSE;
+}
+
+/* Get the range length */
+Size = HalGetBusDataByOffset(PCIConfiguration,
+ DeviceExtension-PciDevice-BusNumber,
+
DeviceExtension-PciDevice-SlotNumber.u.AsULONG,
+ NewValue,
+ Offset,
+ sizeof(ULONG));
+if (Size != sizeof(ULONG))
+{
+DPRINT1(Wrong size %lu\n, Size);
+return FALSE;
+}
+
+/* Restore original value */
+Size = HalSetBusDataByOffset(PCIConfiguration,
+ DeviceExtension-PciDevice-BusNumber,
+
DeviceExtension-PciDevice-SlotNumber.u.AsULONG,
+ OriginalValue,
+ Offset,
+ sizeof(ULONG));
+if (Size != sizeof(ULONG))
+{
+DPRINT1(Wrong size %lu\n, Size);
+return FALSE;
+}
+
+return TRUE;
+}
static BOOLEAN
PdoGetRangeLength(PPDO_DEVICE_EXTENSION DeviceExtension,
- ULONG Offset,
- PULONG Base,
- PULONG Length,
- PULONG Flags)
-{
-ULONG OrigValue;
-ULONG BaseValue;
-ULONG NewValue;
-ULONG Size;
-ULONG XLength;
-
-/* Save original value */
-Size= HalGetBusDataByOffset(PCIConfiguration,
-DeviceExtension-PciDevice-BusNumber,
-
DeviceExtension-PciDevice-SlotNumber.u.AsULONG,
-OrigValue,
-Offset,
-sizeof(ULONG));
-if (Size != sizeof(ULONG))
-{
-DPRINT1(Wrong size %lu\n, Size);
+ UCHAR Bar,
+ PULONGLONG Base,
+ PULONGLONG Length,
+ PULONG Flags,
+ PUCHAR NextBar,
+ PULONGLONG MaximumAddress)
+{
+union {
+struct {
+ULONG Bar0;
+ULONG Bar1;
+} Bars;
+ULONGLONG Bar;
+} OriginalValue;
+union {
+struct {
+ULONG Bar0;
+ULONG Bar1;
+} Bars;
+ULONGLONG Bar;
+} NewValue;
+ULONG Offset;
+
+/* Compute the offset of this BAR in PCI config space */
+Offset = 0x10 + Bar * 4;
+
+/* Assume this is a 32-bit BAR until we find wrong */
+*NextBar = Bar +
Re: [ros-dev] Windows Server 2003 Testbot is live!
Sure Thomas, but I was asking myself that because, for example kernel32:console, seems to fail 4 tests (iirc) but if I run them manually on windows 2k3 they don't fail (at least, they didn't 1 month ago). And they succeed on ReactOS. H. -Message d'origine- De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Thomas Faber Envoyé : lundi 2 mars 2015 04:47 À : ReactOS Development List Objet : Re: [ros-dev] Windows Server 2003 Testbot is live! Broken tests is what they are. For the most part, anyway. On 2015-03-02 02:37, Hermès BÉLUSCA - MAÏTO wrote: Hi! That's very nice! I'm however wondering what all those failed (or crashed) tests are... Hermès. -Message d'origine- De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de Colin Finck Envoyé : dimanche 1 mars 2015 11:46 À : 'ReactOS Development List' Objet : [ros-dev] Windows Server 2003 Testbot is live! Hi all, After a long, long time, we finally have a Testbot regularly running our Wine tests and API tests under our target platform Windows Server 2003. The VM is actually based on Windows Home Server, which is a cheap Windows Server 2003 SP2 edition. The first successful test results are here: https://reactos.org/sites/all/modules/reactos/testman/compare.php?ids= 34839 Okay, I have to admit this already required manual intervention. Test msi:install reproducibly hangs with the error message The process cannot access the file because another process has locked a portion of the file. I expect all of this to still need some tweaking here and there. Please reply to this mail with all your tweaking suggestions and I see what I can do. Have fun, Colin ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
