search for: stm

The callback struct drm_driver.get_scanout_position() is deprecated in favor of struct drm_crtc_helper_funcs.get_scanout_position(). Convert stm over. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/stm/drv.c | 1 - drivers/gpu/drm/stm/ltdc.c | 65 ++++++++++++++++++++------------------ drivers/gpu/drm/stm/ltdc.h | 5 --- 3 files changed, 34 insertions(+), 37 deletions(-) diff --git a/drivers/gpu/dr...

The callback struct drm_driver.get_scanout_position() is deprecated in favor of struct drm_crtc_helper_funcs.get_scanout_position(). Convert stm over. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> Tested-by: Yannick Fertr? <yannick.fertre at st.com> --- drivers/gpu/drm/stm/drv.c | 1 - drivers/gpu/drm/stm/ltdc.c | 65 ++++++++++++++++++++------------------ drivers/gpu/drm/stm/ltdc.h | 5 --- 3 files changed, 34...

VBLANK callbacks in struct drm_driver are deprecated in favor of their equivalents in struct drm_crtc_funcs. Convert stm over. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/stm/drv.c | 1 - drivers/gpu/drm/stm/ltdc.c | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/stm/drv.c b/drivers/gpu/drm/stm/drv.c index 486985604109..ea9fcbdc68b3 100644...

VBLANK callbacks in struct drm_driver are deprecated in favor of their equivalents in struct drm_crtc_funcs. Convert stm over. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/stm/drv.c | 1 - drivers/gpu/drm/stm/ltdc.c | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/stm/drv.c b/drivers/gpu/drm/stm/drv.c index 486985604109..ea9fcbdc68b3 100644...

VBLANK callbacks in struct drm_driver are deprecated in favor of their equivalents in struct drm_crtc_funcs. Convert stm over. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> Tested-by: Yannick Fertr? <yannick.fertre at st.com> --- drivers/gpu/drm/stm/drv.c | 1 - drivers/gpu/drm/stm/ltdc.c | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/stm/drv.c b/drivers...

The redundant fb helper .load_lut is no longer used, and can not work right without also providing the fb helpers .gamma_set and .gamma_get thus rendering the code in this driver suspect. Just remove the dead code. Signed-off-by: Peter Rosin <peda at axentia.se> --- drivers/gpu/drm/stm/ltdc.c | 12 ------------ drivers/gpu/drm/stm/ltdc.h | 1 - 2 files changed, 13 deletions(-) diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.c index 1b9483d..87829b9 100644 --- a/drivers/gpu/drm/stm/ltdc.c +++ b/drivers/gpu/drm/stm/ltdc.c @@ -375,17 +375,6 @@ static irqreturn_t...

On 06/22/2017 08:06 AM, Peter Rosin wrote: > The redundant fb helper .load_lut is no longer used, and can not > work right without also providing the fb helpers .gamma_set and > .gamma_get thus rendering the code in this driver suspect. > Hi Peter, STM32 chipsets supports 8-bit CLUT mode but this driver version does not support it "yet" (final patch has not been upstreamed because it was a too big fbdev patch for simply adding CLUT...). Regarding your patch below, if it helps you to ease the drm framework update then I am agree to &...

...; On 06/22/2017 08:06 AM, Peter Rosin wrote: > > The redundant fb helper .load_lut is no longer used, and can not > > work right without also providing the fb helpers .gamma_set and > > .gamma_get thus rendering the code in this driver suspect. > > > > Hi Peter, > STM32 chipsets supports 8-bit CLUT mode but this driver version does not > support it "yet" (final patch has not been upstreamed because it was a > too big fbdev patch for simply adding CLUT...). > > Regarding your patch below, if it helps you to ease the drm framework > up...

...;${PREFIX}-gcc" export CXX="${PREFIX}-g++" export LD="${PREFIX}-ld" export NM="${PREFIX}-nm -B" export AR="${PREFIX}-ar" export RANLIB="${PREFIX}-ranlib" export LN_S="ln -s" export CFLAGS="-g -O2" export PKG_CONFIG_PATH=/opt/STM/STLinux-2.3/devkit/sh4/target/usr/lib/pkgconfig export LD_LIBRARY_PATH=/opt/STM/STLinux-2.3/devkit/sh4/lib export LDFLAGS="-L/opt/STM/STLinux-2.3/devkit/sh4/lib -L/opt/STM/STLinux-2.3/devkit/sh4/lib/gcc/sh4-linux/4.2.4" export CPPFLAGS="-I/opt/STM/STLinux-2.3/devkit/sh4/include -I/op...

...elsewhere as well (x86?). Perhaps what we need is a > switch to disable memset/memcpy lowering? > Do you offer to call libc memset/memcpy functions always instead of intrinsic lowering? It seems not a good idea, because often (especially in cases of small chunks of memory) consecutive ldm/stm instructions are more efficient than memcpy call. >> further combines them into ldm/stm with special pass after register >> allocation. But ldm/stm commands require registers to go in ascending order, >> what is often not so after regalloc, therefore some str/ldr commands. For &...

Hi, llvm emits code for "memcpy" on ARM as consecutive ldr/str commands, and further combines them into ldm/stm with special pass after register allocation. But ldm/stm commands require registers to go in ascending order, what is often not so after regalloc, therefore some str/ldr commands. For example such code: struct Foo {int a, b, c, d; } void CopyStruct(struct Foo *a, struct Foo *b) { *a = *b; } co...

.... Perhaps what we need is a >> switch to disable memset/memcpy lowering? >> > > Do you offer to call libc memset/memcpy functions always instead of > intrinsic lowering? It seems not a good idea, because often (especially > in cases of small chunks of memory) consecutive ldm/stm instructions are > more efficient than memcpy call. > >>> further combines them into ldm/stm with special pass after register >>> allocation. But ldm/stm commands require registers to go in ascending order, >>> what is often not so after regalloc, therefore some str...

...PHC PHC PHC PHC PHC PHC PHC PHC PHC PHC [325] PHC PHC PHC POS POS POS POS POS POS POS POS POS POS POS PTO PTO PTO PTO [343] PTO PTO PTO PTO PTO PTO PTO PTO PTO PTO PTO RBM RBM RBM RBM RBM RBM RBM [361] RBM RBM RBM RBM RBM RBM RBM RBM SKJ SKJ SKJ SKJ SKJ SKJ SKJ SKJ SKJ SKJ [379] SKJ SKJ SKJ SKJ SKJ STM STM STM STM STM STM STM STM STN STN STN STN STN [397] STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN [415] SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO SWO TOR TOR [433] TOR TOR TOR TOR TOR TOR YFN YFN YFN YFN YFN YFN YFN YFN YFN YFN YFN YFN [451] YFN YFN YFN...

...quot;Generics support for N3" by Tilmann Schelle [clang] "Adding support for C++ classes in clang" by Argiris Kirtzidis [codegen] "PSP (Playstation Portable) support into LLVM Mips backend" by Bruno Cardoso Lopes [llvmir] "Software Transactional Memory (STM) support in LLVM" by Luis Felipe Strano [clang] "llvm/clang distcc" by Peter Neumark [tester] "Improve the llvm nightly tester" by Rajika Kumarasiri Some more details are here: http://code.google.com/soc/2008/llvm/about.html Congratulations to the students, and...

On Tuesday 22 April 2008, Chris Lattner wrote: > [llvmir] "Software Transactional Memory (STM) support in LLVM" by > Luis Felipe Strano Hi, I'd like to know more about the directions for the STM project. Somewhat contrary to what the project's abstract states, there are open C/C++ based implementations for compiler support for memory transactions. Besides some efforts t...

...n <vasiliy.korchagin at gmail.com> wrote: > Hi, > > llvm emits code for "memcpy" on ARM as consecutive ldr/str commands, and Hmm, this happens elsewhere as well (x86?). Perhaps what we need is a switch to disable memset/memcpy lowering? > further combines them into ldm/stm with special pass after register > allocation. But ldm/stm commands require registers to go in ascending order, > what is often not so after regalloc, therefore some str/ldr commands. For > example such code: > > struct Foo {int a, b, c, d; } > void CopyStruct(struct Foo *a, struc...

...017-November/032950.html To me that shift from using nfs-ganesha to storhaug was a huge change to be absorbed for a minor release version and was made bigger when storhaug does not appear to be ready go given the recommendation to go back and use 3.10. With the release of 3.12 ltm and now 3.13 stm, when 4.0 is released 3.10 is shown to be at eol; Version Status ???? Release_Date EOL_Version EOL_Date 3.10 ?? LTM ??? ??? 2017-02-27 ?? 4.0 3.11 ?? EOL ??? ??? 2017-05-30 ?? 3.12 ??? ?? 2017-8-30 3.12 ?? LTM ??? ??? 2017-08-30??? 4.3 3.13 ?? STM ??? ??? 2017-12-7???? 4.0 4.0 ??? Planned STM abo...

Hello Everyone, Anyone know of a way of bypassing the 90K audiocodes mediant 3000 equipped for STM-1 interface using line cards and a linux box :). Kind Regards, Nick.

...> @@ -45,32 +45,63 @@ > TargetRegistry::RegisterAsmPrinter(TheAMDGPUTarget, createAMDGPUAsmPrinterPass); > } > > +AMDGPUAsmPrinter::AMDGPUAsmPrinter(TargetMachine &TM, MCStreamer &Streamer) > + : AsmPrinter(TM, Streamer) > +{ > + const AMDGPUSubtarget &STM = TM.getSubtarget<AMDGPUSubtarget>(); > + > + DisasmEnabled = STM.dumpCode() && > + STM.getGeneration() > AMDGPUSubtarget::NORTHERN_ISLANDS && > + ! Streamer.hasRawTextSupport(); > +} > + > /// We need to override th...

On 20/12/2017 16:51, Craig Lesle wrote: > With the release of 3.12 ltm and now 3.13 stm, when 4.0 is > released 3.10 is shown to be at eol; > > Version Status ???? Release_Date? EOL_Version EOL_Date > 3.10 ?? LTM ??? ??? 2017-02-27 ?? 4.0 ??? > 3.11 ?? EOL ??? ??? 2017-05-30 ?? 3.12 ??? ?? 2017-8-30 > 3.12 ?? LTM ??? ??? 2017-08-30??? 4.3 ??? > 3.13 ?? STM ??? ???...