Difference between pages "Subarches" and "Package:Feh"

From Funtoo
(Difference between pages)
Jump to navigation Jump to search
 
 
Line 1: Line 1:
{{:Install/Header}}
{{Ebuild
= Funtoo Linux Sub-Architectures =
|Summary=A fast, lightweight imageviewer using imlib2
__NOTITLE__
|CatPkg=media-gfx/feh
This page provides an overview of Funtoo Linux sub-architectures (also called ''subarches'',) designed for quick and easy reference. While this information is available in other places, such as Wikipedia, it often takes some time to study and cross-reference the various articles to get a good understanding of each type of sub-architecture, and this information generally isn't all collected neatly in one place. That is the purpose of this page. When possible, links to more detailed Wikipedia pages are provided. You are encouraged to help maintain this page as well as the Wikipedia articles referenced here.
|Maintainer=
|Homepage=http://feh.finalrewind.org/
}}
=== What is feh? ===


== 64-bit Suport (Generic) ==
<blockquote>
feh is an X11 image viewer aimed mostly at console users. Unlike most other viewers, it does not have a fancy GUI, but simply displays images. It is controlled via commandline arguments and configurable key/mouse actions.[http://feh.finalrewind.org/ Feh homepage]
</blockquote>


=== generic_64 ===
== USE-Flags ==
<console>
CFLAGS: -mtune=generic -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2
</console>
 
The '''generic_64''' subarch is designed to support 64-bit PC-compatible CPUs, such as the [[Wikipedia:AMD_K8|AMD K8-series processors]], which were introduced in late 2003. They were notable as the first processors that supported the [[Wikipedia:X86-64|AMD64 (also called X86-64) 64-bit instruction set]] for PC-compatible systems, which was introduced as a backwards-compatible 64-bit alternative to Intel's IA-64 architecture. Intel followed suit and also began supporting this 64-bit instruction set, which they called "[[Wikipedia:X86-64#Intel_64|Intel 64]]", by releasing X86-64 64-bit compatible CPUs from mid-2004 onwards (See [[Wikipedia:X86-64#Intel_64_implementations|Intel 64 implementations]].)
 
AMD desktop 64-bit CPUs include the Athlon 64, Athlon 64 FX, Athlon 64 X2, Athlon X2, Turion 64, Turion 64 X2 and Sempron series processors. AMD server processors were released under the Opteron brand and have codenames SledgeHammer, Venus, Troy, Athens, Denmark, Italy, Egypt, Santa Ana and Santa Rosa. All Opterons released through late 2006 were based on the K8 microarchitecture with original X86-64 instructions.
 
== 64-bit AMD Processors ==
 
=== amd64-k10 ===
<console>
CFLAGS: -march=amdfam10 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 3dnow 3dnowext
</console>
 
The '''amd64-k10''' subarch provides support for the [[Wikipedia:AMD_10h|AMD Family 10h processors]], which were released in late 2007 as a successor to the AMD K8 series processors.
 
Desktop amd64-k10 CPUs include [[Wikipedia:AMD Phenom|AMD Phenom]], [[Wikipedia:AMD_10h#Phenom_II_Models|AMD Phenom II]] and [[Wikipedia:AMD_10h#Athlon_II_Models|AMD Athlon II]]. Server CPUs include Opterons with codenames Budapest, Barcelona, Suzuka, Shanghai, Istanbul, Lisbon, and Magny-Cours. A full listing of amd64-k10 Opteron models [[Wikipedia:List_of_AMD_Opteron_microprocessors#K10_based_Opterons|can be found here]].
 
=== amd64-bulldozer ===
<console>
CFLAGS: -march=bdver1 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>
 
The '''amd64-bulldozer''' subarch supports the [[Wikipedia:Bulldozer (microarchitecture)|AMD bulldozer microarchitecture]] CPUs, which were released from late 2011 through the first quarter of 2012 as a replacement for the [[Wikipedia:AMD_10h|K10 microarchitecture]] CPUs.
Bulldozer desktop CPUs use the [[Wikipedia:Socket_AM3+|AM3+ socket]] and server CPUs use the  [[Wikipedia:Socket_G34|G34 socket]].
 
Desktop bulldozer CPUs include the [[Wikipedia:List_of_AMD_FX_microprocessors#.22Zambezi.22_.2832_nm_SOI.29|Zambezi FX-series CPUs]]. Server bulldozer CPUs include Opterons with codenames Zurich (Opteron 3200-series), Valencia (Opteron 4200-series) and Interlagos (Opteron 6200 series). A complete list of Opteron models [[Wikipedia:http://en.wikipedia.org/wiki/Opteron#Opteron_.2832_nm_SOI.29-_First_Generation_Bulldozer_Microarchitecture|can be found here.]].
 
=== amd64-piledriver ===
<console>
CFLAGS: -march=bdver2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>
 
The '''amd64-piledriver''' subarch supports the [[Wikipedia:Piledriver (microarchitecture)|AMD Piledriver microarchitecture]] produced by AMD from mid-2012 through 2015, which is the successor to the [[Wikipedia:Bulldozer (microarchitecture)|AMD bulldozer microarchitecture]].
Piledriver CPUs and APUs are available that use the [[Wikipedia:FM2 Socket|FM2 socket]]. Desktop Piledriver CPUs use the [[Wikipedia:Socket_AM3+|AM3+ socket]]. Server Piledriver CPUs use a variety of sockets, including [[Wikipedia:Socket_AM3+|AM3+]], [[Wikipedia:Socket_C32|C32]] and [[Wikipedia:Socket_G34|G34]].
 
Desktop piledriver CPU and APUs include FX-series with codename Vishera (FX-8350, FX-8370),  [[Wikipedia:List_of_AMD_accelerated_processing_unit_microprocessors#Virgo:_.22Trinity.22_.282012.2C_32_nm.29|A-series with codename Trinity]] (A6-5400K, A10-5800K) and [[Wikipedia:http://en.wikipedia.org/wiki/List_of_AMD_accelerated_processing_unit_microprocessors#.22Richland.22_.282013.2C_32_nm.29_2|A-series with codename Richland]].
 
Server piledriver CPUs include Opterons with codenames Delhi (Opteron 3300-series, [[Wikipedia:Socket_AM3+|AM3+]]), Seoul (Opteron 4300-series, [[Wikipedia:Socket_C32|C32]])  and Abu Dhabi (Opteron 6300-series, [[Wikipedia:Socket_G34|G34]]). A full listing of Opteron models [[Wikipedia:Opteron#Opteron_.2832_nm_SOI.29_-_Piledriver_Microarchitecture|is available here]].


Piledriver adds several new instructions over bulldozer, so AMD bulldozer systems cannot run amd64-piledriver-optimized stages. However, this subarch is  instruction-compatible with its successor, the, so amd64-piledriver stages can run on amd64-steamroller systems, and vice versa.
;<code>curl</code>: Add support for the Client-Side URL transfer library.
;<code>debug</code>: Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces, see http://www.gentoo.org/proj/en/qa/backtraces.xml.
;<code>exif</code>: Add support for reading EXIF headers from JPEG and TIFF images.
;<code>xinerama</code>: Add support for the xinerama X11 extension, which is mandator if you work in a multiple monitor setup.


=== amd64-steamroller ===
== Installing feh ==
After adding your USE flags (or not) to <tt>/etc/portage/package.use/feh</tt>, you can emerge feh:
<console>
<console>
CFLAGS: -march=bdver3 -O2 -pipe
###i## emerge feh
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>
</console>


The '''amd64-steamroller''' subarch supports the [[Wikipedia:Steamroller (microarchitecture)|AMD steamroller microarchitecture]], produced from early 2014. It is the successor to the [[Wikipedia:Piledriver (microarchitecture)|AMD Piledriver microarchitecture]].
== Using feh ==
Steamroller APUs are available that use the [[Wikipedia:FM2+ Socket|FM2+ socket]] and  [[Wikipedia:Socket_FP3|FP3 socket]] (mobile.)
=== Set desktop background ===
 
<tt>feh</tt> has several options for setting your desktop background:
Desktop steamroller APUs include the [[Wikipedia:AMD_Accelerated_Processing_Unit#Steamroller_architecture_.282014.29:_Kaveri|A-Series with codename Kaveri]], such as the quad-core AMD A10-7850K APU. Steamroller APUs are also available in mobile versions. Server steamroller APUs will include the Berlin APUs, which are expected to be released some time in 2015.
* <tt>--bg-center</tt>: Center the image file on the background. If the image file is smaller in resolution than the screen resolution, it will have black borders around it.
* <tt>--bg-scale</tt>: Fit the image to the background without repeating it, cutting parts of the image off, or using black borders. Because of these changes, the aspect ratio is not preserved.
* <tt>--bg-fill</tt>: Similar to <tt>--bg-scale</tt> except that it tries to fill the image to the screen while maintaining its aspect ratio. This may result in parts of the image being cut off.
* <tt>--bg-max</tt>: Similar to <tt>--bg-fill</tt>, except that scales the image to the maximum size that fits the screen. This leads to black borders on one side.
* <tt>--bg-tile</tt>: Tile the image across the screen.


Amd64-steamroller subarches are instruction-compatible with amd64-piledriver, but add new instructions over amd64-bulldozer.
Here is an example:
 
=== amd64-jaguar ===
<console>
<console>
CFLAGS: -march=btver2 -O2 -pipe
###i## feh --bg-scale ~/path/to/picture.jpg
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>
</console>


The '''amd64-jaguar''' (also called AMD Family 16h) subarch supports the  [[Wikipedia:Jaguar (microarchitecture)|AMD jaguar microarchitecture]], which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the [[Wikipedia:Playstation 4|Playstation 4]] and [[Wikipedia:Xbox One|Xbox One]], which each use custom 8-core Jaguar APUs.
=== Source fehbg to set your wallpaper in Openbox ===
Socketed Jaguar APUs use the [[Wikipedia:AM1 Socket|AM1 socket]], and  [[Wikipedia:Socket_FT3|FT3 socket]] for mobile devices. G-series [[Wikipedia:System_on_a_chip|"system on a chip" (SoC)]] APUs are available for non-socketed devices such as tablets and embedded system boards.
After you have run <tt>feh</tt> one time, the directory of the image file is stored in <tt>~/.fehbg</tt>. This file can be sourced in your <tt>.config/openbox/autostart</tt> to load the picture instead of typing out <tt>feh --bg-scale /picture/location.jpg</tt>:
 
Desktop Jaguar APUs include the [[Wikipedia:List_of_AMD_accelerated_processing_unit_microprocessors#.22Kabini.22.2C_.22Temash.22_.282013.2C_28_nm.29|Kabini A-series APUs and Temash E-series APUs]], such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.
 
Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.
 
== 64-bit Intel Processors ==
=== core2_64 ===
<console>
CFLAGS: -march=core2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 ssse3
</console>
 
The '''core2_64''' subarch supports [[Wikipedia:Intel_Core#64-bit_Core_microarchitecture_based|64-bit-capable processors]] based on the [[Wikipedia:Intel Core (microarchitecture)|Core microarchitecture]] and all processors of the [[Wikipedia:Penryn_(microarchitecture)|Penryn microarchitecture]]. This includes all [[Wikipedia:Intel_Core_2|Intel Core 2]] branded processors, [[Wikipedia:Celeron#Core-based_Celerons|some Celeron]], [[Wikipedia:Pentium#Core_microarchitecture_based|some Pentium]] and [[Wikipedia:Xeon#Core-based_Xeon|some Xeon]] branded processors. These processors were introduced in July of 2006 and were phased out in July of 2011, in favor of  [[Wikipedia:Nehalem_(microarchitecture)|Nehalem-based]] processors.
 
For a full list of Core 2 processors, [http://ark.intel.com/search/advanced?s=t&FamilyText=Legacy%20Intel%C2%AE%20Core%E2%84%A22%20Processor see this link].<br />
For a full list of supported Xeon processors, [[Wikipedia:Xeon#Core-based_Xeon|see this link]].
 
=== corei7 ===
<console>
CFLAGS: -march=corei7 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 ssse3 sse4
</console>
 
Beginning in November 2008, Intel launched the first Core i7 processor, codenamed [[Wikipedia:Bloomfield_(microprocessor)|Bloomfield]], based on the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]] microarchitecture. With this launch, they also added to and modified the conventions used in their [[Wikipedia:Intel_Core|Intel Core]] branding scheme. '''(Not to be confused with the [[Wikipedia:Intel Core (microarchitecture)|Intel Core microarchitecture]]. See [[Subarches#core2_64|core2_64]].)'''. This new naming scheme distinguishes between grades of processors rather than microarchitectures or design. Therefore, the '''corei7''' subarch supports the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Sandy_Bridge_(microarchitecture)|Sandy Bridge]],  [[Wikipedia:Ivy_Bridge_(microarchitecture)|Ivy Bridge]], and [[Wikipedia:Haswell_(microarchitecture)|Haswell]] microarchitectures under the follow brand names:
 
* Intel Pentium/Celeron (low-level consumer)
* Intel Core i3 (entry-level consumer)
* Intel Core i5 (mainstream consumer)
* Intel Corei7 (high-end consumer/business)
* Intel Xeon (business server/workstation)
 
See the following links for a list of supported [[Wikipedia:Celeron|Celeron]], [[Wikipedia:Pentium|Pentium]], [[Wikipedia:Intel_Core#Nehalem_microarchitecture_based|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Intel_Core#Sandy_Bridge_microarchitecture_based|Sandy Bridge]],  [[Wikipedia:Intel_Core#Ivy_Bridge_microarchitecture_based|Ivy Bridge]], and [[Wikipedia:Intel_Core#Haswell_microarchitecture_based|Haswell]] processors.
 
=== atom_64 ===
<console>
CFLAGS: -O2 -fomit-frame-pointer -march=atom -pipe -mno-movbe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3
</console>
 
The Intel Atom Processor is the common name for Intel's  [[Wikipedia:Bonnell_(microarchitecture)|Bonnell microarchitecture]],  which represents a partial revival of the principles used in earlier Intel designs such as P5 and the i486, with the sole purpose of enhancing the performance per watt ratio.  Successor to the [[Wikipedia:Stealey_(microprocessor)|Intel A100 series (Stealey)]], which was derived from the [[Wikipedia:Pentium_M|Pentium M]], the Intel Atom has been produced since 2008. Targeted at low-power devices, Atom processors can be found in a wide range of notebooks, tablets and small form-factor desktops and servers.
 
The '''atom_64''' sub-architecture supports 64-bit capable Intel Atom CPUs.  The first 64-bit capable Intel Atom CPUs were the Intel Atom 230 and 330, released in late 2008. However, Intel also continued to produce new 32-bit Atom Processors after this date. For example, the Atom N2xx series Atom Diamondville models cannot support 64-bit operation, while the 2xx and 3xx Diamondville, Pineview, Cedarview and Centerton can. A full list of 64-bit capable Intel Atom Processors [http://ark.intel.com/search/advanced?s=t&FamilyText=Intel%C2%AE%20Atom%E2%84%A2%20Processor&InstructionSet=64-bit can be seen here.]
 
{{Important|For 64-bit support to be functional, a 64-bit capable Atom Processor must be paired ''with a processor, chipset, and BIOS'' that all support [[Wikipedia:X86-64#Intel_64|Intel 64]]. If not all hardware supports 64-bit, then you must use the '''atom_32''' subarch instead.}}


{{:Install/Footer}}
{{file|name=~/.config/openbox/autostart|desc= |body=
...
~/.fehbg &
...
}}
{{EbuildFooter}}

Revision as of 22:55, November 19, 2014

Feh

   Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

What is feh?

feh is an X11 image viewer aimed mostly at console users. Unlike most other viewers, it does not have a fancy GUI, but simply displays images. It is controlled via commandline arguments and configurable key/mouse actions.Feh homepage

USE-Flags

curl
Add support for the Client-Side URL transfer library.
debug
Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces, see http://www.gentoo.org/proj/en/qa/backtraces.xml.
exif
Add support for reading EXIF headers from JPEG and TIFF images.
xinerama
Add support for the xinerama X11 extension, which is mandator if you work in a multiple monitor setup.

Installing feh

After adding your USE flags (or not) to /etc/portage/package.use/feh, you can emerge feh:

root # emerge feh

Using feh

Set desktop background

feh has several options for setting your desktop background:

  • --bg-center: Center the image file on the background. If the image file is smaller in resolution than the screen resolution, it will have black borders around it.
  • --bg-scale: Fit the image to the background without repeating it, cutting parts of the image off, or using black borders. Because of these changes, the aspect ratio is not preserved.
  • --bg-fill: Similar to --bg-scale except that it tries to fill the image to the screen while maintaining its aspect ratio. This may result in parts of the image being cut off.
  • --bg-max: Similar to --bg-fill, except that scales the image to the maximum size that fits the screen. This leads to black borders on one side.
  • --bg-tile: Tile the image across the screen.

Here is an example:

root # feh --bg-scale ~/path/to/picture.jpg

Source fehbg to set your wallpaper in Openbox

After you have run feh one time, the directory of the image file is stored in ~/.fehbg. This file can be sourced in your .config/openbox/autostart to load the picture instead of typing out feh --bg-scale /picture/location.jpg:

   ~/.config/openbox/autostart
...
~/.fehbg &
...