Keywords for Unprotocols - Unprotocols

Keywords for Unprotocols - Unprotocols:

'via Blog this'

Hi,

---

Flow-based programming - Wikipedia, the free encyclopedia

Flow-based programming - Wikipedia, the free encyclopedia:

'via Blog this'

First impression FBP made on me while playing with Lego edition of LabView. I still prefer CPS actor based style to program robots but I found that most of protocol handling can be nicely decomposed in FBP.

This is Umlet (http://www.umlet.com/) palette which you can copy to ../Umlet/palettes/FBP.uxf and use it for your own design.

  8
  
    com.umlet.element.custom.State
    
      8
      24
      104
      64
    
    READ
--
Read
  Masters

    
  
  
    com.umlet.element.Relation
    
      88
      40
      136
      64
    
    lt=->
m1=OUT
m2=IN[0]

    24;24;56;24;56;48;120;48
  
  
    com.umlet.element.custom.State
    
      208
      72
      104
      56
    
    COLLATE
--
Collate
    
  
  
    com.umlet.element.custom.State
    
      8
      112
      104
      64
    
    READ
--
Read
  Details

    
  
  
    com.umlet.element.Relation
    
      88
      88
      136
      72
    
    lt=->
m1=OUT
m2=IN[1]

    24;56;56;56;56;24;120;24
  
  
    com.umlet.element.custom.State
    
      200
      224
      112
      64
    
    PROC
--
Process
 Merged Streams
    
  
  
    com.umlet.element.Relation
    
      232
      104
      40
      136
    
    lt=->
m1=OUT
m2=IN

    24;24;24;120
  
  
    com.umlet.element.custom.State
    
      8
      192
      104
      64
    
    WRITE
--
Write
  New Masters

    
  
  
    com.umlet.element.custom.State
    
      8
      272
      104
      64
    
    REPORT
--
Summary 
 & Errors

    
  
  
    com.umlet.element.Relation
    
      88
      200
      128
      64
    
    lt=->
m1=OUTM
m2=IN

    112;48;88;48;88;24;24;24
  
  
    com.umlet.element.Relation
    
      88
      240
      128
      72
    
    lt=->
m1=OUTSE
m2=IN

    112;24;88;24;88;56;24;56
  

Using xrandr and gtf to add a new mode to your X configuration at runtime | arunviswanathan.com

Using xrandr and gtf to add a new mode to your X configuration at runtime | arunviswanathan.com:

'via Blog this'

In case if xrand reports:


DP3 connected 1920x1080+1680+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080      60.0 +
   1680x1050      60.0

but monitor can not detect signal it is worst to try subj solution.

In my case HP EliteBook -> DP -> Benq BL2400 could not accept  '1920x1080      60.0' but

was convinced via:

xrandr --output LVDS1 --off
xrandr --newmode "1920x1080_59.90"  172.51  1920 2040 2248 2576  1080 1081 1084 1118  -HSync +Vsync
xrandr --addmode DP3 1920x1080_59.90
xrandr --output DP3 --mode 1920x1080_59.90 --rotate normal --output VGA1 --auto --rotate normal --left-of DP3 --pos 0x0

GIT tuning from under firewall

This summary is not available. Please click here to view the post.

The Linux Kernel Makefile.in

OpenSS7, one of my favorite projects, succeed to make fully blown LKM compilation.

After some experiments fail miserable...
My KISS style LKM inside Atoconf based on faking Makefile.in

---

OpenSS7 macro to find kernel

# =========================================================================
# _LINUX_KERNEL
# -------------------------------------------------------------------------
# The linux kernel build directory is the build kernel tree root against which
# kernel modules will be compiled.
# -------------------------------------------------------------------------
AC_DEFUN([_LINUX_KERNEL], [dnl
    AC_CACHE_CHECK([for kernel build directory], [linux_cv_kernel_build], [dnl
 AC_MSG_RESULT([searching...])
 AC_ARG_WITH([kernel-build],
     AS_HELP_STRING([--with-kernel-build=DIR],
  [specify the base kernel build directory in which configured
  kernel source resides.]),
     [with_kernel_build="$withval"],
     [with_kernel_build=])
 if test :"${with_kernel_build:-no}" != :no
 then
     linux_cv_kernel_build="$with_kernel_build"
 fi
 if test :"${linux_cv_kernel_build:-no}" = :no -o ! -d "$linux_cv_kernel_build"
 then
     if test :"${linux_cv_kernel_build:-no}" = :no
     then
  AC_MSG_ERROR([
***
*** This package does not support headless kernel build.  Install the
*** appropriate built kernel-source and kernel-headers package for the
*** target kernel and then configure again.
***
*** The following directories do no exist in the build environment:
*** "$with_kernel_build"
***
*** ])
     fi
 fi
 AC_MSG_CHECKING([for kernel build directory]) ])
    kbuilddir="$linux_cv_kernel_build"
    AC_SUBST([kbuilddir])dnl
])# LINUX_KERNEL

---

acinclude.in per module macro

# =============================================================================
# _MODEM_SETUP_MODULES
# -----------------------------------------------------------------------------
AC_DEFUN([_MODEM_SETUP_MODULES], [dnl
    AC_ARG_ENABLE([module-lte-sched],
 AS_HELP_STRING([--enable-module-lte-sched],
     [enable module lte_sched for linkage with MODEM.
     @<:@default=module@:>@]),
     [enable_module_lte_sched="$enableval"],
     [if test :${modem_big_compile:-yes} = :yes ; then enable_module_lte_sched='yes' ; else enable_module_lte_sched='module' ; fi])
    AM_CONDITIONAL([CONFIG_MODEM_LTE_SCHED],  [test :${modem_cv_module_lte_sched:-module} = :yes])
# -----------------------------------------------------------------------------

    AC_CACHE_CHECK([for MODEM module lte_sched], [modem_cv_module_lte_sched], [dnl
 modem_cv_module_lte_sched="${enable_module_lte_sched:-module}"
 if test :$modem_cv_module_lte_sched = :module -a :${linux_cv_k_linkage:-loadable} = :linkable ; then
     modem_cv_module_lte_sched='yes'
 fi])
# -----------------------------------------------------------------------------
    case ${modem_cv_module_lte_sched:-module} in
 (yes)
     AC_DEFINE_UNQUOTED([CONFIG_MODEM_LTE_SCHED], [1], [When defined,] AC_PACKAGE_TITLE [
     will include the lte_sched module for linkage with MODEM.  When undefined,]
     AC_PACKAGE_TITLE [will not include the lte_sched module for linkage with MODEM.])
     ;;
 (module)
     AC_DEFINE_UNQUOTED([CONFIG_MODEM_LTE_SCHED_MODULE], [1], [When defined,]
     AC_PACKAGE_TITLE [will include the lte_sched module as a standalone loadable kernel module.  When
     undefined,] AC_PACKAGE_TITLE [will not include the lte_sched module as a standalone loadable kernel
     module.])
     ;;
    esac
# -----------------------------------------------------------------------------
    AM_CONDITIONAL([CONFIG_MODEM_LTE_SCHED],  [test :${modem_cv_module_lte_sched:-module} = :yes])
    AM_CONDITIONAL([CONFIG_MODEM_LTE_SCHED_MODULE], [test :${modem_cv_module_lte_sched:-module} = :module])
])# _MODEM_SETUP_MODULES

---

Fake Makefile.in

target_alias = @target_alias@
target_cpu = @target_cpu@
prefix = @prefix@

KERNEL_ROOT=@kbuilddir@
TARGETDIR=$(prefix)/firmware

ifneq ($(KERNELRELEASE),)
ifdef V
    KBUILD_VERBOSE = $(V)
endif

EXTRA_CFLAGS += -I$(src)
EXTRA_CFLAGS += 

@CONFIG_LTE_SCHED_MODULE_TRUE@lte_sched.c: lte_sched.h
@CONFIG_LTE_SCHED_MODULE_TRUE@obj-m += lte_sched.o

#sched_csap-y := sched_csap.o

else

all: modules

modules:
 echo "Making $@ in `pwd`"
 ARCH=$(target_cpu) CROSS_COMPILE="$(target_alias)-" \
 $(MAKE) V=1 -C $(KERNEL_ROOT) M=`pwd` modules

clean:
 echo "Making $@ in `pwd`"
 ARCH=$(target_cpu) CROSS_COMPILE="$(target_alias)-" \
 $(MAKE) V=0 -C $(KERNEL_ROOT) M=`pwd` clean

install:
 echo "Making $@ in `pwd`"
 ARCH=$(target_cpu) CROSS_COMPILE="$(target_alias)-" \
 $(MAKE) V=1 -C $(KERNEL_ROOT) M=`pwd` INSTALL_MOD_PATH=$(TARGETDIR) modules_install 
endif