search for: parentless

...all (I/O) subchannels using e.g. the same dma size? (TBH, that question sounds a bit silly: that should be a property belonging to the ccw device, shouldn't it?) - What dma properties does the fake subchannel have? (Probably none, as its only purpose is to serve as a parent for otherwise parentless disconnected ccw devices, and is therefore not involved in any I/O.) - There needs to be some kind of handling in the machine check code, I guess? We would probably need a different allocation if we end up at a different subchannel? I think we can assume that the dma size is at most 31 bits...

...all (I/O) subchannels using e.g. the same dma size? (TBH, that question sounds a bit silly: that should be a property belonging to the ccw device, shouldn't it?) - What dma properties does the fake subchannel have? (Probably none, as its only purpose is to serve as a parent for otherwise parentless disconnected ccw devices, and is therefore not involved in any I/O.) - There needs to be some kind of handling in the machine check code, I guess? We would probably need a different allocation if we end up at a different subchannel? I think we can assume that the dma size is at most 31 bits...

...not true (due to adding DIEs to types after-the-fact, due to things like > implicit special members, member templates, and nested types). > > The assertion you would need to check that a worklist is not required > would be a mapping listing the "assumptions" (ie: we found this parentless > DIE and assumed it was in the same DIE as this other DIE we're building) > and then, whenever a DIE is added to a parent that chains up to a CU we > would have to check that mapping to see if the assumption turned out to be > true. > > I don't mind if you implement this...

...39;ve explained is not true (due to adding DIEs to types after-the-fact, due to things like implicit special members, member templates, and nested types). The assertion you would need to check that a worklist is not required would be a mapping listing the "assumptions" (ie: we found this parentless DIE and assumed it was in the same DIE as this other DIE we're building) and then, whenever a DIE is added to a parent that chains up to a CU we would have to check that mapping to see if the assumption turned out to be true. I don't mind if you implement this or not. What I do mind and w...

Hi, I made a simple patch which makes switcher's window a splash window (_NET_WM_WINDOW_TYPE_SPLASH). This way I can easily add effects for it. The window is a splash window, so why not use this type instead of Unknown? Beryl's switcher window is a Splash window too. Is there a reason why Compiz uses Uknown for it? Patch: --- switcher.c 2006-12-28 10:14:52.000000000 +0100 +++

Hi, A long time ago, I made some MFC GUI programming ... There was basically 2 kinds of application : - dialog based application : a simple app based on a dialog (without menu, toolbar, status bar ...) - frame based app (Single Document or Multiple Document) with menu, toolbar, status bar ... I tried to make a dialog based app with wxRuby but the application never exits !! The following code

On Wed, Oct 16, 2013 at 1:58 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Oct 16, 2013 at 1:21 PM, Manman Ren <manman.ren at gmail.com> wrote: > >> >> There are a few places where we break the assumption: >> 1> formal_parameter constructed in DwarfDebug when adding attribute type >> we call SPCU->addType(Arg, ATy),

...ls using e.g. the same dma size? (TBH, that > question sounds a bit silly: that should be a property belonging to > the ccw device, shouldn't it?) > - What dma properties does the fake subchannel have? (Probably none, as > its only purpose is to serve as a parent for otherwise parentless > disconnected ccw devices, and is therefore not involved in any I/O.) > - There needs to be some kind of handling in the machine check code, I > guess? We would probably need a different allocation if we end up at > a different subchannel? > Basically nothing changes with me...

...le ASPM for PCIe devices. wcte12xp, wctdm24xxp: Add compile-time option to disable ASPM for PCIe devices. dahdi: Update dev_set_name / dev_name for RHEL 5.6+. dahdi_dynamic_eth: Move tx packet flushing to process context. dahdi_dynamic: Since dynamic devices are 'parentless' we must name them. dahdi_dynamic_eth: Prevent crash is packet arrives before span is fully configured. dahdi_dynamic_eth: Fix compilation on kernels < 2.6.22. wct4xxp: Disable all interrupts explicitly in interrupt handler. wct4xxp: Trivial formatting changes...

...le ASPM for PCIe devices. wcte12xp, wctdm24xxp: Add compile-time option to disable ASPM for PCIe devices. dahdi: Update dev_set_name / dev_name for RHEL 5.6+. dahdi_dynamic_eth: Move tx packet flushing to process context. dahdi_dynamic: Since dynamic devices are 'parentless' we must name them. dahdi_dynamic_eth: Prevent crash is packet arrives before span is fully configured. dahdi_dynamic_eth: Fix compilation on kernels < 2.6.22. wct4xxp: Disable all interrupts explicitly in interrupt handler. wct4xxp: Trivial formatting changes...

...lated project that will take advantage of it. I've updated the core and most plugins so they work correctly with multiple displays. However, our configuration plugins needs some more work. - Core object There's now a "core" object. This is the only object that is allowed to be parentless, every other object needs a parent. A lot of hooks that currently exist in the display object should be moved into core object. All general object hooks should be in the core object. TODO - Matching interface The matching interface should be updated to work with all kinds of objects and not on...

...errors. msi: Check transform validation flags. Henri Verbeet (12): wined3d: Allow sRGB read/write and VTF on WINED3DFMT_R8G8B8A8_UNORM. d3d10core: Set wined3d state in d3d10_device_RSSetState(). d3d10core/tests: Add a basic scissoring test. d3d10core: Properly handle parentless views in d3d10_device_OMGetRenderTargets(). d3d10: Implement d3d10_stateblock_Capture(). d3d10: Implement d3d10_stateblock_Apply(). d3d10_1: Forward stateblock functions to d3d10. d2d1: Get rid of a FIXME in d2d_d3d_render_target_BeginDraw(). d2d1: Implement d2d_d3d_re...

On Wed, 15 May 2019 22:51:58 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Mon, 13 May 2019 11:41:36 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 26 Apr 2019 20:32:41 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > As virtio-ccw devices are channel devices, we need to use the dma area > >

On Wed, 15 May 2019 22:51:58 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Mon, 13 May 2019 11:41:36 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 26 Apr 2019 20:32:41 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > As virtio-ccw devices are channel devices, we need to use the dma area > >