I'm glad it worked! =)

Em 17-06-2014 09:03, krd escreveu:


On Thursday, June 12, 2014 4:52:51 PM UTC+2, Miguel Aveiro wrote:

    Em 12-06-2014 07:04, krd escreveu:
    On Wednesday, June 11, 2014 11:33:25 AM UTC+2, krd wrote:



        On Wednesday, June 4, 2014 4:50:44 PM UTC+2, RobertCNelson
        wrote:

            On Wed, Jun 4, 2014 at 9:29 AM, krd <k...@dacsystem.pl>
            wrote:
            > Hey,
            >
            > I'm testing a new kernel - 3.15.0-rc5-bone0.1 from
            RCN's github - for my BBB
            > under Debian. What I've found out recently is lack of
            > /sys/devices/bone_capemgr.* directory. Also my atempts
            to turn off hdmi via
            > uEnv file fizzle out. Is it me doing something wrong or
            this is how it
            > should be? Is there a way to get back my control over
            uarts, and ability to
            > turn off hdmi under new kernel?

            capemgr hasn't been ported fully from 3.8

            Use this repo:

            https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.15
            <https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.15>



            You can enable extra usarts by adding this to uEnv.txt

            cape=ttyO1

            Regards,

-- Robert Nelson
            http://www.rcn-ee.com/



        I have switched to the image you've recommended and succeeded
        only with enabling ttyO1, The other ones are not enabled.
        I've defined them like that in uEnv.txt:
        /cape=ttyO1
        cape=ttyO4
        cape=ttyO2
        cape=ttyO5/

        Is there a way to disable HDMI? cape_disable=capemgr.disable_
        partno=BB-BONELT-HDMI,BB-BONELT-HDMIN in uEnv.txt is not
        working, but since you said that capemgr had not been ported
        to new kernel I'm not surprised. If it's not possible to do
        in some other way, which is the latest system where capemgr
        works?


    Ok, I managed to switch off hdmi by removing all hdmi-related
    entries from dts files and recompile the kernel. That's not the
    most elegant solution for sure, but it works;) The uarts' issue
    still waits for the solution.

    Well, I think there is a better solution, but since you already
    recompiled the kernel, I did just like you and edited
    "am335x-boneblack.dts":

    /*
     * Copyright (C) 2012 Texas Instruments Incorporated -
    http://www.ti.com/
     *
     * This program is free software; you can redistribute it and/or
    modify
     * it under the terms of the GNU General Public License version 2 as
     * published by the Free Software Foundation.
     */
    /dts-v1/;

    #include "am33xx.dtsi"
    #include "am335x-bone-common.dtsi"

    &ldo3_reg {
        regulator-min-microvolt = <1800000>;
        regulator-max-microvolt = <1800000>;
        regulator-always-on;
    };

    &mmc1 {
        vmmc-supply = <&vmmcsd_fixed>;
    };

    &mmc2 {
        vmmc-supply = <&vmmcsd_fixed>;
        pinctrl-names = "default";
        pinctrl-0 = <&emmc_pins>;
        bus-width = <8>;
        status = "okay";
        ti,vcc-aux-disable-is-sleep;
    };

    &uart2 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart2_pins>;

        status = "okay";
    };

    &uart4 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart4_pins>;

        status = "okay";
    };

    &uart5 {
        pinctrl-names = "default";
        pinctrl-0 = <&uart5_pins>;

        status = "okay";
    };

    &am33xx_pinmux {
    };


    / {
        cpus {
            cpu@0 {
                cpu0-supply = <&dcdc2_reg>;
                /*
                 * To consider voltage drop between PMIC and SoC,
                 * tolerance value is reduced to 2% from 4% and
                 * voltage value is increased as a precaution.
                 */
                operating-points = <
                    /* kHz    uV */
                    1000000    1325000
                    800000    1300000
                    600000  1112000
                    300000   969000
                >;
            };
        };

    };


Thanks a lot! Your solution works very nice.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com <mailto:beagleboard+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

--
For more options, visit http://beagleboard.org/discuss
--- You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to