[STLinux-announce] Re: Update to the STLinux Distribution 2.0 (#6)

[stlinux-announce at stlinux.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Folks

There were two changes in the SH4 kernel in the latest set of updates
(version 2.6.11.12_stm20-32) which should have been highlighted as
having a user visible effect. These have caught out a number of
people, hence this email to try and avoid further problems:

  - Disable the I2C support for SSC1 on the 7100ref (it is used for SPI)

    This had been causing problems for a while, as probing for I2C
    devices attached to SSC1 could produce random results as the only
    device attached to it uses the SPI protocol. However this also had
    the knock on effect of renumbering the I2C bus driven by SSC2 from
    2 to 1. This bus is used for HDMI, and as a result it causes
    problems for the frame buffer driver (stgfb).

    The fix for this is edit the source for stgfb. You need to change
    line 127 of stgfb/Linux/video/stmfb.c from
       static const int HDMI_I2C_ADAPTER_NRS[NR_FRAMEBUFFERS] = {2,-1};
    to
       static const int HDMI_I2C_ADAPTER_NRS[NR_FRAMEBUFFERS] = {1,-1};

    More details are available from bugzilla:
       https://bugzilla.stlinux.com/show_bug.cgi?id=640

  - Fix coprocessor memory allocation and cache flushing

    A second part of this change was to allow coprocessor memory
    regions to be placed anywhere in the address map. This had the
    knock on effect that the format of the kernel command line option
    "coprocessor_mem=" changed so that the size and address of each
    region needs to be specified, and these must now be within the
    range of memory known to the Linux kernel. The documentation on
    the STLinux web site has now been updated to reflect this:

http://linux.bri.st.com/docs/manual/development/advanced_development22.php

    A typical command line before this would have used:
       mem=48m coprocessor_mem=48m:0m,16m
    this should now be:
       mem=64m coprocessor_mem=0 at 0,16m at 0x07000000

    Unfortunately there is also a bug in the new command line parsing
    code which means that you cannot have the coprocessor_mem option
    as the last one on the command line, or with only the mem= option
    after it.

    More details are available from bugzilla:
       https://bugzilla.stlinux.com/show_bug.cgi?id=637

Sorry for any problems this has caused.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEdK0R61BlSKQGbXkRAuvhAJsHxc88VI7yVuJDgGoGHb92xJ4SOwCaArkL
us2u7De+Lz/nd5QTVVVIaek=
=grpT
-----END PGP SIGNATURE-----