Home
last modified time | relevance | path

Searched refs:tested (Results 1 – 25 of 227) sorted by relevance

12345678910

/Linux-v6.6/Documentation/arch/arm/sa1100/
Dassabet.rst254 - PM: Not tested.
256 - PM: Not tested.
257 - I2C: Implemented, not fully tested.
258 - L3: Fully tested, pass.
259 - PM: Not tested.
262 - LCD: Fully tested. PM
270 - Playback: Fully tested, pass.
271 - Record: Implemented, not tested.
272 - PM: Not tested.
275 - Audio play: Implemented, not heavily tested.
[all …]
/Linux-v6.6/tools/testing/selftests/powerpc/eeh/
Deeh-vf-aware.sh16 tested=0
26 tested="$((tested + 1))"
39 if [ "$tested" == 0 ] ; then
/Linux-v6.6/Documentation/arch/arm/vfp/
Drelease-notes.rst19 The operations which have been tested with this package are:
41 Other operations which have been tested by basic assembly-only tests
51 The combination operations have not been tested:
/Linux-v6.6/Documentation/misc-devices/
Dpci-endpoint-test.rst31 Tests the BAR. The number of the BAR to be tested
37 to be tested should be passed as argument.
40 to be tested should be passed as argument.
/Linux-v6.6/drivers/media/pci/tw686x/
DKconfig14 - TW6865 (4 video channels, not tested, second generation chip),
16 built-in video decoder are supported, not tested),
/Linux-v6.6/Documentation/firmware-guide/acpi/
Dosi.rst22 Linux runs on two groups of machines -- those that are tested by the OEM
23 to be compatible with Linux, and those that were never tested with Linux,
26 The larger group is the systems tested to run only Windows. Not only that,
27 but many were tested to run with just one specific version of Windows.
29 only a single path through the BIOS has actually been tested.
122 a BIOS that has been tested only with that _OSI returning TRUE.
133 in tested flows to support real Linux features. In 2009, Linux
141 ACPI BIOS that are tested on Windows machines. There is a real risk
175 Just like on Windows-tested platforms, this strategy has risks.
/Linux-v6.6/Documentation/input/devices/
Dcs461x.rst10 is present here, but have not tested completely. The button analysis
14 driver as a backend. I've tested this driver with CS4610, 4-axis and
19 The sensitivity and calibrate quality have not been tested; the two
/Linux-v6.6/Documentation/dev-tools/kunit/
Dstyle.rst33 test subsystem should match a single kernel module. If the code being tested
38 Test subsystems should be named after the code being tested, either after the
39 module (wherever possible), or after the directory or files being tested. Test
80 functionality being tested. Test suites can have shared initialization and
129 function being tested, with a description of the input or codepath being tested.
162 tested, or be under [Kernel Hacking]->[Kernel Testing and Coverage]
/Linux-v6.6/Documentation/devicetree/bindings/mtd/
Dlpc32xx-slc.txt11 - nxp,wdr-clks: Delay before Ready signal is tested on write (W_RDY)
12 - nxp,rdr-clks: Delay before Ready signal is tested on read (R_RDY)
/Linux-v6.6/Documentation/networking/device_drivers/fddi/
Dskfp.rst64 Compaq adapters (not tested):
245 - not tested with 2.1.xx kernels
246 - integration in kernel not tested
247 - not tested simultaneously with FDDI adapters from other vendors.
/Linux-v6.6/Documentation/fb/
Dmetronomefb.rst29 udev/hotplug setup. I have only tested with a single waveform file which was
37 mappable frame buffer. It has been tested with tinyx (Xfbdev). It is known
/Linux-v6.6/drivers/media/platform/via/
DKconfig13 Chrome9 chipsets. Currently only tested on OLPC xo-1.5 systems
/Linux-v6.6/tools/testing/selftests/firmware/
Dsettings3 # present, each with 2 "nowait" functions tested 5 times. Expected time for a
/Linux-v6.6/tools/testing/selftests/rcutorture/doc/
DTINY_RCU.txt19 In common code tested by TREE_RCU test cases.
/Linux-v6.6/drivers/media/pci/solo6x10/
DKconfig16 Following cards have been tested:
/Linux-v6.6/net/mac802154/
DKconfig18 been tested yet!
/Linux-v6.6/arch/m68k/hp300/
DREADME.hp3006 Currently only 9000/340 machines have been tested. Any amount of RAM should
/Linux-v6.6/kernel/rcu/
DKconfig.debug34 after the fact on the running kernel to be tested, if desired.
49 after the fact on the running kernel to be tested, if desired.
65 tested, if desired.
/Linux-v6.6/drivers/gpu/drm/omapdrm/
DTODO19 Currently tested on
/Linux-v6.6/Documentation/hwmon/
Dlm92.rst47 which are mostly compatible. They have not all been tested, so you
/Linux-v6.6/drivers/net/ethernet/synopsys/
DKconfig35 This driver was tested on Synopsys XLGMAC IP Prototyping Kit.
/Linux-v6.6/tools/power/cpupower/
DTODO24 tested executable.
/Linux-v6.6/Documentation/admin-guide/media/
Davermedia.rst49 that the card presents), but this has not been tested yet. If
74 via /dev/dvb/adapter{x}/dvr0. I have not tested the
/Linux-v6.6/Documentation/dev-tools/
Dtesting-overview.rst33 of the kernel, which can be tested in isolation. This aligns well with the
55 (e.g. by a syscall, device, filesystem, etc.) can be tested with kselftest. To
61 expose an interface to userspace, which can be tested, but not implementation
71 of code. This is useful for determining how much of the kernel is being tested,
/Linux-v6.6/Documentation/process/
Dstable-kernel-rules.rst10 - It must be obviously correct and tested.
193 to be tested by developers and testers.
196 be queued. Additional -rc releases are then released and tested until no
202 containing all the queued and tested patches.

12345678910