Platforms supported by linux

Supported Platforms

This page contains information about all platforms (meaning architecture+compiler combinations) supported by the upcoming wxWidgets 3.0 release.

You may also be interested in the list of supported classes for each platform.

Contents

Tier-1 Platforms

These architectures/compilers are tested regularly and before each release and are never supposed to be broken:

• Win32 using Microsoft Visual C++ 2005, 2008, 2010.
• Win64 using Microsoft Visual C++ 2010.
• Linux using g++ 4
• OS X using Apple g++ or clang

We try to support as many other platforms as possible but they are not tested as regularly. Your help with testing them and reporting your results on this wiki is welcome!

Platforms supported by wxMSW

The programs using wxMSW run on any of the desktop 32-bit Windows version, including Windows 95 (and Windows 98/ME/NT4/2000/XP/Vista/2008/7/8/2012). wxMSW was tested with the following compilers:

50000

OS	Compiler	Version	Last tested svn revision	Remarks
Win32 (Windows 9x/NT/XP/2003/Vista/2008/7/8/2012)	Microsoft Visual C++	5.0	Not officially supported but may work using VC6 project files
		6.0	2.9.2 / trunk	checked by a buildbot
		7.1 (a.k.a. 2003)	2.9.0
		8.0 (a.k.a. 2005)	2.9.0
		9.0 (a.k.a. 2008)	2.9.5 / trunk	checked by a buildbot
		10.0 (a.k.a. 2010)	trunk-rev66841	Starting rev 66836, everything compiles w/o errors. No need for any project-files workaround.
	mingw32 g++	3.4.2 (using makefiles)	2.9.0
		3.4.5 (with MSYS/configure)	2.9.5
		4.3.1 (with MSYS/configure)	55381
		4.5.2 (using makefiles)	2.9.3 RC1
		4.6.1 (using MSYS/configure)	r70370
	Cygwin g++	3.4.4/4.3.4 (Cygwin 1.5/1.7)	65114	Compiles, links, and appears to run. Unit testing has not been run as of 2010/07/26
		4.3.4 (Cygwin 1.7)	2.8.10	build fails , see
		4.5.3 (Cygwin 1.7)	2.9.5	Configured with --host=i686-w64-mingw32 --build=i686-pc-cygwin as explained in . If using wxWebView, insert two missing ‘>’ characters at the lines pointed out by the compiler in /usr/i686-w64-mingw32/sys-root/mingw/include/mshtml.h
	Borland C++	5.5	Fixed with Patch ID 1902415. Was: Broken as of r51810 due to wxWeakRef changes.	minimal Ok; larger programs should be built using -DSHARED=1 for library and program
		5.6
		5.8 (BCB 2006)		minimal Ok; larger programs should be built using -DSHARED=1 for library and program
		6.3 (CodeGear C++Builder 2008)	r66666	minimal Ok
	Open Watcom	1.6 / 1.7	53417	have issues with templates (2.8.7 is Ok with 1.6 and 1.7)
		1.8 beta tested 30 April	53417	compiles, links and run ok
	Digital Mars	8.50	does not compile
Win64 (Windows XP/2003/Vista/2008/7/8/2012)	Microsoft Visual C++	7.1 (a.k.a. 2003)
		9.0 (a.k.a. 2008)	2.9.5
	mingw64	4.4.0 (experimental)

Platforms supported by wxGTK

wxGTK can be compiled either using GTK+ 2 or GTK+ 1.2. The latter port is called wxGTK1 and is not actively maintained any more, although it is still supported for now. wxGTK2 should, in principle, work with any GTK+ 2 version but is mostly tested with GTK+ >= 2.4 as many of optional features are not available with GTK+ 2.2 or below and some features only work with GTK+ 2.12 or later.

r45000

OS	Arch	Compiler	Version	Last tested wx version	Remarks
Linux (2.4 or 2.6 kernel, glibc 2.x)	x86	g++	2.95
			3.2
			3.3
			3.4
			4.0
			4.1
			4.4/4.5/4.6	2.9.3
			4.7 (2012-01-28 snapshot)	r70472	Building in C++11 mode requires the patch of r70556.
		Intel C/C++ (icc)	9.1	r48901
			10.0	r56828	PCH support works fine in this version (see below)
			11.0	r56828	PCH support seems to be broken
		Sun CC for Linux	5.11	2.9.3
	x64	g++	4.7 (2012-01-28 snapshot)	r70472	Building in C++11 mode requires the patch of r70556.
NetBSD 3.1	amd64	g++	3.3.3	r48909
FreeBSD 6.2	amd64	g++	3.4.6	2.9.0
OpenBSD 4.2	x86	g++	3.3.5
Solaris	UltraSPARC IV+ Sun-Fire-V890	g++	3.4.5	r49502
	UltraSPARC IV+ Sun-Fire-V890	Sun CC	5.9	r49502
	x86	Sun CC	5.12	2.9.3	Last OpenSolaris version (5.11 snv_134)
HP-UX 11.31	ia64	HP aC++	B3910B A.06.15	trunk r56786
HP-UX 11.11	PA	HP aC++	3.80	trunk r51426	CC=»aCC -Ae» CXX=»aCC -AA -ext»
AIX 5.3	IBM XL C/C++	7.00	2.9.3

Platforms supported by wxX11/Univ

wxX11 port was recently tested in the following configurations:

OS	Compiler	Version	Last tested wx version	Remarks

Platforms supported by wxDFB

OS	Compiler	Version	Last tested wx version	Remarks

Platforms supported by wxMotif

wxMotif can be used either with Motif (version 2, version 1 might still be supported but is not tested as Motif 1 is rather difficult to find nowadays) or Lesstif.

OS	Compiler	Version	Last tested wx version	Remarks

Other ports

Other ports are limited to their native OS: wxMac builds under OS X, wxPM — under OS/2 and so on.

Old cumulative platforms table

Here is the copy of the old page for the reference, testing results for the platforms not yet tested with wxWidgets 3.0 are welcome!

Источник

Platform Devices and Drivers¶

See
for the driver model interface to the platform bus: platform_device, and platform_driver. This pseudo-bus is used to connect devices on busses with minimal infrastructure, like those used to integrate peripherals on many system-on-chip processors, or some “legacy” PC interconnects; as opposed to large formally specified ones like PCI or USB.

Platform devices¶

Platform devices are devices that typically appear as autonomous entities in the system. This includes legacy port-based devices and host bridges to peripheral buses, and most controllers integrated into system-on-chip platforms. What they usually have in common is direct addressing from a CPU bus. Rarely, a platform_device will be connected through a segment of some other kind of bus; but its registers will still be directly addressable.

Platform devices are given a name, used in driver binding, and a list of resources such as addresses and IRQs:

Platform drivers¶

Platform drivers follow the standard driver model convention, where discovery/enumeration is handled outside the drivers, and drivers provide probe() and remove() methods. They support power management and shutdown notifications using the standard conventions:

Note that probe() should in general verify that the specified device hardware actually exists; sometimes platform setup code can’t be sure. The probing can use device resources, including clocks, and device platform_data.

Platform drivers register themselves the normal way:

Or, in common situations where the device is known not to be hot-pluggable, the probe() routine can live in an init section to reduce the driver’s runtime memory footprint:

Kernel modules can be composed of several platform drivers. The platform core provides helpers to register and unregister an array of drivers:

If one of the drivers fails to register, all drivers registered up to that point will be unregistered in reverse order. Note that there is a convenience macro that passes THIS_MODULE as owner parameter:

Device Enumeration¶

As a rule, platform specific (and often board-specific) setup code will register platform devices:

The general rule is to register only those devices that actually exist, but in some cases extra devices might be registered. For example, a kernel might be configured to work with an external network adapter that might not be populated on all boards, or likewise to work with an integrated controller that some boards might not hook up to any peripherals.

In some cases, boot firmware will export tables describing the devices that are populated on a given board. Without such tables, often the only way for system setup code to set up the correct devices is to build a kernel for a specific target board. Such board-specific kernels are common with embedded and custom systems development.

In many cases, the memory and IRQ resources associated with the platform device are not enough to let the device’s driver work. Board setup code will often provide additional information using the device’s platform_data field to hold additional information.

Embedded systems frequently need one or more clocks for platform devices, which are normally kept off until they’re actively needed (to save power). System setup also associates those clocks with the device, so that calls to clk_get(&pdev->dev, clock_name) return them as needed.

Legacy Drivers: Device Probing¶

Some drivers are not fully converted to the driver model, because they take on a non-driver role: the driver registers its platform device, rather than leaving that for system infrastructure. Such drivers can’t be hotplugged or coldplugged, since those mechanisms require device creation to be in a different system component than the driver.

The only “good” reason for this is to handle older system designs which, like original IBM PCs, rely on error-prone “probe-the-hardware” models for hardware configuration. Newer systems have largely abandoned that model, in favor of bus-level support for dynamic configuration (PCI, USB), or device tables provided by the boot firmware (e.g. PNPACPI on x86). There are too many conflicting options about what might be where, and even educated guesses by an operating system will be wrong often enough to make trouble.

This style of driver is discouraged. If you’re updating such a driver, please try to move the device enumeration to a more appropriate location, outside the driver. This will usually be cleanup, since such drivers tend to already have “normal” modes, such as ones using device nodes that were created by PNP or by platform device setup.

None the less, there are some APIs to support such legacy drivers. Avoid using these calls except with such hotplug-deficient drivers:

You can use platform_device_alloc() to dynamically allocate a device, which you will then initialize with resources and platform_device_register() . A better solution is usually:

You can use platform_device_register_simple() as a one-step call to allocate and register a device.

Device Naming and Driver Binding¶

The platform_device.dev.bus_id is the canonical name for the devices. It’s built from two components:

platform_device.name … which is also used to for driver matching.

platform_device.id … the device instance number, or else “-1” to indicate there’s only one.

These are concatenated, so name/id “serial”/0 indicates bus_id “serial.0”, and “serial/3” indicates bus_id “serial.3”; both would use the platform_driver named “serial”. While “my_rtc”/-1 would be bus_id “my_rtc” (no instance id) and use the platform_driver called “my_rtc”.

Driver binding is performed automatically by the driver core, invoking driver probe() after finding a match between device and driver. If the probe() succeeds, the driver and device are bound as usual. There are three different ways to find such a match:

Whenever a device is registered, the drivers for that bus are checked for matches. Platform devices should be registered very early during system boot.

When a driver is registered using platform_driver_register(), all unbound devices on that bus are checked for matches. Drivers usually register later during booting, or by module loading.

Registering a driver using platform_driver_probe() works just like using platform_driver_register(), except that the driver won’t be probed later if another device registers. (Which is OK, since this interface is only for use with non-hotpluggable devices.)

Early Platform Devices and Drivers¶

The early platform interfaces provide platform data to platform device drivers early on during the system boot. The code is built on top of the early_param() command line parsing and can be executed very early on.

Example: “earlyprintk” class early serial console in 6 steps

1. Registering early platform device data¶

The architecture code registers platform device data using the function early_platform_add_devices(). In the case of early serial console this should be hardware configuration for the serial port. Devices registered at this point will later on be matched against early platform drivers.

2. Parsing kernel command line¶

The architecture code calls parse_early_param() to parse the kernel command line. This will execute all matching early_param() callbacks. User specified early platform devices will be registered at this point. For the early serial console case the user can specify port on the kernel command line as “earlyprintk=serial.0” where “earlyprintk” is the class string, “serial” is the name of the platform driver and 0 is the platform device id. If the id is -1 then the dot and the id can be omitted.

3. Installing early platform drivers belonging to a certain class¶

The architecture code may optionally force registration of all early platform drivers belonging to a certain class using the function early_platform_driver_register_all(). User specified devices from step 2 have priority over these. This step is omitted by the serial driver example since the early serial driver code should be disabled unless the user has specified port on the kernel command line.

4. Early platform driver registration¶

Compiled-in platform drivers making use of early_platform_init() are automatically registered during step 2 or 3. The serial driver example should use early_platform_init(“earlyprintk”, &platform_driver).

5. Probing of early platform drivers belonging to a certain class¶

The architecture code calls early_platform_driver_probe() to match registered early platform devices associated with a certain class with registered early platform drivers. Matched devices will get probed(). This step can be executed at any point during the early boot. As soon as possible may be good for the serial port case.

6. Inside the early platform driver probe()В¶

The driver code needs to take special care during early boot, especially when it comes to memory allocation and interrupt registration. The code in the probe() function can use is_early_platform_device() to check if it is called at early platform device or at the regular platform device time. The early serial driver performs register_console() at this point.

For further information, see
.

© Copyright The kernel development community.

Источник