1. 27 Nov, 2018 18 commits
    • bunnei's avatar
      Merge pull request #1815 from DarkLordZach/npad-pos-fix · 71dfe4a7
      bunnei authored
      npad: Fix copy/paste error with LED position assignments
      71dfe4a7
    • Zach Hilman's avatar
      6df74ff5
    • bunnei's avatar
      Merge pull request #1802 from DarkLordZach/user-data-storage · 3cc204af
      bunnei authored
      profile_manager: Save and load ProfileData from disk
      3cc204af
    • bunnei's avatar
      Merge pull request #1812 from lioncash/nacp · bf055e14
      bunnei authored
      control_metadata: Correct typo in language name (Portugese -> Portuguese)
      bf055e14
    • bunnei's avatar
      Merge pull request #1813 from ReinUsesLisp/fixup-clip · 06614085
      bunnei authored
      gl_shader_decompiler: Fixup clip distance index
      06614085
    • ReinUsesLisp's avatar
      2e9b90ab
    • Lioncash's avatar
      control_metadata: Correct typo in language name (Portugese -> Portuguese) · d4e3d567
      Lioncash authored
      While we're at it, organize the array linearly, since clang formats the
      array elements quite wide length-wise with the addition of the missing
      'u'.
      
      Technically also fixes patch lookup and icon lookup with Portuguese,
      though I doubt anyone has actually run into this issue.
      d4e3d567
    • bunnei's avatar
      Merge pull request #1810 from degasus/dirty_flags · 5bea164a
      bunnei authored
      gl_rasterizer: Fixup for #1723.
      5bea164a
    • Markus Wick's avatar
      gl_rasterizer: Fixup for #1723. · 8747f5fc
      Markus Wick authored
      On invalidating the streaming buffer, we need to reupload all vertex buffers.
      But we don't need to reconfigure the vertex format.
      This was a (silly) misstake in #1723.
      
      Thanks at Rodrigo for discovering the issue.
      
      Fun fact, as configuring the vertex format also invalidate the vertex buffer,
      this misstake had no affect on the behavior.
      8747f5fc
    • bunnei's avatar
      Merge pull request #1806 from ReinUsesLisp/morton-fixup · 1cd40f10
      bunnei authored
      morton: Fixup compiler warning
      1cd40f10
    • bunnei's avatar
      Merge pull request #1804 from lioncash/cast · 11c17465
      bunnei authored
      gdbstub: Silence value truncation warning within FpuWrite()
      11c17465
    • bunnei's avatar
      Merge pull request #1805 from lioncash/resource · 852a462d
      bunnei authored
      svc: Implement svcCreateResourceLimit, svcGetResourceLimitCurrentValue(), svcGetResourceLimitLimitValue(), and svcSetResourceLimitLimitValue()
      852a462d
    • Lioncash's avatar
      svc: Implement svcSetResourceLimitLimitValue() · 5905162e
      Lioncash authored
      The opposite of the getter functions, this function sets the limit value
      for a particular ResourceLimit resource category, with the restriction
      that the  new limit value must be equal to or greater than the current
      resource value. If this is violated, then ERR_INVALID_STATE is returned.
      
      e.g.
      
      Assume:
      
      current[Events] = 10;
      limit[Events] = 20;
      
      a call to this service function lowering the limit value to 10 would be
      fine, however, attempting to lower it to 9 in this case would cause an
      invalid state error.
      5905162e
    • Lioncash's avatar
      svc: Implement svcGetResourceLimitCurrentValue() · eb559604
      Lioncash authored
      This kernel service function is essentially the exact same as
      svcGetResourceLimitLimitValue(), with the only difference being that it
      retrieves the current value for a given resource category using the
      provided resource limit handle, rather than retrieving the limiting
      value of that resource limit instance.
      
      Given these are exactly the same and only differ on returned values, we
      can extract the existing code for svcGetResourceLimitLimitValue() to
      handle both values.
      eb559604
    • ReinUsesLisp's avatar
      morton: Fixup compiler warning · 237c2026
      ReinUsesLisp authored
      237c2026
    • Lioncash's avatar
      svc: Implement svcGetResourceLimitLimitValue() · 1d6399c2
      Lioncash authored
      This kernel service function retrieves the maximum allowable value for
      a provided resource category for a given resource limit instance. Given
      we already have the functionality added to the resource limit instance
      itself, it's sufficient to just hook it up.
      
      The error scenarios for this are:
      
      1. If an invalid resource category type is provided, then ERR_INVALID_ENUM is returned.
      
      2. If an invalid handle is provided, then ERR_INVALID_HANDLE is returned (bad thing goes in, bad thing goes out, as one would expect).
      
      If neither of the above error cases occur, then the out parameter is
      provided with the maximum limit value for the given category and success
      is returned.
      1d6399c2
    • Lioncash's avatar
      svc: Implement svcCreateResourceLimit() · 4ef2af8c
      Lioncash authored
      This function simply creates a ResourceLimit instance and attempts to
      create a handle for it within the current process' handle table. If the
      kernal fails to either create the ResourceLimit instance or create a
      handle for the ResourceLimit instance, it returns a failure code
      (OUT_OF_RESOURCE, and HANDLE_TABLE_FULL respectively). Finally, it exits
      by providing the output parameter with the handle value for the
      ResourceLimit instance and returning that it was successful.
      
      Note: We do not return OUT_OF_RESOURCE because, if yuzu runs out of
      available memory, then new will currently throw. We *could* allocate the
      kernel instance with std::nothrow, however this would be inconsistent
      with how all other kernel objects are currently allocated.
      4ef2af8c
    • Lioncash's avatar
      gdbstub: Silence value truncation warning within FpuWrite() · 474c7455
      Lioncash authored
      Previously this would cause an implicit truncation warning about
      assigning a u64 value to a u32 value without an explicit cast.
      474c7455
  2. 26 Nov, 2018 12 commits
  3. 25 Nov, 2018 8 commits
  4. 24 Nov, 2018 2 commits