search for: syscfg

...ff --git a/arch/arm/boot/dts/stih407-family.dtsi b/arch/arm/boot/dts/stih407-family.dtsi > index d1258d5..d263c96 100644 > --- a/arch/arm/boot/dts/stih407-family.dtsi > +++ b/arch/arm/boot/dts/stih407-family.dtsi > @@ -880,5 +880,81 @@ > status = "disabled"; > st,syscfg = <&syscfg_core>; > }; > + > + sti_uni_player0: sti-uni-player at 0 { > + compatible = "st,sti-uni-player"; > + status = "disabled"; > + #sound-dai-cells = <0>; > + st,syscfg = <&syscfg_core>; > + clocks = <&...

...ff --git a/arch/arm/boot/dts/stih407-family.dtsi b/arch/arm/boot/dts/stih407-family.dtsi > index d1258d5..d263c96 100644 > --- a/arch/arm/boot/dts/stih407-family.dtsi > +++ b/arch/arm/boot/dts/stih407-family.dtsi > @@ -880,5 +880,81 @@ > status = "disabled"; > st,syscfg = <&syscfg_core>; > }; > + > + sti_uni_player0: sti-uni-player at 0 { > + compatible = "st,sti-uni-player"; > + status = "disabled"; > + #sound-dai-cells = <0>; > + st,syscfg = <&syscfg_core>; > + clocks = <&...

...changed, 76 insertions(+) diff --git a/arch/arm/boot/dts/stih407-family.dtsi b/arch/arm/boot/dts/stih407-family.dtsi index d1258d5..d263c96 100644 --- a/arch/arm/boot/dts/stih407-family.dtsi +++ b/arch/arm/boot/dts/stih407-family.dtsi @@ -880,5 +880,81 @@ status = "disabled"; st,syscfg = <&syscfg_core>; }; + + sti_uni_player0: sti-uni-player at 0 { + compatible = "st,sti-uni-player"; + status = "disabled"; + #sound-dai-cells = <0>; + st,syscfg = <&syscfg_core>; + clocks = <&clk_s_d0_flexgen CLK_PCM_0>; + assi...

Hi, I have tried several different line options, but I cannot seem to get the pxe master password option to work? I have basically tried all combinations of: DEFAULT local PROMPT 0 ALLOWOPTIONS 1 TIMEOUT 500 MENU TITLE sometitle MENU MASTER PASSWD somepassword But just can't seem to get the menu to prompt for a password. version I have is pxe 3.31 Thanks for any help

...quot;; I find it's normally nicer to place the status of the node at the bottom, separated by a '\n'. There isn't a functional difference admittedly, but it would be my preference, since it's not describing the device per se. > + #sound-dai-cells = <0>; > + st,syscfg = <&syscfg_core>; > + reg = <0x8D83000 0x158>; We usually use lower-case for the address. Since this has a 'reg' property, the '0' in the node name does not look appropriate. > + interrupts = <GIC_SPI 87 IRQ_TYPE_NONE>; > + dmas = <&fdm...

...quot;; I find it's normally nicer to place the status of the node at the bottom, separated by a '\n'. There isn't a functional difference admittedly, but it would be my preference, since it's not describing the device per se. > + #sound-dai-cells = <0>; > + st,syscfg = <&syscfg_core>; > + reg = <0x8D83000 0x158>; We usually use lower-case for the address. Since this has a 'reg' property, the '0' in the node name does not look appropriate. > + interrupts = <GIC_SPI 87 IRQ_TYPE_NONE>; > + dmas = <&fdm...

...+++ b/arch/arm/boot/dts/stih407-family.dtsi @@ -956,5 +956,31 @@ st,version = <5>; st,mode = "SPDIF"; }; + + sti_uni_reader0: sti-uni-reader at 0 { + compatible = "st,sti-uni-reader"; + status = "disabled"; + #sound-dai-cells = <0>; + st,syscfg = <&syscfg_core>; + reg = <0x8D83000 0x158>; + interrupts = <GIC_SPI 87 IRQ_TYPE_NONE>; + dmas = <&fdma0 5 0 1>; + dma-names = "rx"; + dai-name = "Uni Reader #0 (PCM IN)"; + st,version = <3>; + }; + + sti_uni_reader1: sti-uni-r...

...;\n' in the next version. > There isn't a functional difference > admittedly, but it would be my preference, since it's not describing > the device per se. Will change to your preference in the next version. > > > + #sound-dai-cells = <0>; > > + st,syscfg = <&syscfg_core>; > > + reg = <0x8D83000 0x158>; > > We usually use lower-case for the address. Will fix. > > Since this has a 'reg' property, the '0' in the node name does not > look appropriate. Will fix. > > > + interrupts =...

Hi Vinod, Bjorn, Patrice, This patchset adds support for the Flexible Direct Memory Access (FDMA) core found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU with a dedicated firmware. It is a general purpose DMA controller supporting 16 independent channels and data can be moved from memory to memory or between memory and paced latency critical real time targets. After quite

Hi Vinod, Bjorn, Patrice, This patchset adds support for the Flexible Direct Memory Access (FDMA) core found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU with a dedicated firmware. It is a general purpose DMA controller supporting 16 independent channels and data can be moved from memory to memory or between memory and paced latency critical real time targets. After quite

...e "preserve DTB mappings"; - introduce a new "move setup_mm right after setup_pagetables" patch; - stop iterating over the DT nodes in device_tree_for_each_node if func returns a value != 0; - return 1 from _find_compatible_node when a node is found; - move the wait loop and the syscfg cfgctrl write into a separate function; - fix comments; - define all registers in write; - move platform_vexpress.c to platforms/vexpress.c; - move platform_vexpress.h to arm-arm/platforms/vexpress.h; - use a lookup table to set the color masks; - fix indentation; - make sure mode_string is not NUL...

...dtsi @@ -873,5 +873,12 @@ <&clk_s_c0_flexgen CLK_TX_ICN_DISP_0>, <&clk_s_c0_flexgen CLK_EXT2F_A9>; }; + + sti_sasg_codec: sti-sasg-codec { + compatible = "st,stih407-sas-codec"; + #sound-dai-cells = <1>; + status = "disabled"; + st,syscfg = <&syscfg_core>; + }; }; }; -- 1.9.1

...ed, 52 insertions(+) diff --git a/arch/arm/boot/dts/stih407-family.dtsi b/arch/arm/boot/dts/stih407-family.dtsi index d294e82..45cab30 100644 --- a/arch/arm/boot/dts/stih407-family.dtsi +++ b/arch/arm/boot/dts/stih407-family.dtsi @@ -821,5 +821,57 @@ clock-frequency = <600000000>; st,syscfg = <&syscfg_core 0x224>; }; + + /* fdma audio */ + fdma0: dma-controller at 8e20000 { + compatible = "st,stih407-fdma-mpe31-11", "st,slim-rproc"; + reg = <0x8e20000 0x8000>, + <0x8e30000 0x3000>, + <0x8e37000 0x1000>, +...

...listed. the ability to [un]lock specific keys in the agent in addition to the entire agent might also be useful. ssh-add -l would then show which keys are locked. ssh-add -[X|x] [key]. note - -i, -o should take precedence always. then deal with agent/files as above. 1. cmdline 2. usercfg 3. syscfg OpenSSH_3.5p1 FreeBSD-20030924, SSH protocols 1.5/2.0, OpenSSL 0x0090703f yeah, yeah... test key generation... cd ~/.ssh ; rm id* ssh-keygen -t dsa -b 512 -N defpass -C defkey -f id_dsa for key in a b c ; do ssh-keygen -t dsa -b 512 -N ${key}pass -C ${key}key -f id_dsa_$key done ssh host...

...uot;Sorry, there must be 2 arguments on the command line\n"; } -$etherdir = $ARGV[0]; -$outdir = $ARGV[1]; +if ($#ARGV == 2) +{ $debug = "true"; $etherdir = $ARGV[1]; $outdir = $ARGV[2]; } +else # $#ARGV == 1 +{ $etherdir = $ARGV[0]; $outdir = $ARGV[1]; } my $etherfile; my $syscfgfile; @@ -123,8 +126,7 @@ ($drivername, $leftover) = /^family\s+drivers\/net\/(\S+)/; if (defined $drivername) { - # Uncomment lines with "###" if you are debugging, for more verbosity. - ###print...