| /dports/graphics/lightzone/LightZone-4.1.8-3-g36e87773/lightcrafts/locale/com/lightcrafts/image/metadata/makernotes/ |
| H A D | PentaxTags.properties | 353 003F>787=SMC Pentax-F 24-50mm F4
354 003F>788=SMC Pentax-F 35-80mm F4-5.6
366 003F>800=SMC Pentax-F 50mm F1.4
367 003F>801=SMC Pentax-F 50mm F1.7
369 003F>803=SMC Pentax-F 28mm F2.8
378 003F>818=SMC Pentax-FA 28-70mm F4 AL
405 003F>1052=SMC Pentax-FA 35mm F2 AL
445 003F>1283=SMC Pentax-FA 50mm F1.7
446 003F>1284=SMC Pentax-FA 50mm F1.4
468 003F>1545=SMC Pentax-FA 20mm F2.8
[all …]
|
| /dports/devel/cc65/cc65-2.19/doc/ |
| H A D | smc.sgml | 60 SMC:
69 labeled SMC target.
178 SMC SumRegister, { LDA #10 }
192 SMC ShiftOrNothing, { LSL }
210 SMC AdaptCharWidth, { NOP }
306 SMC LoadData, { LDA $2000 }
323 SMC LoadData, { LDA $2000 }
462 SMC instructions.
475 SMC LoadMask, { LDA #$20 }
522 SMC LoadValue, { LDA #12 }
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/net/smc/ |
| H A D | Kconfig | 2 config SMC config
3 tristate "SMC socket protocol family"
6 SMC-R provides a "sockets over RDMA" solution making use of
9 The Linux implementation of the SMC-R solution is designed as
10 a separate socket family SMC.
12 Select this option if you want to run SMC socket applications
15 tristate "SMC: socket monitoring interface"
16 depends on SMC
18 Support for SMC socket monitoring interface used by tools such as
|
| /dports/multimedia/libv4l/linux-5.13-rc2/net/smc/ |
| H A D | Kconfig | 2 config SMC config
3 tristate "SMC socket protocol family"
6 SMC-R provides a "sockets over RDMA" solution making use of
9 The Linux implementation of the SMC-R solution is designed as
10 a separate socket family SMC.
12 Select this option if you want to run SMC socket applications
15 tristate "SMC: socket monitoring interface"
16 depends on SMC
18 Support for SMC socket monitoring interface used by tools such as
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/net/smc/ |
| H A D | Kconfig | 2 config SMC config
3 tristate "SMC socket protocol family"
6 SMC-R provides a "sockets over RDMA" solution making use of
9 The Linux implementation of the SMC-R solution is designed as
10 a separate socket family SMC.
12 Select this option if you want to run SMC socket applications
15 tristate "SMC: socket monitoring interface"
16 depends on SMC
18 Support for SMC socket monitoring interface used by tools such as
|
| /dports/math/R-cran-psych/psych/R/ |
| H A D | ICLUST.R | 19 …,cut=0,n.iterations=0,title="iclust",plot=TRUE,weighted=TRUE,cor.gen =TRUE,SMC=TRUE,purify=TRUE ) { argument
20 …ter,reverse,beta.min,output,digits,labels,cut,n.iterations,title,plot,weighted,cor.gen,SMC,purify)}
24 …,cut=0,n.iterations=0,title="ICLUST",plot=TRUE,weighted=TRUE,cor.gen =TRUE,SMC=TRUE,purify=TRUE ) … argument
32 …e=reverse,beta.min=beta.min,output=output,digits=digits,weighted=weighted,cor.gen=cor.gen,SMC=SMC) nameattr
43 …loads <- cluster.loadings(iclust.results$clusters,r.mat,SMC=SMC) #summarize the results by using c…
49 …loads <- cluster.loadings(sorted.cluster.keys,r.mat,SMC=SMC) #these are the original cluster load…
76 loads <- cluster.loadings(clusters,r.mat,SMC=SMC)
80 loads <- cluster.loadings(clusters,r.mat,SMC=SMC)
84 loads <- cluster.loadings(clusters,r.mat,SMC=SMC)
98 purified <- cluster.cor(p.sorted$clusters,r.mat,SMC=SMC)
|
| H A D | fa.parallel.poly.R | 3 function(x,n.iter=10,SMC=TRUE,fm="minres") { argument
14 f <- fa(r,n.obs=n.obs,SMC = SMC,covar=FALSE,fm=fm) #call fa with the appropriate parameters
30 fs <- fa(r,n.obs=n.obs,SMC = SMC,covar=FALSE,fm=fm) #call fa with the appropriate parameters
|
| /dports/sysutils/atf-sun50i_h6/arm-trusted-firmware-2.5/docs/security_advisories/ |
| H A D | security-advisory-tfv-8.rst | 6 | | Normal World SMC client to another |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact | Leakage of SMC return values from one normal world SMC |
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
65 software must trap SMC calls from EL1 software to ensure secure behaviour.
68 SMC synchronous exception. It has behaved this way since the first version.
[all …]
|
| /dports/sysutils/atf-sun50i_a64/arm-trusted-firmware-2.5/docs/security_advisories/ |
| H A D | security-advisory-tfv-8.rst | 6 | | Normal World SMC client to another |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact | Leakage of SMC return values from one normal world SMC |
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
65 software must trap SMC calls from EL1 software to ensure secure behaviour.
68 SMC synchronous exception. It has behaved this way since the first version.
[all …]
|
| /dports/sysutils/atf-rk3328/arm-trusted-firmware-2.5/docs/security_advisories/ |
| H A D | security-advisory-tfv-8.rst | 6 | | Normal World SMC client to another |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact | Leakage of SMC return values from one normal world SMC |
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
65 software must trap SMC calls from EL1 software to ensure secure behaviour.
68 SMC synchronous exception. It has behaved this way since the first version.
[all …]
|
| /dports/sysutils/atf-fvp/arm-trusted-firmware-2.5/docs/security_advisories/ |
| H A D | security-advisory-tfv-8.rst | 6 | | Normal World SMC client to another |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact | Leakage of SMC return values from one normal world SMC |
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
65 software must trap SMC calls from EL1 software to ensure secure behaviour.
68 SMC synchronous exception. It has behaved this way since the first version.
[all …]
|
| /dports/sysutils/atf-rk3399/arm-trusted-firmware-2.5/docs/security_advisories/ |
| H A D | security-advisory-tfv-8.rst | 6 | | Normal World SMC client to another |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact | Leakage of SMC return values from one normal world SMC |
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
65 software must trap SMC calls from EL1 software to ensure secure behaviour.
68 SMC synchronous exception. It has behaved this way since the first version.
[all …]
|
| /dports/emulators/mess/mame-mame0226/src/devices/cpu/alto2/ |
| H A D | alto2cpu.cpp | 1996 case SMC(0,0,0,0, 1, 1): in alu_74181()
2009 case SMC(0,0,0,1, 1, 1): in alu_74181()
2022 case SMC(0,0,1,0, 1, 1): in alu_74181()
2035 case SMC(0,0,1,1, 1, 1): in alu_74181()
2048 case SMC(0,1,0,0, 1, 1): in alu_74181()
2061 case SMC(0,1,0,1, 1, 1): in alu_74181()
2074 case SMC(0,1,1,0, 1, 1): in alu_74181()
2087 case SMC(0,1,1,1, 1, 1): in alu_74181()
2100 case SMC(1,0,0,0, 1, 1): in alu_74181()
2113 case SMC(1,0,0,1, 1, 1): in alu_74181()
[all …]
|
| /dports/emulators/mame/mame-mame0226/src/devices/cpu/alto2/ |
| H A D | alto2cpu.cpp | 1996 case SMC(0,0,0,0, 1, 1): in alu_74181()
2009 case SMC(0,0,0,1, 1, 1): in alu_74181()
2022 case SMC(0,0,1,0, 1, 1): in alu_74181()
2035 case SMC(0,0,1,1, 1, 1): in alu_74181()
2048 case SMC(0,1,0,0, 1, 1): in alu_74181()
2061 case SMC(0,1,0,1, 1, 1): in alu_74181()
2074 case SMC(0,1,1,0, 1, 1): in alu_74181()
2087 case SMC(0,1,1,1, 1, 1): in alu_74181()
2100 case SMC(1,0,0,0, 1, 1): in alu_74181()
2113 case SMC(1,0,0,1, 1, 1): in alu_74181()
[all …]
|
| /dports/sysutils/atf-sun50i_h6/arm-trusted-firmware-2.5/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 12 Call (SMC) instruction. These requests will follow the convention described in
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function
14 identifiers to each SMC request and describes how arguments are passed and
17 SMC Functions are grouped together based on the implementor of the service, for
36 The SMC Function Identifier includes a OEN field. These values and their
69 The SMC Function ID also indicates whether the call has followed the SMC32
76 specific handler for each SMC call, but it is expected that an individual
157 SMC Function call via the handler function.
180 SMC calls for a service are forwarded by the framework to the service's SMC
196 otherwise completing the request with the *Unknown SMC Function ID*:
[all …]
|
| /dports/sysutils/atf-sun50i_a64/arm-trusted-firmware-2.5/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 12 Call (SMC) instruction. These requests will follow the convention described in
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function
14 identifiers to each SMC request and describes how arguments are passed and
17 SMC Functions are grouped together based on the implementor of the service, for
36 The SMC Function Identifier includes a OEN field. These values and their
69 The SMC Function ID also indicates whether the call has followed the SMC32
76 specific handler for each SMC call, but it is expected that an individual
157 SMC Function call via the handler function.
180 SMC calls for a service are forwarded by the framework to the service's SMC
196 otherwise completing the request with the *Unknown SMC Function ID*:
[all …]
|
| /dports/sysutils/atf-rk3328/arm-trusted-firmware-2.5/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 12 Call (SMC) instruction. These requests will follow the convention described in
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function
14 identifiers to each SMC request and describes how arguments are passed and
17 SMC Functions are grouped together based on the implementor of the service, for
36 The SMC Function Identifier includes a OEN field. These values and their
69 The SMC Function ID also indicates whether the call has followed the SMC32
76 specific handler for each SMC call, but it is expected that an individual
157 SMC Function call via the handler function.
180 SMC calls for a service are forwarded by the framework to the service's SMC
196 otherwise completing the request with the *Unknown SMC Function ID*:
[all …]
|
| /dports/sysutils/atf-fvp/arm-trusted-firmware-2.5/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 12 Call (SMC) instruction. These requests will follow the convention described in
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function
14 identifiers to each SMC request and describes how arguments are passed and
17 SMC Functions are grouped together based on the implementor of the service, for
36 The SMC Function Identifier includes a OEN field. These values and their
69 The SMC Function ID also indicates whether the call has followed the SMC32
76 specific handler for each SMC call, but it is expected that an individual
157 SMC Function call via the handler function.
180 SMC calls for a service are forwarded by the framework to the service's SMC
196 otherwise completing the request with the *Unknown SMC Function ID*:
[all …]
|
| /dports/sysutils/atf-rk3399/arm-trusted-firmware-2.5/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 12 Call (SMC) instruction. These requests will follow the convention described in
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function
14 identifiers to each SMC request and describes how arguments are passed and
17 SMC Functions are grouped together based on the implementor of the service, for
36 The SMC Function Identifier includes a OEN field. These values and their
69 The SMC Function ID also indicates whether the call has followed the SMC32
76 specific handler for each SMC call, but it is expected that an individual
157 SMC Function call via the handler function.
180 SMC calls for a service are forwarded by the framework to the service's SMC
196 otherwise completing the request with the *Unknown SMC Function ID*:
[all …]
|
| /dports/devel/z88dk/z88dk/libsrc/target/zx/graphics/ |
| H A D | clrarea2.asm | 20 ; Generic SMC version by Stefano Bodrato.
33 ;ld (coord+1),hl ; SMC: remember y,x
39 ld (saddr+1),de ; SMC: remember screen address
42 ld (bitmaskl1+1),a ; SMC
43 ld (bitmaskl2+1),a ; SMC
97 .saddr ld hl,0 ; SMC
99 ld (saddr+1),hl ; SMC
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/drivers/net/ethernet/smsc/ |
| H A D | Kconfig | 3 # Western Digital/SMC network device configuration
7 bool "SMC (SMSC)/Western Digital devices"
17 the questions about SMC/Western Digital cards. If you say Y, you will
23 tristate "SMC 9194 support"
37 tristate "SMC 91C9x/91C1xxx support"
44 This is a driver for SMC's 91x series of Ethernet chipsets,
55 tristate "SMC 91Cxx PCMCIA support"
60 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
67 tristate "SMC EtherPower II"
72 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
|
| /dports/multimedia/libv4l/linux-5.13-rc2/drivers/net/ethernet/smsc/ |
| H A D | Kconfig | 3 # Western Digital/SMC network device configuration
7 bool "SMC (SMSC)/Western Digital devices"
17 the questions about SMC/Western Digital cards. If you say Y, you will
23 tristate "SMC 9194 support"
37 tristate "SMC 91C9x/91C1xxx support"
44 This is a driver for SMC's 91x series of Ethernet chipsets,
55 tristate "SMC 91Cxx PCMCIA support"
60 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
67 tristate "SMC EtherPower II"
72 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/drivers/net/ethernet/smsc/ |
| H A D | Kconfig | 3 # Western Digital/SMC network device configuration
7 bool "SMC (SMSC)/Western Digital devices"
17 the questions about SMC/Western Digital cards. If you say Y, you will
23 tristate "SMC 9194 support"
37 tristate "SMC 91C9x/91C1xxx support"
44 This is a driver for SMC's 91x series of Ethernet chipsets,
55 tristate "SMC 91Cxx PCMCIA support"
60 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
67 tristate "SMC EtherPower II"
72 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
|
| /dports/devel/z88dk/z88dk/libsrc/gfx/narrow/ |
| H A D | clrarea2.asm | 19 ; Generic SMC version by Stefano Bodrato.
32 ld (coord+1),hl ; SMC: remember y,x
40 ld (bitmaskl1+1),a ; SMC
41 ld (bitmaskl2+1),a ; SMC
93 .coord ld hl,0 ; SMC -> y,x
95 ld (coord+1),hl ; SMC -> y,x
|
| /dports/misc/rump/buildrump.sh-b914579/src/sys/dev/acpi/ |
| H A D | acpidevs | 210 PNP80dd SMC ARCNETPC
211 PNP80de SMC ARCNET PC100, PC200
212 PNP80df SMC ARCNET PC110, PC210, PC250
213 PNP80e0 SMC ARCNET PC130/E
215 PNP80e2 SMC ARCNET PC270/E
216 PNP80e5 SMC ARCNET PC600W, PC650W
244 PNP8123 SMC StarCard PLUS (WD/8003S)
246 PNP8125 SMC EtherCard PLUS (WD/8003E)
275 PNP81c8 SMC EtherElite Ultra 16
292 PNP8227 SMC 3000 Series
[all …]
|