Hello,

Here´s some fixes for a D-Link DVA-G3810BN target. The first is an edit and the second should be a patch, but I´m not sure how to make the patch - it´s a heavily patched file

Edit:
trunk/target/linux/brcm63xx/image/Makefile
# D-Link DVA-G3810BN/TL
$(call Image/Build/CFEFIXUP,$(1),96358VW,DVAG3810BN,6358,DVAG3810BN)

Add:
linux-brcm63xx/linux-3.0.18/arch/mips/bcm63xx/boards/board_bcm63xx.c

/* D-Link DVA-G3810BN/TL */
static struct board_info __initdata board_DVAG3810BN = {
    .name                = "DVAG3810BN",
    .expected_cpu_id    = 0x6358,

    .has_uart0            = 1,
    .has_enet0            = 1,
    .has_enet1            = 1,
    .has_pci            = 1,

    .enet0 = {
        .has_phy            = 0,    // makes warnings go away
        .use_internal_phy    = 1,
        .force_speed_100    = 1,
        .force_duplex_full    = 1,
    },

    .enet1 = {
        .force_speed_100    = 1,
        .force_duplex_full    = 1,
    },


    .has_ohci0 = 1,
    .has_pccard = 1,
    .has_ehci0 = 1,

    .leds = {
        {
            .name        = "VoIP",
            .gpio        = 1,
        },
        {
            .name        = "DSL",
            .gpio        = 22,
            .active_low    = 1,
        },
        {
            .name        = "Internet",
            .gpio        = 23,
            .active_low    = 1,
        },
        {
            .name        = "power",
            .gpio        = 4,
            .default_trigger = "default-on",
        },
        {
            .name        = "stop",
            .gpio        = 5,
        },
    },

    .buttons = {
        {
            .desc        = "reset",
            .gpio        = 10,    // Not sure, 1..9, 30,31,32,33,34=wrong
            .active_low    = 1,
            .type        = EV_KEY,
            .code        = KEY_RESTART,
            .threshold    = 3,
        },
    },
};

[....]

&board_DVAG3810BN,

Could someone put this in trunk, or explain what to do to get it added?

Thanks,
Jeroen

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to