search for: 04.07.19

On 04.07.19 15:54, Rowland penny via samba wrote:>> Still left are the three governsId collisions, which are now identical >> across all DCs: >> >>> Checking 3861 objects >>> Error: governsID >>> CN=ucsUser,CN=Schema,CN=Configuration,DC=ad,DC=tao,DC=at on >>> 1.3.6.1.4.1.19414.3.2.2 already exists as an attributeId or governsId >>>

Hi Am 04.07.19 um 12:18 schrieb Noralf Tr?nnes: > > > Den 04.07.2019 09.43, skrev Thomas Zimmermann: >> Hi >> >> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: >>> >>> >>> Den 03.07.2019 10.32, skrev Thomas Zimmermann: >>>> DRM client buffers are permanently mapped throughout their lifetime. This >>>> prevents us from

Hi Am 04.07.19 um 12:18 schrieb Noralf Tr?nnes: > > > Den 04.07.2019 09.43, skrev Thomas Zimmermann: >> Hi >> >> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: >>> >>> >>> Den 03.07.2019 10.32, skrev Thomas Zimmermann: >>>> DRM client buffers are permanently mapped throughout their lifetime. This >>>> prevents us from

Den 04.07.2019 13.10, skrev Thomas Zimmermann: > Hi > > Am 04.07.19 um 12:18 schrieb Noralf Tr?nnes: >> >> >> Den 04.07.2019 09.43, skrev Thomas Zimmermann: >>> Hi >>> >>> Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: >>>> >>>> >>>> Den 03.07.2019 10.32, skrev Thomas Zimmermann: >>>>> DRM

On 03.07.19 18:04, Rowland penny via samba wrote: >>>> How do I get rid of these bogus Schema entries, and how do I fix the >>>> user account? >>> I do not think you can remove anything from the schema, but I believe >>> you can deactivate schema objects, try reading this: >>> >>>

Hi Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: > > > Den 03.07.2019 10.32, skrev Thomas Zimmermann: >> DRM client buffers are permanently mapped throughout their lifetime. This >> prevents us from using generic framebuffer emulation for devices with >> small dedicated video memory, such as ast or mgag200. With fb buffers >> permanently mapped, such devices

Hi Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: > > > Den 03.07.2019 10.32, skrev Thomas Zimmermann: >> DRM client buffers are permanently mapped throughout their lifetime. This >> prevents us from using generic framebuffer emulation for devices with >> small dedicated video memory, such as ast or mgag200. With fb buffers >> permanently mapped, such devices

Hi Craig, On 03.07.19 17:33, Craig Topper wrote: > Don't the CreateICmp calls return a Value* with an i1 type? But then > they are added to an i8 type? Not sure that works.  I had that initially: auto cf = IRB.CreateICmpULT(Incr, ConstantInt::get(Int8Ty, 1)); auto carry = IRB.CreateZExt(cf, Int8Ty); Incr = IRB.CreateAdd(Incr, carry); it makes no difference to the generated assembly